skills.rest
adriangmrraa
adriangmrraaCOMMUNITY
Explore all skills by this author →
GitHub

Spec Architect

Generate and validate SDD v2.0 specification files (.spec.md) for feature planning, refinement, and audit workflows.

Updated Dec 24, 2025
Search Tags:#refinement#specification#requirements#audit#sdd#generate#gherkin
One-click install
npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill spec-architect-adriangmrraa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Spec Architect
Source: https://github.com/adriangmrraa/MultiAgents-Platform-ROI/tree/main/.agent/skills/Spec_Architect
Command: npx skills add https://github.com/adriangmrraa/MultiAgents-Platform-ROI --skill spec-architect-adriangmrraa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity between product requirements and implementation by generating, validating, and versioning specification files (.spec.md) according to the SDD v2.0 standard, ensuring requirements are actionable and testable.

Core Features & Use Cases

  • Spec Generation: Produces dated, versioned spec files in specs/ using a mandatory master template that includes context, KPIs, data schemas, persistence changes, business invariants, stack constraints, and Gherkin acceptance criteria.
  • Refinement Workflow: Analyzes existing specs for ambiguities and missing edge cases, prompts for clarifying technical decisions, and enforces traceability to originating tickets.
  • Audit & Drift Detection: Compares implementation files against the spec to report deviations such as type mismatches, missing validations, or security rule omissions, and recommends corrective actions.
  • Use Case: Product managers and engineers use /specify to create a new feature spec before development, iterate with /refine during planning, and run /audit post-implementation to surface spec drift.

Quick Start

Use the command /specify to generate a new SDD v2.0 specification for a described feature.

Frequently Asked Questions about Spec Architect

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

FAQPage Schema
How do I generate software specification files with Gherkin acceptance criteria?▼

Software specification files with Gherkin acceptance criteria are generated by applying the SDD v2.0 standard to produce structured .spec.md outputs. These files include context, data schemas, business invariants, and version history to ensure requirements are actionable and testable.

What is the best way to audit code for spec drift after feature implementation?▼

Auditing code for spec drift is done by comparing implementation files against the specification to report deviations. This process detects type mismatches, missing validations, and security rule omissions, and then recommends corrective actions to align the code with the spec.

How do I refine existing feature specifications to eliminate ambiguity?▼

Refining feature specifications to eliminate ambiguity involves analyzing existing specs for missing edge cases and prompting for clarifying technical decisions. This workflow enforces traceability to originating tickets to ensure requirements remain actionable during planning.

Can I use SDD v2.0 structured outputs for ticket-driven development?▼

SDD v2.0 structured outputs are designed for ticket-driven development, ensuring traceability between product requirements and implementation. They map data schemas, persistence changes, and stack constraints directly to originating tickets to eliminate ambiguity.

When do I need to create versioned specification files in a code repository?▼

Versioned specification files are needed in a code repository when planning new features to establish a clear, audit-ready baseline. They track persistence changes and business invariants over time, preventing ambiguity between product requirements and implementation.

Related Skills

Explore More Software Engineering Skills→
yi-john-huangyi-john-huang
48

sdd-requirements

Generate EARS-formatted requirements documents with FRs, NFRs, and acceptance criteria.

Community
Advanced
VinedineVinedine
2

c4-audit-system

Audit software system documentation against source code implementations.

Community
Advanced
Ahnd6474Ahnd6474

accelint-ac-to-playwright

Convert acceptance criteria into validated JSON test plans and Playwright spec files.

Community
Advanced
xmx0632xmx0632
1

requirements-analysis

Analyze business requirements and create a software requirements specification.

Community
Intermediate