What problem does it solve? Engineers and subagents often receive vague feature specs and must guess at file paths, test commands, and task ordering, which causes rework and failed handoffs. This Skill turns an approved design into a complete, zero-context execution contract with exact files, code, commands, and verification steps. ## Core Features & Use Cases - Canonical Task Authoring: Writes bite-sized tasks (write failing test, verify failure, implement, verify pass, commit) directly into the repository's OpenSpec tasks.md or a single Beads issue, never a side ledger. - Anti-Pattern Enforcement: Bans placeholders like "TBD" and "add error handling", and scans for vague acceptance criteria, missing rollback notes, hidden reverse dependencies, and mismatched test frameworks. - Self-Review and Optional Subagent Review: Provides a three-step self-review checklist (spec coverage, anti-pattern scan, type consistency) plus a dispatch template for an independent plan-document reviewer subagent. - Use Case: After a design is approved for a new API endpoint, use this Skill to produce an OpenSpec change whose tasks an engineer with zero codebase context can execute step by step, then hand off to the apply execution lane. ## Quick Start Ask the agent to use the writing-plans skill to turn the approved design spec into an executable OpenSpec task breakdown before any code is written.
