skills.rest
pgermishuys
pgermishuysCOMMUNITY
Explore all skills by this author →
Website𝕏@pgermishuysGitHub

sdd-specification

Automates creation and validation of formal feature specifications with YAML frontmatter and quality checklists.

143|10|Updated Feb 24, 2026
Search Tags:#specification#requirements#validation#edge-cases#feature#quality-checks
One-click install
npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-specification-pgermishuys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-specification
Source: https://github.com/pgermishuys/opencode-weave/tree/main/examples/config/github-speckit/skills/sdd-specification
Command: npx skills add https://github.com/pgermishuys/opencode-weave --skill sdd-specification-pgermishuys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature specification often suffers from ambiguity and missed requirements. This Skill provides a standardized template and clear quality checks to ensure complete, testable specs that guide implementation.

Core Features & Use Cases

  • Standardized feature specification format with mandatory sections (Header, User Scenarios, Functional Requirements, Success Criteria, Edge Cases, Key Entities, Assumptions) and a built-in validation checklist.
  • Quality validation guidelines that enforce testability, clarity, and alignment with governance rules for consistent reviews.
  • Clear instruction set for writing requirements and acceptance criteria to support reliable development, testing, and stakeholder alignment.

Quick Start

Create a new feature spec by following the template and filling in the header, scenarios, FRs, success criteria, and edge cases.

Frequently Asked Questions about sdd-specification

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

FAQPage Schema
How do I create a feature specification with clear functional requirements and edge cases?▼

A complete feature specification requires a YAML frontmatter header for name and description, followed by structured sections for user scenarios, functional requirements, success criteria, and edge cases. This ensures testable requirements and alignment across stakeholders.

What is the best way to validate feature specifications for testability and ambiguity?▼

Validating feature specifications involves applying built-in quality checks that enforce testability, clarity, and alignment with governance rules. This ensures complete, testable specs that guide implementation and reliable development.

How do I ensure my requirements specification covers all edge cases and success criteria?▼

Ensure requirements specification coverage by using a standardized template with dedicated sections for edge cases and success criteria. A built-in validation checklist verifies all functional requirements are testable.

Can I use a structured template for writing product feature specs without missing key entities?▼

Yes, a structured template for product feature specs mandates sections for key entities, assumptions, and user scenarios. This prevents missed requirements and ensures stakeholders align on reliable development and testing parameters.

What sections are mandatory in a formal feature specification to pass quality checks?▼

Mandatory sections in a formal feature specification include the header, user scenarios, functional requirements, success criteria, edge cases, key entities, and assumptions. These sections satisfy the validation checklist for testable requirements.

Related Skills

Explore More Product & Management Skills→
686f6c61686f6c61
105

write-prd

Generate a Product Requirements Document with problem statement, solution, user stories, and acceptance criteria.

Community
Intermediate
flybirdxxflybirdxx

plan-test-writer

Convert feature implementation plans into executable test cases using Gemini and Claude.

Community
Intermediate
Athena-Git-GroupAthena-Git-Group

athena-carry-on-engineering-plan

Coordinate multi-phase engineering workflows with dependency tracking and review feedback.

Official
Advanced
intelligentcode-aiintelligentcode-ai
35

requirements-engineer

Capture and formalize stakeholder needs into testable requirements with traceability.

Official
Basic