What problem does it solve? Turning a feature specification into a concrete implementation plan requires investigating the codebase, resolving design unknowns, and producing consistent planning documents, which is slow and error-prone when done manually. ## Core Features & Use Cases - Phased Plan Generation: Produces plan.md with Summary, Project Structure, and Constitution Check, then Phase 0 research and Phase 1 design artifacts (data-model.md, contracts/). - Size-Aware Budgeting: Reads the recorded change size from .spec-context.json and trims the plan for simple changes, skipping data-model.md and folding decisions into a Key Decisions note. - Extension & Node Hooks: Runs spec-kit extension hooks from .specify/extensions.yml and project node hooks from .specify/companion.yml without ever failing the host command. - Use Case: After writing a feature spec with spec-kit, run this step to investigate the codebase, record design decisions in research.md, and emit contracts that copy the spec's Verbatim Constraints exactly. ## Quick Start Ask the assistant to run the speckit companion plan step for the current feature so it produces plan.md, research.md, and the design artifacts in the feature directory.
