Minu SDD Skill

Guide specification-first software development across four SDD stages with traceable artifacts.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/IDEA-on-Action/Minu-Shared --skill minu-sdd-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Minu SDD Skill
Source: https://github.com/IDEA-on-Action/Minu-Shared/tree/main/claude-skills/minu-sdd
Command: npx skills add https://github.com/IDEA-on-Action/Minu-Shared --skill minu-sdd-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Misalignment between requirements, planning, and implementation often leads to scope creep, rework, and project delays. This skill introduces a Spec-Driven Development (SDD) methodology to ensure clarity and consistency from concept to code.

Core Features & Use Cases

  • 4-Stage Development Process: Guides through defining specifications, planning technical approaches, breaking down tasks, and implementing code, with clear principles for each stage.
  • Single Source of Truth: Establishes specifications as the primary source, ensuring code is a direct artifact of well-defined requirements.
  • Context Preservation: Emphasizes documenting the "why" behind decisions, fostering better understanding and long-term maintainability.
  • AI Collaboration Framework: Provides a structured way for AI to understand project context and contribute effectively at every development stage.
  • Use Case: When starting a new feature, use this skill to ensure you follow the Minu SDD process, from defining user requirements and acceptance criteria to breaking down tasks into manageable units, maintaining alignment with project goals and reducing development friction.

Quick Start

Explain the four stages of the Minu Spec-Driven Development (SDD) process and their primary objectives.

Frequently Asked Questions about Minu SDD Skill

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

FAQPage Schema
What is spec-driven development and why does it reduce rework?

Spec-driven development (SDD) establishes specifications as the single source of truth before implementation, ensuring requirements, planning, and code stay aligned. This prevents scope creep and rework by making expectations explicit and traceable from the start.

How do I structure documentation to maintain alignment between requirements and code?

Organize specifications in docs/ as the canonical source, linking requirements to acceptance criteria, constraints, architecture decisions, and implementation tasks. This traceable structure ensures code artifacts directly reflect well-defined requirements.

What are the four stages of the Minu SDD workflow?

Stage 1 (Specify) defines requirements and acceptance criteria; Stage 2 (Plan) documents architecture decisions; Stage 3 (Break Down) organizes tasks; Stage 4 (Implement) executes with test-driven development, enforcing validation against specifications throughout.

Can I use spec-driven development with AI collaboration?

Yes. SDD provides a structured framework for AI to understand project context and contribute effectively at every stage by maintaining explicit specifications, documented constraints, and clear decision rationale that AI can reference.

When should I apply spec-driven development?

Apply SDD when starting new features or projects where misalignment between requirements and implementation could cause delays or rework. It's especially valuable in complex workflows involving multiple stakeholders or long development cycles.

Does spec-driven development require test-driven development?

Yes. SDD mandates iterative validation and TDD practices during implementation, ensuring code adheres to specifications and acceptance criteria. This enforced testing confirms that specifications are met throughout Stage 4.