writing-planslisted

# Writing Plans ## Overview Write a comprehensive implementation plan from an approved design. Assume the implementer understands software development but has little context for this repository. Include exact files, steps, verification commands, acceptance criteria, dependencies, and commit points. **Announce at start:** "I'm using the writing-plans skill to create the implementation plan." **Plan location:** Read `2-DESIGN.md` from the active `~/.pi/plans/<YYYY-MM-DD>_<project>_<task>/` folder and write `3-PLAN.md` in the same folder. If no active task folder is known, ask the user for the folder or design file path before proceeding. ## Scope Check If the design covers multiple independent subsystems, suggest breaking it into separate plans — one per subsystem. Each plan should produce working, testable software on its own. ## File Structure Before defining tasks, map out which files will be created or modified and what each one is responsible for. - Design units with clear boundaries and well-defined interfaces. - Prefer smaller, focused files over large files that do too much. - Files that change together should live together. - In existing codebases, follow established patterns. - Include targeted cleanup only when it directly supports the task. This structure informs task decomposition. Each task should produce self-contained changes that make sense independently. ## Pi Task Integration For each implementation task in the plan: 1. Prefer `@tintinweb/pi-task