sdd-spec

Generate delta specs for affected domains from change proposals.

1.3k|159|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/Gentleman-Programming/agent-teams-lite/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write specifications as delta-ready artifacts that capture added, modified, or removed behaviors from change proposals, enabling precise collaboration and traceability.

Core Features & Use Cases

  • Identify affected domains from a proposal and group changes by domain.
  • Read existing specs and generate delta specs per domain, or a full spec for new domains.
  • Return a structured summary with artifacts and next steps, ready for design and task planning.

Quick Start

Execute the delta-spec writer against the current change proposal to generate delta specs for impacted domains and persist artifacts according to the configured artifact_store.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I write delta specifications for existing system domains?

To write delta specifications, identify affected domains from a change proposal, consolidate existing specifications, and generate delta specs for added, modified, or removed behaviors per domain.

What is a delta spec and how does it handle change proposals?

A delta spec captures added, modified, or removed behaviors from a change proposal, grouping changes by impacted domain to produce structured artifacts ready for design handoff.

How do I generate full specifications for new domains instead of delta updates?

For new domains, generate a full specification instead of a delta update by configuring the artifact_store policy as engram, openspec, or none to persist the artifacts.

Do I need testable scenarios for requirements in my delta specs?

Yes, delta specs must adhere to RFC 2119-based requirements and ensure every change includes testable scenarios to guarantee precise collaboration and traceability for design handoff.

Can I use OpenSpec or Engram for artifact storage when writing specifications?

Yes, you can use OpenSpec or Engram for artifact storage. The Skill supports an artifact_store policy accepting engram, openspec, or none to persist delta specs and full specifications.

What is the best way to group changes by domain from a proposal?

The best way to group changes by domain is to process the change proposal through a tool that identifies affected domains, reads existing specs, and writes per-domain delta specs to a change folder.