What problem does it solve?
This Skill solves the problem of inconsistent, incomplete, or context-starved implementation work that occurs when engineers receive a feature spec without a clear, structured plan for execution. It ensures all necessary context, file paths, test steps, and code quality guardrails are documented upfront to reduce rework and speed up delivery.
Core Features & Use Cases
- Structured Task Decomposition: Breaks down complex specs into bite-sized, independently testable tasks with explicit file creation/modification paths, code snippets, and test commands.
- Best Practice Enforcement: Embeds core development principles like DRY, YAGNI, and TDD directly into every task to ensure consistent, maintainable, and well-tested code.
- Use Case: For example, when building a new multi-currency payment processing module for the Ventura Dental clinic system, this Skill generates a full plan that tells the engineer exactly which backend API routes and frontend components to modify, what test cases to write, and how to commit changes, even if they have no prior context with the codebase.
Quick Start
Use the writing-plans skill to generate a complete, step-by-step implementation plan for the new patient billing feature described in the attached product specification.