What problem does it solve? Non-trivial changes in the gokit repository need a written, reviewable contract before any code is touched. This Skill turns a feature, refactor, parity port, or release into a structured plan folder that other skills can execute iteratively, eliminating ad-hoc or untracked planning. ## Core Features & Use Cases - Standardized plan structure: Generates a README overview plus zero-padded, dependency-ordered step files (01-core.md, 02-...) under the gitignored tmp/<plan-name>/ directory. - Baseline-bound rules: Every plan restates gokit's engineering baseline — test-first TDD, acyclic layering, canonical reuse, typed minimal APIs, and no compatibility shims. - Progress tracking: Each step carries a Status field and checkbox acceptance criteria that the apply-plan and apply-step skills read and flip as work lands. - Use Case: When scoping a new storage backend, invoke this Skill to produce tmp/storage-gcs-backend/ with an indexed README and per-layer step files, each mapping to a standalone reviewable change. ## Quick Start Ask the assistant to create a plan for adding a GCS storage backend, and it will write the README and numbered step files under tmp/storage-gcs-backend/.