القائمة
Create a phase/feature plan that scopes work, defines high-level tasks, and identifies dependencies. Dispatches Ada for planning.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks ("do this thoroughly", "be systematic", "deep work mode") OR when the task objectively spans multiple files, multiple sources, or multiple sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine.
Bootstrap project orchestration with beads task tracking.
Core engineering principles for implementation tasks
Create beads from a spec (full decomposition) or from user input (ad-hoc issues). Single entry point for all bead creation.
Dispatch the implementation supervisor for a bead task. Resolves the correct supervisor from the assignee field, checks branch state, and dispatches with full context.
QA finalization gate — validates spec conformity, runs tests/build/lint, produces a structured QA report. Auto-dispatches the supervisor for rework on FAIL. Last gate before human merge.
استنادا إلى تصنيف SOC المهني
| name | plan |
| description | Create a phase/feature plan that scopes work, defines high-level tasks, and identifies dependencies. Dispatches Ada for planning. |
| user_invocable | true |
Create a phase or feature plan that scopes work and identifies dependencies for research and specification.
Define output location:
docs/plans/{NN}-plan-{feature-kebab}.mddocs/plans/ directory exists (create if needed)Dispatch using exactly these parameters — no more, no less:
Agent(
subagent_type="architect",
prompt="Create a PHASE PLAN (not a spec) for: {phase_description}. Read the PRD at {prd_path} and architecture at {arch_path} for context. This is a planning document that defines: scope (what's in/out for this phase), high-level task breakdown, dependencies between tasks, external dependencies and APIs that will need research, and acceptance criteria for the phase. Save to {plan_path} with status DRAFT. Do NOT write implementation specs — that comes after research validates the plan's assumptions. Iterate with the user until APPROVED."
)
Do NOT add extra parameters unless the user explicitly requests it.