Plan

plan-graph

grill-with-docs

validate-direction

Output Location

.codex/plans/

.plan.md

.plan.md

Plan Shape

plan-graph

---
name: <short unique plan name>
overview: <one paragraph summary>
todos:
  - id: <stable-id>
    content: <concrete executable task>
    status: pending
isProject: false
---

# <short unique plan name>

## Execution Notes

<intent, context, accepted decisions, and useful references>

## Constraints

<scope limits, compatibility requirements, files not to touch, rollout constraints>

## Operator Guidance

<testing, sequencing, review notes, and when to use subagents>

add-parser-tests

implement-parser

wire-cli

Workflow

1. Read the PRD, issue, or brief.
2. Read

   CONTEXT.md

   ,

   docs/adr/

   , and

   docs/agents/domain.md

   when present.
3. Identify natural work lanes:
   • shared interface or schema work
   • independent implementation modules
   • tests and fixtures
   • migrations or compatibility work
   • documentation or rollout
4. Choose one or more plan files.
5. Make dependencies clear in plan structure:
   • sequential todos inside one plan for tightly coupled work
   • separate plan files for lanes that can run independently
   • note explicit inter-plan dependencies in

     Operator Guidance

6. Keep todo text executable and reviewable. Each todo should describe one outcome, not a vague phase.
7. Validate with

   plan-graph

   before any subagent launch.

Boundaries

• Do not spawn subagents from this skill. Planning produces files; orchestration comes later.
• Do not use a single huge plan when two independent lanes would graph cleanly.
• Do not create speculative tasks for work the PRD explicitly excludes.
• Do not mark todos

  completed

  unless the work is already done in the repo.

Next Step

plan-graph validate

subagent-graph