sdd-uc-spec-write

Define SDD specifications with use cases, actors, and acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/franztrierweiler/claude-code-skills --skill sdd-uc-spec-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-uc-spec-write
Source: https://github.com/franztrierweiler/claude-code-skills/tree/main/skills/sdd-uc-spec-write
Command: npx skills add https://github.com/franztrierweiler/claude-code-skills --skill sdd-uc-spec-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables drafting software specifications by use case (UC) following the Spec Driven Development (SDD) methodology, ensuring the specification can be executed by an AI and understood by decision-makers.

Core Features & Use Cases

  • Structured SPEC.md generation by UC with phases: Framing (context, actors, constraints), UC detailing (steps, exceptions, business rules), and complements (non-functional requirements, scope).
  • Support for packaging organization into two-level packages (level 2 Epic, level 1 Feature) and diagrams that reflect UC relationships, enabling scalable planning and development.
  • Facilitation of editing and updating existing SPEC.md (merge changes, preserve traceability, and regenerate diagrams) to maintain a living specification aligned with implementation.

Quick Start

Provide an initial cadrage and UC requirements to begin drafting the SPEC.md.

Frequently Asked Questions about sdd-uc-spec-write

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

FAQPage Schema
How do I write use case specifications for AI-driven software development?

Use case specifications for AI execution are written by outlining actors, acceptance criteria, and detailed UC steps using the Spec Driven Development methodology. This generates a machine-readable SPEC.md that AI agents can reliably implement.

What is Spec Driven Development and how does it structure use cases?

Spec Driven Development (SDD) structures use cases into two-level packages, with level 2 as Epics and level 1 as Features. It details each UC with steps, exceptions, business rules, and IHM references to enable scalable planning.

How do I maintain a living specification document when requirements change?

To maintain a living specification, you can edit and update an existing SPEC.md by merging changes and preserving traceability. The SDD methodology ensures diagrams reflecting UC relationships are regenerated to stay aligned with implementation.

Can I generate Mermaid diagrams automatically from use case relationships?

Yes, Mermaid diagrams for UC relationships are automatically regenerated when drafting or updating the SPEC.md. This visualizes the two-level package organization and use case interactions for decision-makers.

What should a complete software specification include beyond basic use cases?

A complete software specification must include non-functional requirements, framing context, actor constraints, business rules, and management rules. It also requires versioning and changelogs to ensure reliable implementation and historical traceability.

Does Spec Driven Development work for organizing large-scale software features?

Spec Driven Development supports large-scale organization by packaging use cases into two-level structures, separating Epics and Features. This hierarchical approach enables scalable planning and development for complex software systems.