Writing Plans

Overview

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

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: This should be run in a dedicated worktree (created by obra-brainstorming).

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

Copilot-Friendly Rules

• Output format: Intent → (optional) Assumptions → numbered Plan → Validation commands.
• Keep steps concrete and testable; avoid vague verbs.
• Avoid platform-specific orchestration or slash commands. If parallelism helps, describe it as optional.