| name | compound-v-plan |
| description | Autonomous planning with internal reasoning. Researches, evaluates ideas, presents a plan. Minimizes user round-trips. Use before making non-trivial changes. |
Planning Skill
Announce at start: "I'm using the planning skill to work through this."
When to use this skill
- any multi-file change
- any change that impacts behavior, data, auth, billing, or production workflows
- any debugging that needs systematic isolation
- any design decision with multiple viable approaches
Core pattern: think first, ask smart
Planning is LLM-driven, not turn-by-turn. Follow these phases:
Phase 1: Establish the goal
Determine the desired end result — the single sentence that defines success.
- If the user stated a clear goal, use it.
- If the goal is ambiguous, ask ONE question: "What's the desired end result?" and STOP.
- Do NOT ask multiple clarifying questions. Infer what you can and note assumptions.
Phase 2a: Load stack context (sequential — before research)
Read .agents/rules/stack.md if it exists; otherwise read legacy .agent/rules/stack.md. If neither exists, infer versions from go.mod, mix.exs, package.json, or equivalent. These versions scope all subsequent web searches.
If stack.md is missing from both locations, print: "No stack.md found. Run /stack to pin your versions — this improves web search accuracy." Then continue planning.
Phase 2b: Research (autonomous — no user interaction)
Do all of this in parallel (invoke multiple tool calls in the same response):
