sdd-spec

Convert free-text feature requests and GitHub issues into verifiable technical specifications.

2|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/chichex/skills --skill sdd-spec-chichex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/chichex/skills/tree/main/claude/sdd-spec
Command: npx skills add https://github.com/chichex/skills --skill sdd-spec-chichex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in software development by converting vague feature requests or issues into rigorous, verifiable specifications that align with your project's autonomy contract.

Core Features & Use Cases

  • Verification Verdicts: Automatically assesses whether a feature can be tested via TDD, e2e, or requires human intervention based on your project's current capabilities.
  • Inference Transparency: Forces all implicit assumptions to the surface, allowing you to review and validate every decision before implementation begins.
  • Use Case: When you have a vague GitHub issue like "add dark mode," use this skill to generate a concrete plan that defines exactly how the feature will be implemented, tested, and verified against your existing codebase.

Quick Start

Use the sdd-spec skill to convert the issue number 42 into a verifiable specification.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I convert vague GitHub issues into verifiable technical specifications?

To convert vague GitHub issues into verifiable technical specifications, you can use the sdd-spec skill. It cross-references your free-text feature requests against the project's autonomy contract and maps acceptance criteria to specific verification mechanisms.

What is the best way to identify implicit model assumptions in feature requests?

The best way to identify implicit model assumptions in feature requests is by using the sdd-spec skill. It forces all implicit assumptions to the surface during the conversion process, allowing you to review and validate every decision before implementation begins.

How to generate observable acceptance criteria for GitHub issues?

You generate observable acceptance criteria for GitHub issues by transforming them with the sdd-spec skill. It ensures all resulting acceptance criteria are observable and explicitly mapped to your project's specific verification mechanisms.

Does the sdd-spec skill work with GitHub issues to assess TDD readiness?

Yes, the sdd-spec skill works with GitHub issues to assess TDD readiness. It automatically provides verification verdicts to determine whether a feature can be tested via TDD, e2e, or requires human intervention based on your current project capabilities.

When do I need to map feature requirements to an autonomy contract?

You need to map feature requirements to an autonomy contract when you want to eliminate ambiguity in software development. This process ensures your vague feature requests align with project capabilities and produce rigorous, verifiable specifications.