Writing Plans

Write implementation plans that let a skilled engineer work safely with almost no prior context. A plan names the exact files, interfaces, behavior, tests, documentation, and commands needed for each independently verifiable task. Plans are durable repository artifacts, not chat-only checklists. Each task also ends with a compile, diff review, and conventional commit gate.

Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the writing-plans skill to create the implementation plan."

Context: If working in an isolated worktree, use the repository's worktree workflow at execution time. Do not make the plan depend on chat history.

Save plans to: .agents/plans/YYYY-MM-DD-<feature-name>.md

Every plan is Markdown with YAML frontmatter. The frontmatter is the machine-readable index for cross-session tracking: