Wira Delta Indonesia

Workflow Options

WDI Method Workflow Options

Work varies in scale, risk, and context. WDI Method sizes its ceremony to the task through three workflow tracks.

Workflow Selection Matrix

Before starting a task, decide which track fits its scope:

Workflow Best Suited For Human Ceremony How It Runs
Option A: Guided Track New products, major initiatives, architectural changes Review gates G1 to G5, one decision per gate You start each gate skill; the agent names the next one and waits
Option B: Autonomous Daily Everyday work on a system whose architecture is in place An accepted mandate, then a hand-test checklist after the merge Autonomous loop (/wdi-daily-autopilot)
Option C: Fast Path A fix of at most one ticket that changes no FR, UC, AD-N, or domain model No document gates /implement directly, with no wrapper skill

Option A: Guided Delivery Track (G1 to G5)

For new products, major initiatives, and architectural changes. You start each gate skill; the agent names the next one and waits.

  • G1 Problem: Run /wdi-problem → you read .what-rendered/_product-brief/brief.md.
  • G2 Product: Run /wdi-product, and /wdi-ux if you need it → you read .what-rendered/_prd/<slug>/prd.md.
  • G3 Blueprint: Run /wdi-blueprint → you read .how-rendered/blueprint.md. (Once per product.)
  • G4 Component: Run /wdi-component → you read .how-rendered/<pc>/SDD-<pc>.md. (Skipped at mode: catalog.)
  • G5 Release: Run /wdi-build → one spec from open to closed: you run to-spec and to-tickets, each ticket goes to a green PR, then the spec closes. It never merges.

Option B: Autonomous Daily Operations

Once the architecture is in place, everyday work runs as a daily rhythm through four skills you type inside your agent:

  1. /wdi-daily-what-to-build: turns hand-testing notes or bug reports into a reviewed spec or ticket, then stops.
  2. /wdi-daily-autopilot: checks for an accepted mandate (runs the preflight if there is none) and starts the loop, which ends with one PR ready for review.
  3. /wdi-daily-what-to-test: after a merge, syncs the development branch, prunes merged branches, and builds a hand-test checklist.
  4. /wdi-prune-or-archive: archives or prunes closed specs.

For the full command syntax, see Autonomous Daily Operations.

Option C: Fast Path (Direct Implementation)

A fix may skip every gate when it changes no FR, UC, AD-N, or domain model, is at most one ticket, and touches no money, personal data, or third-party integration. You run /implement directly, with no wrapper skill: 

/implement <description of small fix>

When the Fast Path Stops:

If the fix turns out to touch an FR, work stops and becomes a spec of size S (at most 3 tickets), which runs through wdi-build.