plan-review

What this skill does

Plans are written to ./.agents/sessions/{date}-{xxx feature}/plan.md. Use the current date for {date} in YYYY-MM-DD form and a short kebab-case feature label for {xxx feature}. Review comments live inline in that same file — no separate threads, no external tools. The file is the single source of truth for both the plan and its review history.

Writing a plan

A useful plan explains why, not just what. Anyone reading it later — including a reviewer or a future you — should be able to reconstruct the reasoning without access to the original conversation.

For each significant decision, cover:

• What you decided
• What alternatives you considered and why you ruled them out
• What tradeoffs you accepted and why they're acceptable

This is more work upfront but eliminates the most common review failure mode: "why did you do it this way?" when the answer was obvious in context but undocumented.

Structure to follow: