28 lines
1.8 KiB
Markdown
28 lines
1.8 KiB
Markdown
---
|
|
description: Trigger phased planning for a new task — enters CLARIFY mode and walks through DISCOVER → PLAN → CRITIC-GATE
|
|
---
|
|
|
|
You are the lead agent. The user has invoked `/plan` to begin structured planning for a task.
|
|
|
|
## Steps
|
|
|
|
1. **CLARIFY**: Ask the user clarifying questions about the task using the `question` tool. Gather: goals, constraints, affected areas, success criteria. Record in megamemory.
|
|
|
|
2. **DECOMPOSE** (if applicable): If the user requested 3+ features, or features span independent domains/risk profiles, load the `work-decomposition` skill. Follow its decomposition procedure to:
|
|
- Identify distinct features and assess independence
|
|
- Group into independent workstreams
|
|
- Classify risk profiles and assign quality tiers
|
|
- Allocate worktrees (one per independent workstream)
|
|
- Identify human checkpoint triggers (security, architecture, vision-dependent features)
|
|
- Present the decomposition to the user and wait for approval before proceeding
|
|
|
|
3. **DISCOVER**: Delegate to `explorer` to map relevant parts of the codebase. Delegate to `researcher` for any technical unknowns. Record findings in megamemory.
|
|
|
|
4. **CONSULT** (if needed): For domain-specific questions, check megamemory for cached SME guidance first. If not cached, delegate to `sme`.
|
|
|
|
5. **PLAN**: Draft a phased task list per workstream. Each task must have: description, acceptance criteria, assigned agent(s), dependencies, workstream assignment, and coder dispatch scope (one feature per coder). Store plan as a megamemory `feature` concept.
|
|
|
|
6. **CRITIC-GATE**: Delegate plan to `critic`. If APPROVED → present plan to user and await go-ahead. If REPHRASE → revise and re-gate. If RESOLVE → **stop**, resolve every blocker, then re-gate. Do not proceed to EXECUTE with unresolved blockers.
|
|
|
|
Present the final approved plan to the user before starting EXECUTE.
|