PROPOSITO UNICO DE ESTE SKILL: Crear, generar y validar archivos YAML de especificacion de producto. Este skill NO edita, modifica, compila ni genera codigo fuente. Su unico entregable son archivos .yml.
Product Spec-Driven Delivery is a requirements-first workflow where YAML user stories are the single source of truth for product teams. Every feature request traces back to a spec. Every acceptance criterion is verifiable. Every handoff to engineering is complete.
This skill guides product teams through a 5-phase process from raw intake to a validated handoff package. The output of every phase is a set of structured YAML files.
The 5 Phases
| Phase | Name | Tracker / Milestone | Deliverable |
|---|---|---|---|
| 01 | Discovery & Intake | Requirements Package Complete | Spec folders in spec-product/, Stakeholder Map |
| 02 | Prioritization | Roadmap Defined | Prioritized backlog (RICE/WSJF), Quarter roadmap |
| 03 | Specification | Specs Ready for Review | Detailed user stories with acceptance criteria, flows, metrics |
| 04 | Validation | Stakeholder Sign-Off | Approved specs, risk assessment, go/no-go decision |
| 05 | Handoff Package | Engineering Ready | Complete delivery package: specs, context, success criteria |
Rule: Do not begin a phase until the previous phase's Exit Criteria are fully satisfied. The agent executing this skill must verify the checklist before advancing.
Pre-flight Check
Before starting any phase, run the spec validator and inspect the project root:
bash references/validate-specs.sh
- The validator checks if
spec-product/exists and creates it if missing. - If it exists:
- Lists all subdirectories:
feat-XXXX-dd-mm-yy-hh-mm/ - Identifies the most recent by directory name timestamp
- Reads the
feat-XXXX.ymlinside the most recent folder for context - Records the highest sequential ID to continue numbering from there
- Lists all subdirectories:
- Validate: no gaps in ID sequence unless explicitly documented.
Spec Folder & File Naming Convention
Folder Format: spec-product/feat-XXXX-dd-mm-yy-hh-mm/
XXXX: Sequential 4-digit number (0001, 0002, ...). No gaps allowed.dd-mm-yy-hh-mm: Creation timestamp. 2-digit year.- Example:
spec-product/feat-0001-15-05-26-14-30/
File Format (inside folder): feat-XXXX.yml (archivo principal)
- Archivo principal: solo el ID, sin timestamp ni slug descriptivo.
- Se permite incluir archivos YAML adicionales relacionados con la misma feature (por ejemplo, discovery, especificacion, validacion, handoff).
- Todos los archivos
.ymlde una feature deben vivir dentro de su carpetafeat-XXXX-.../. - Example:
spec-product/feat-0001-15-05-26-14-30/feat-0001.ymlspec-product/feat-0001-15-05-26-14-30/feat-0001-discovery.ymlspec-product/feat-0001-15-05-26-14-30/feat-0001-handoff.yml
Post-phase Verification
After completing any phase, run the spec validator:
bash references/validate-specs.sh
Then verify manually:
- List all
spec-product/feat-*/directories created in this phase. - For each directory, verify:
- Directory name follows
feat-XXXX-dd-mm-yy-hh-mm/format - Directory contains at least the archivo principal:
feat-XXXX.yml - Todos los archivos
.ymldentro del directorio son YAML validos y no vacios - El archivo principal (
feat-XXXX.yml) tiene los campos requeridos: id, type, as_a, i_want, so_that, product, metadata.created_at -
metadata.created_aten el archivo principal coincide con el timestamp del directorio (dd-mm-yy-hh-mm) - ID en YAML del archivo principal coincide con el ID del directorio
- Directory name follows
- If any check fails:
- Do NOT proceed to the next phase
- Report the exact failure
- Fix before continuing
Final Verification
After Phase 05 complete:
- Inventory all
spec-product/feat-*/directories. - Verify no orphaned IDs (gaps in sequence without documented reason).
- Verify all P0/P1 stories have status
approvedordone. - Verify timestamps in directory names are chronologically ordered by ID.
- Emit summary:
- Total specs created
- P0 count / P1 count / P2+P3 count
- Timestamp range (first → last)
- Coverage % of acceptance criteria
Quick Start
- Run Pre-flight Check above.
- Load
references/phase-01-discovery-and-intake.mdand collect requirements. - When
Exit Criteriapass, run Post-phase Verification, then loadreferences/phase-02-prioritization.md. - Continue sequentially through all 5 phases, running Post-phase Verification after each.
- After Phase 05, run Final Verification.
Phases
- Phase 01: Discovery & Intake
- Phase 02: Prioritization
- Phase 03: Specification
- Phase 04: Validation
- Phase 05: Handoff Package
References
- Risk Matrix - Risk identification & mitigation
- Tools - Recommended software per phase
- Books - Essential reading for product managers
- Spec Validator - Bash script to validate
spec-product/structure and YAML contents - User Story Templates README - YAML schema & examples
Core Principles
- Este skill genera specs en YAML - No implementa features, no escribe codigo, no crea branches ni hace deploys. Su unico output son archivos .yml.
- Specs are the contract - YAML user stories are the agreement between product and engineering.
- Traceability - Every spec has an ID that follows the feature through design, development, and release.
- Acceptance criteria are non-negotiable - If it cannot be verified, it is not a criterion.
- Start with the problem, not the solution - Specs must articulate the user need before proposing features.
- Decisions are documented - Priority changes, scope cuts, and trade-offs are recorded.
- Handoff is a package, not a meeting - Engineering receives complete context, not a bullet list.
Build YAML specs that serve as the unambiguous contract between product and engineering.