ag-referencia-sdd

Streamlines PRD to SPEC to execution and review workflows.

19|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-referencia-sdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ag-referencia-sdd
Source: https://github.com/andregusman-raiz/a-gusman-claude/tree/main/skills/ag-referencia-sdd
Command: npx skills add https://github.com/andregusman-raiz/a-gusman-claude --skill ag-referencia-sdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec Driven Development provides a structured approach to turning product ideas into verifiable implementations by enforcing a PRD→SPEC→Execution→Review workflow.

Core Features & Use Cases

  • PRD and SPEC templates with clear sections
  • Decision logs and risk tracking
  • On-demand reference for planning and review cycles

Quick Start

Ask Claude to apply SDD to your next feature by following the PRD→SPEC→Execution→Review flow.

Frequently Asked Questions about ag-referencia-sdd

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

FAQPage Schema
What is spec-driven development and how does it structure product planning?

Spec-driven development is a structured workflow that turns product ideas into verifiable implementations by enforcing a strict PRD to SPEC to execution to review cycle. It ensures formalized documentation, decision logging, and rollback considerations across the entire feature planning process.

How do I write a PRD and technical spec for a new feature?

You can write a PRD and technical spec by applying dedicated templates with clear sections for decision logs and risk tracking. The spec-driven workflow guides product teams through formalized PRD creation, technical SPEC generation, and structured review cycles.

Can I use spec-driven planning for tracking technical decisions and rollback plans?

Yes, spec-driven planning satisfies requirements for formalized decision logs, plan execution steps, and rollback considerations. It provides on-demand reference templates to track technical decisions and manage risks throughout the feature implementation lifecycle.

What is the best way to manage a product review cycle after spec execution?

The best way to manage a product review cycle is by following the structured PRD to SPEC to execution to review flow. This approach provides on-demand reference for planning and verification, ensuring technical specs are validated against original product requirements.

Does spec-driven development work for product teams without existing documentation templates?

Yes, spec-driven development works without existing templates because it provides built-in PRD and SPEC templates with clear sections. Product teams can start immediately by applying the structured workflow to generate formalized documentation, decision logs, and risk tracking from scratch.

When should I not use a spec-driven workflow for feature planning?

You should avoid spec-driven workflows for rapid prototyping or exploratory phases where formalized PRD and SPEC templates add unnecessary overhead. The structured execution steps and review cycles are designed for product teams handling defined feature planning rather than unstructured ideation.