write-planlisted

# Write Plan ## Overview Write comprehensive implementation plans assuming the engineer has zero context for the 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 the toolset or problem domain. Assume they don't know good test design very well. **Announce at start:** "I'm using the write-plan skill to create the implementation plan." **Context:** Plans are written in the user's checkout; they are *executed* in this checkout if already on the ticket branch, otherwise in a per-ticket worktree that execute-plan opens via the `git-worktrees` skill. Keep every path in the plan repo-relative so it resolves in either place. ## Documentation layout (two tiers) | Tier | Path | Git | Use | |------|------|-----|-----| | **Durable** | `docs/features/<TICKET-ID>/` | tracked | Design, implementation plans, test checklists — commit when stable | | **WIP** | `docs/plans/<TICKET-ID>/` | gitignored | Agent scratch during write-plan / execute-plan | Infer `<TICKET-ID>` from the branch name (e.g. `PROJ-123`) or ask once if unclear. If your project does not use ticket IDs, use a short kebab-case slug for the feature. **Save new implementation plans to (WIP):** `docs/plans/<TICKET-ID>/<scope>-implementation-plan.md` **Overw