What problem does it solve? Writing the technical plan for a work unit often produces inconsistent documents: technology choices without a confirmed basis, business rules leaking into technical sections, and optional artifacts generated or skipped at random. This Skill standardizes how plan.md and its auxiliary files (data-model.md, research.md, contracts/, ui/) are authored in a spec-driven development workflow. ## Core Features & Use Cases - Structured plan.md authoring: Defines the expected sections (stack, technical decisions, data model, contracts, interface, testing strategy, documentation impact) and what belongs in each. - Decision provenance enforcement: Requires every settled technology choice to cite a concrete confirmation basis (code in use, user statement, AGENTS.md) recorded in research.md, escalating unconfirmed choices as gaps. - Explicit optional-artifact decisions: Forces a recorded generate-or-waive verdict for each canonical optional (data-model.md, research.md, contracts/, ui/) with a one-line reason. - Use Case: When planning a new backend module, use this Skill to produce a plan.md that traces from the current code state, documents tradeoffs in research.md, specifies the REST API in contracts/*.openapi.yaml, and records deliberate documentation drift. ## Quick Start Ask the AI to author the plan.md and supporting technical artifacts for the current spec unit following the plan-authoring standard.
