wdd

Coordinate WDD task worker agents from task files, track each active task independently, run review gates, route feedback, reconcile shared context, and merge only after verification and branch freshness pass.

Run the text-only Wave-Driven Development workflow using local markdown/json artifacts, including wdd-info routing, micro-wave work packets, profiled epics, task waves, controller gates, review, validation, and final PR handoff.

Create or amend a text-only WDD constitution with model aliases, storage mode, branching, review policy, verification policy, agent roles, task rules, wave rules, shared-context rules, and governance.

Initialize a repository for text-only Wave-Driven Development by creating .wdd artifacts, templates, epic storage, and constitution scaffolding without relying on a CLI or scripts.

Activate the next pending WDD wave as a strategy-selected batch of eligible task files, update orchestration and controller state, then hand off to subagent-pr-orchestration.

Show current Wave-Driven Development state from local .wdd text artifacts, including constitution status, micro-wave work packets, epics, tickets, tasks, waves, orchestration gates, monitoring, shared-context reconciliation, validation, and next action.

Plan a WDD epic end to end by creating shared context, ticket containers, task kanban files, dependency and conflict grids, waves, schema-versioned orchestration state, and controller state.

Finish a WDD micro-wave by reconciling task evidence, review state, branch freshness, verification, and final handoff for a .wdd/work packet without epic validation ceremony.

Plan a WDD micro-wave by splitting one work packet into 2-5 compact task briefs and state.json. Use after wdd-start-work when a bounded ticket benefits from compact task planning without full epic planning ceremony.

Reconcile a completed WDD wave by inspecting task files, PRs or patches, reviews, verification, shared-context updates, architecture drift, and future-wave readiness before starting the next wave.

Run or resume a WDD micro-wave by dispatching compact task workers from .wdd/work state, tracking gates, applying adaptive monitoring, and preparing tasks for wdd-finish-work.

Explain Wave-Driven Development modes and route users to the right next step. Use when the user asks whether to use WDD, how WDD works, which mode to choose, how to reduce ceremony or token use, how to resume existing WDD work, or what skill to run next for micro, lite, standard, or full workflows.

Start a WDD micro-wave work packet for one bounded ticket or request that may split into a few compact tasks without full epic ceremony. Use when the user asks for WDD micro, micro-wave, ticket-sized WDD, or controlled execution for a single chunky task.

Start a profiled WDD epic by turning broad feature, migration, refactor, hardening, or bug-cluster input into an implementation-ready epic specification and progressive shared-context scaffold under .wdd/epics. Use wdd-start-work instead for single chunky tickets that fit micro-wave scope.

Sync Wave-Driven Development local epics with GitHub Projects as an optional adapter. Use when Codex needs to import or pull GitHub Project epics, tickets, or tasks into .wdd/epics, push local WDD tickets or tasks toward GitHub Issues/Projects, compare local and remote planning state, generate dry-run sync plans, write adapter manifests, or report GitHub/WDD conflicts without making GitHub Projects a required WDD backend.

Validate a completed WDD epic branch after all waves are reconciled by checking deliverables, task evidence, reviews, shared context, integration state, branch state, and final PR readiness.

Prepare the final WDD epic pull request from the epic branch into the target branch after epic validation passes, including a comprehensive human-review description.

Compatibility wrapper for older WDD wave-planning prompts; route work into wdd-plan-epic because waves now schedule executable task files and require orchestration state.

Compatibility wrapper for older WDD validation prompts; route validation into wdd-plan-epic because planning now validates epic, ticket, task, wave, shared-context, and orchestration readiness together.

Compatibility wrapper for older WDD prompts that asked to write tickets; route the work into wdd-plan-epic because tickets, tasks, validation, waves, and orchestration are now planned together.