What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up vague, files are unspecified, and engineers without codebase context get stuck. This Skill produces complete, bite-sized implementation plans that an engineer with zero project context can execute task by task. ## Core Features & Use Cases - Structured Plan Generation: Creates plan documents with a mandatory header, file structure mapping, and tasks broken into 2-5 minute steps following TDD (failing test, verify failure, minimal implementation, verify pass). - Placeholder Enforcement: Forbids vague steps like "add error handling" — every step must contain exact file paths, complete code, and exact commands with expected output. - Self-Review and Handoff: Includes a self-review checklist for spec coverage, placeholder scans, and type consistency, plus an execution handoff offering subagent-driven or inline execution. - Use Case: After brainstorming a feature spec for a KWin script, invoke this Skill to produce a dated plan in docs/agents/plans/ with per-task checkboxes, test code, and coding-convention checklists ready for an implementing agent. ## Quick Start Use the writing-plans skill to turn my spec into a step-by-step implementation plan saved under docs/agents/plans.
