What problem does it solve? Turning a decided change proposal into an implementation plan often produces vague, unverifiable, or misordered tasks that an executing agent cannot complete unaided. This Skill converts a change's proposal, design, and spec deltas into a short, dependency-ordered tasks.md where every checkbox names exact files, an observable outcome, and an automated verification. ## Core Features & Use Cases - Verifiable checkbox authoring: Every checkbox names the exact files it creates or modifies, an observable outcome, and a verify: clause pointing to a test, command assertion, file-content check, automated browser test, or openspec validate. - Testability discipline: Behavior-changing checkboxes must name the specific test file and test case; prose-only edits carry a [prose-exempt: <reader>] marker; render-affecting work must name a browser-engine test. - Dependency ordering and terminal state: Checkboxes are ordered so each relies only on earlier ones, and changes too large for the budget return NEEDS SPLIT with a proposed decomposition into child changes. - Use Case: After deciding a change's proposal and design in an OpenSpec-based planning flow, run this Skill to produce openspec/changes/<change-id>/tasks.md that an implementing agent can execute and self-verify without human intervention. ## Quick Start Ask the agent to run the ptp-writing-plans skill on the current change to write its tasks.md implementation plan.
