sdd-spec

Create structured SDD delta specifications with RFC 2119 requirements and Given/When/Then scenarios.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-spec-zmynxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-spec
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-spec-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams convert change proposals into structured specifications, reducing ambiguity between requirements, implementation, and testing.

Core Features & Use Cases

  • Delta Specification Writing: Creates structured SDD specifications that describe added, modified, removed, and renamed system behaviors.
  • Scenario Definition: Produces testable Given/When/Then scenarios with clear requirements and acceptance criteria.
  • Use Case: Help an engineering team turn a feature proposal into implementation-ready specifications while preserving existing behavior and guiding downstream design and task planning.

Quick Start

Use the sdd-spec skill to create a delta specification for the requested software change proposal.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I write structured software specifications from engineering proposals?

Structured software specifications are created by converting engineering proposals into delta specifications using spec-driven development practices. This process defines added, modified, and removed system behaviors into implementation-ready requirements.

What is spec-driven development and when do I need it for software architecture?

Spec-driven development is a practice of creating precise software change specifications to reduce ambiguity between requirements, implementation, and testing. You need it when engineering teams require structured documentation for new or modified system capabilities.

How do I create testable scenarios with Given When Then for software requirements?

Testable Given When Then scenarios are generated as part of the specification writing process to define clear requirements and acceptance criteria. These scenarios map directly to system behaviors outlined in the engineering change proposal.

Does spec-driven development require RFC 2119 requirement language?

Spec-driven development workflows utilizing this approach require RFC 2119 requirement language to enforce strict specification semantics. This standardizes requirement definitions within the delta specification and artifact persistence conventions.

What is the best way to document modified system behaviors without losing existing functionality?

The best way to document modified behaviors without losing existing functionality is creating delta specifications that explicitly describe added, modified, removed, and renamed system behaviors while preserving current operations through structured requirements.

Can I use this specification process for downstream task planning and design?

The specification process is designed to guide downstream design and task planning by producing implementation-ready specifications. The generated artifacts serve as the foundation for subsequent software architecture and engineering workflows.