Writing Plans

Purpose

Write plans that help an agent or engineer act, verify progress, and expose uncertainty. Keep the plan as small as the task allows.

First Steps

1. Retrieve missing context before asking the user when local files, command output, or existing documentation can answer the question.
2. State assumptions and unknowns only when they affect execution or validation.
3. Ask at most one clarifying question if the plan would otherwise depend on a risky guess.
4. Prefer a short plan over a complete-looking template.

File Output

When this skill is used, produce a plan document. Save it to the repository by default unless the user explicitly asks for chat-only output.

Use ./docs/plans/ by default unless the user specifies another path. Name plan files as YYYY-MM-DD_<topic>-plan.md, where <topic> is a lowercase kebab-case stem, for example 2026-05-10_auth-migration-plan.md or 2026-05-10_checkout-refactor-plan.md.