What problem does it solve? Teams using the mini-SDD framework need a single authoritative reference explaining how context, spec, plan, and implement steps fit together, how spec.yaml and plan.md files are structured, and how project state determines the next action. ## Core Features & Use Cases - Framework Reference: Explains the full context → spec → plan → implement workflow and the role of each mini-SDD command. - File Format Documentation: Defines the spec.yaml contract (feature, components, constraints), ACID requirement references, plan.md task format, and status lifecycle (draft, ready, in-progress, done). - State Assessment & Hooks: Provides a decision table for determining the next recommended action and documents the pre/post hook configuration system in mini-sdd.config.yml. - Use Case: When a conversation mentions mini-SDD, spec.yaml, or spec-driven development, this skill is loaded so the AI can accurately explain statuses, dependencies, and routing without modifying any project files. ## Quick Start Ask the AI to explain the current state of your mini-SDD project and what command to run next.