What problem does it solve? Turning a feature request into an actionable engineering plan is often vague, inconsistent, or overloaded with detail. This Skill produces a complete, standardized plan package up front so senior engineers and stakeholders can review scope, approach, and verification criteria before any code is written. ## Core Features & Use Cases - Two-tier plan structure: Generates a high-level plan.md (executive summary, mermaid diagram, step overview) plus detailed per-step markdown files under docs/plans/<date>_<descriptor>_<hash>/steps/. - Rigor rules built in: Enforces exact file paths, exact commands with expected output, explicit lists of files to inspect/change/forbid, and pass/fail criteria per step. - Confirmation workflow: Drafts the plan first, asks the user for confirmation and revisions, then expands each step into its own file. - Use Case: A staff engineer asks for a plan to add retry logic to a failed-job pipeline. The Skill produces a plan.md with a mermaid flow diagram and four step files covering migration, retry policy, worker wiring, and test verification. ## Quick Start Ask the assistant to create an implementation plan for the feature or change you want to build.
