Generate component-level SDD specifications from a Reversa PRD.
npx skills add https://github.com/sandeco/reversa --skill reversa-spec-sdd-sandeco
Please help me install this Agent Skill. Skill: reversa-spec-sdd Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-spec-sdd Command: npx skills add https://github.com/sandeco/reversa --skill reversa-spec-sdd-sandeco
Converts PRDs into complete, traceable Spec-Driven Development (SDD) specs for AI-assisted implementation, reducing ambiguity and misalignment when moving from product requirements to executable agent-ready contracts.
prd.md into logical components, one spec per component, based on the PRDβs scope, personas, and acceptance criteria._reversa_sdd/sdd/ and finishes with a handoff to /reversa-forward, enabling the next step of the Reversa workflow.Run /reversa-spec-sdd after /reversa-new so the skill reads _reversa_sdd/prd.md and generates _reversa_sdd/sdd/<componente>.md with quality scores.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into testable SDD specs, you decompose product scope into logical components and generate one structured Spec-Driven Development markdown file per component with explicit acceptance criteria and quality scores.
Spec-driven development decomposition breaks product requirements into logical parts, drafting LLM-ready functional specs that define what should happen rather than how, reducing ambiguity for AI-assisted implementation.
SDD specs are scored 0β100 against completeness, testability, clarity, scope, and edge-case coverage, iterating automatically up to defined limits to ensure agent readiness before handoff.
Yes, you can generate a single SDD spec from user-provided input for standalone evaluation, or apply the skill within pipeline execution by reading a standard prd.md file to output multiple component specs.
The best way to structure acceptance criteria in an SDD markdown file is using an RFC-Pragmatic structure with required RF IDs, explicit acceptance criteria, and π‘ PLANJADO tagging for traceable agent-ready contracts.
After generating SDD specs, the workflow finishes with a handoff to /reversa-forward, enabling the next step of the Reversa pipeline by writing specs under the designated sdd directory for downstream execution.
GeneralJerelDraft structured PRDs from problem statements for product teams.
Pabloprogramador23Decomposes PRD files into scored, component-based SDD specs with gap analysis.
SumitvedpathakGenerate structured checklists to validate requirements documentation clarity and completeness.
CODE-SAURABHConvert vague product ideas and bug reports into implementation-ready specifications.