Wira Delta Indonesia

Getting Started

Getting Started with WDI Method

Install WDI Method into any git repository in three steps, run in order. All prompts offer defaults, and pressing Enter accepts them.

Prerequisites

  • Node.js: Node.js 20 or later.
  • Git: the standard git CLI.
  • uv: uv, which runs the method's Python 3.11+ validators.
  • An agent platform: any of the 39 hosts npx wdi-method --list-agents prints, such as Claude Code, Kiro, Cursor, Codex, OpenCode, Gemini CLI, and GitHub Copilot.

WDI Method itself makes no network calls. Your coding agent still sends code to its model provider.

Install in 3 Steps

Run the three steps in order. The installer stops if step 1 or step 2 has not been done.

Step 1: Install BMad Method

BMad Method writes the product brief, the PRD, UX, and the architecture spine. WDI Method hands that writing to BMad skills, then checks the result:

cd /path/to/your/product-repo
npx bmad-method install

Step 2: Add the Six Engines

Install the engines from mattpocock/skills into your repository (choose either "copy" or "symlink"):

npx skills@latest add mattpocock/skills

When prompted, select all six engines the method drives: to-spec, to-tickets, implement, tdd, code-review, and domain-modeling, and every agent host you will use. Each host must be able to read them (Kiro, for one, reads only .kiro/skills). When one cannot, the installer stops and prints the npx skills add … --agent <id> command for that host.

Why the Claude Code Plugin Is Not Enough:

Three of the six engines (to-spec, to-tickets, implement) ship with disable-model-invocation: true. On every install and update, WDI Method removes that line from the copies in your repo, so wdi-build and wdi-autopilot can run them. It cannot edit a user-level plugin, so the installer stops until the engines are in the repo. --skip-engines-check skips this check.

If the engines are already in the repo but not in a folder a selected host reads, the installer can copy them there. Choose copy in the interactive installer, add --copy-engines to install or update, or run npx wdi-method engines --copy later. The copy comes from the repo's own files, needs no network, and overwrites nothing.

Step 3: Install WDI Method

Launch the interactive installer. It places the skills where each of your agent platforms reads them:

npx wdi-method

Non-interactive, for CI or headless setups:

npx wdi-method install --yes --agents claude-code --product "Your Product Name"

What the Installer Changes in BMad:

The installer also turns off model invocation for 13 BMad build and sprint skills that the engines replace. On hosts that have a lock, it adds one: deny rules in .claude/settings.json for Claude Code, and "ask" in opencode.json for OpenCode. On every host, the method block it writes into AGENTS.md and the host's own rule file forbids them. You can still run them by typing the command.

Your First Command: /wdi-help

Open your coding agent inside the repository and type:

/wdi-help

Status Read From the Registry

/wdi-help reads .control/registry/ on disk and tells you the gate your project is at, the open specs, and the next skill, instead of guessing from the conversation.

Most hosts take /wdi-help. Codex takes $wdi-help, Kimi Code and Pi take /skill:wdi-help, and Windsurf takes @wdi-help. wdi-help names the next skill in your host's form.

Next Steps

Once installed, pick the workflow that fits your next piece of work: