mini-sdd-guide

Documents the mini-SDD spec-driven development framework workflow, file structure, and hook system.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill mini-sdd-guide-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mini-sdd-guide
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/mini-sdd/skills/mini-sdd-guide
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill mini-sdd-guide-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mini-sdd-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the mini-SDD spec-driven development workflow?▼

mini-SDD enforces specs before code through four steps: /mini-sdd-context captures the project foundation, /mini-sdd-spec writes a spec.yaml contract, /mini-sdd-plan generates a plan.md task list, and /mini-sdd-implement executes the tasks. The cycle repeats per feature.

How do I structure a spec.yaml file for feature specs?▼

A spec.yaml begins with a feature block (name, description, status, requires, dates) followed by components grouping functional requirements under UPPER_SNAKE keys, plus optional constraints. Requirements are referenced by ACID: <feature-name>.<GROUP_KEY>.<ID>.

What do the spec status values draft, ready, in-progress, and done mean?▼

draft means the spec contract exists without a plan, ready means plan.md was generated, in-progress means implementation started, and done means implementation completed. A ready spec with unmet requires dependencies still cannot be implemented.

How do mini-SDD hooks work in the config file?▼

Hooks are plain-text instructions in mini-sdd.config.yml that run before or after each workflow step, keyed as hooks.context.pre, hooks.spec.post, and so on for all four steps. The AI executes them as instructions, not shell scripts, and skips ambiguous hooks without blocking.

When should I not use the mini-sdd-guide skill?▼

Do not use it to create context files, write specs, generate plans, or implement features, since those actions belong to the dedicated mini-sdd-context, mini-sdd-spec, mini-sdd-plan, and mini-sdd-implement skills. The guide is read-only reference material.