Writing Plans

Write comprehensive implementation plans assuming zero codebase context. Document: which files to touch, code, testing, docs, how to test. Bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. Assume skilled developer, minimal domain knowledge, weak test design.

Announce at start: "I'm using the writing-plans skill to create the implementation plan." Context: Run in a dedicated worktree (created by brainstorming skill). Save plans to: docs/plans/YYYY-MM-DD-<feature-name>.md using the Write tool. NEVER write to ~/.claude/plans/ — ignore the plan mode default path. REQUIRED: Before ExitPlanMode, run Plan Verification Checklist, then rule-of-five-plans. Verify what before polishing how -- scope errors caught early save wasted polish on deleted tasks.

Mandatory Tasks (Enforcement)

Create these 7 native tasks at plan start (each blocked by previous via addBlockedBy). Cannot call ExitPlanMode with pending tasks:

1. Write draft plan -- Initial structure with all tasks, dependencies, file lists
   • After saving plan — context check: Look at your model ID in the system prompt (e.g., claude-opus-4-6[1m]).
     • [1m] present (default): Skip compact. Announce "Plan written to {path}. Proceeding to verification." and continue to task 2.
     • No [1m] (200k): Show copy-pasteable /compact command (see references/announcements-protocol.md) and wait for user's follow-up before proceeding to task 2.
2. Plan Verification Checklist -- Complete/Accurate/Commands valid/YAGNI/Minimal/Not over-engineered
3. Rule-of-five-plans: Draft pass -- Shape and structure