Wira Delta Indonesia

Overview

WDI Method Documentation

A review layer on top of BMad: documents a human reads to check technical decisions before code is written, sized to what the change actually deserves.

Choose Your Documentation Route

WDI Method serves different roles in a software team. Choose the route that matches your current goal:

For Business & Product Leaders

Understand the Method

How five review gates put technical decisions in front of a person, from the problem to the release, and what each gate asks.

Why WDI Method →

For Developers & Engineers

Quickstart & Workflows

Install the method in 3 steps, understand the 3 workflow tracks, and learn the four daily skills you run inside your agent.

Start Quickstart →

For Staff Engineers & Contributors

Field Guide & Architecture

Configure custom dispatch, read the field rules (the Windows process gate, branches and worktrees), and look up the 22 skills.

Read Field Guide →

What Is WDI Method?

BMad writes documents for AI agents. WDI Method adds documents that many roles already read: use cases, C4 diagrams, API and database lists, and design documents. It wraps BMad without replacing it: the WDI skills for the product brief, the PRD, UX, and the blueprint hand the writing to a BMad skill, then check the result against the method's guides.

1. Documents for Agents: BMad Method: writes the product brief, the PRD, UX, and the architecture spine, each through a BMad skill.

2. Review Layer: WDI Method: wraps those skills, adds the documents other roles read, runs five human gates, links Goal → FR → UC → Ticket → Test, and checks the corpus for drift.

3. Tickets and Code: Engines: to-spec and to-tickets cut the spec into vertical tickets; implement builds each one test-first.

Documents Follow Code

A document behind the code is in its expected state, not a defect. Where the owner chose the code over a document, the document is the one corrected. A document ahead of the code, such as a spec not built yet, is also normal.

Core Pillars at a Glance

  • One Decision Per Gate: each gate decides one thing. At G1 to G4 you read one rendered page; at G5 you read the spec's RTM rows. You answer a short checklist, and one "no" on a starred question holds the gate.
  • Two Fields That Never Merge: mode sets how deep each component's documents go; risk_accepted sets how hard the review is.
  • Single Writer in the Daily Routine: in the daily routine, the coordinating session writes the code itself; reviewers only read.
  • Records in Your Repository: registries, ledgers, and specs live inside your git repository. WDI Method itself makes no network calls. Your coding agent still sends code to its model provider.