القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | wdd-plan-waves |
| 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. |
Use this when the user asks for the older wave-planning phase.
Interpret wave-planning requests as requests to plan or replan task waves for an epic, including dependencies, conflict domains, orchestration state, and controller state.
wdd-plan-epic.wdd-plan-epic planning steps.orchestration.json and controller-state.md match the wave plan.wave-plan.md is internally consistent.orchestration.json tracks every planned task.wdd-start-wave.