/create_plan

Create detailed implementation plans through an interactive, iterative process. The agent researches the codebase, works with you to understand requirements, and produces a phased technical specification.

Usage

/create_plan

Or with a ticket file:

/create_plan thoughts/shared/tickets/eng_1234.md

Process

1. Read what you gave it. Ticket files, research, and prior plans are read in full first; the intake prompt appears only on a bare /create_plan
2. Research. One cartographer per affected area in parallel, plus an archivist for prior plans and decisions
3. Present understanding. Findings with file:line references and only the questions the code cannot answer
4. Outline and approve. You sign off on the phase list before any body is written
5. Draft and adjudicate. A draughtsman writes the body from the approved outline; an adjudicator hunts phantom paths and unverifiable criteria before the plan is saved

Plan Structure

The agent saves plans to thoughts/shared/plans/YYYY-MM-DD-[ENG-XXXX-]description.md on git/obsidian, or as a typed row/object on notion/anytype. Each plan includes:

• Problem statement and context
• Phased implementation steps
• Specific file changes per phase
• Success criteria for each phase
• Checkboxes for tracking completion

Key Behavior

• Uses Opus. Deep reasoning model for thorough analysis
• Interactive. The agent asks questions and iterates on the plan with you
• Skeptical. The agent challenges assumptions and identifies potential issues
• Codebase-aware. Researches existing code before proposing changes