القائمة
Generador de especificaciones de producto en YAML. Unico proposito: crear, estructurar y validar archivos .yml de historias de usuario. No edita codigo fuente.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skill-spec-product |
| description | Generador de especificaciones de producto en YAML. Unico proposito: crear, estructurar y validar archivos .yml de historias de usuario. No edita codigo fuente. |
| compatibility | Framework agnostic. Works with any tech stack or team structure. |
| metadata | {"author":"leifermendez","version":"4.0.0","tags":"product, spec-driven, user-stories, requirements, product-management, delivery, handoff"} |
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.
| 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.
Before starting any phase, run the spec validator and inspect the project root:
bash references/validate-specs.sh
spec-product/ exists and creates it if missing.feat-XXXX-dd-mm-yy-hh-mm/feat-XXXX.yml inside the most recent folder for contextFolder 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.spec-product/feat-0001-15-05-26-14-30/File Format (inside folder): feat-XXXX.yml (archivo principal)
.yml de una feature deben vivir dentro de su carpeta feat-XXXX-.../.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.ymlAfter completing any phase, run the spec validator:
bash references/validate-specs.sh
Then verify manually:
spec-product/feat-*/ directories created in this phase.feat-XXXX-dd-mm-yy-hh-mm/ formatfeat-XXXX.yml.yml dentro del directorio son YAML validos y no vaciosfeat-XXXX.yml) tiene los campos requeridos: id, type, as_a, i_want, so_that, product, metadata.created_atmetadata.created_at en el archivo principal coincide con el timestamp del directorio (dd-mm-yy-hh-mm)After Phase 05 complete:
spec-product/feat-*/ directories.approved or done.references/phase-01-discovery-and-intake.md and collect requirements.Exit Criteria pass, run Post-phase Verification, then load references/phase-02-prioritization.md.spec-product/ structure and YAML contentsBuild YAML specs that serve as the unambiguous contract between product and engineering.
Expert in Clean Architecture + Domain-Driven Design (DDD). Enforces strict separation of layers: Domain, Application, Infrastructure, Interface. No over-engineering - only essential patterns. Every file must start with a layer documentation comment.
Dead code and legacy pattern detector for any codebase. Identifies unused exports, unreachable code, zombie routes, unused dependencies, deprecated APIs, outdated idioms, and technical debt accumulation. Produces a severity-ranked cleanup report with safe removal recommendations.
Performance bottleneck detector for any codebase. Scans backend, frontend, database, and connection layers for N+1 queries, blocking I/O, missing indexes, render thrashing, bundle bloat, pool exhaustion, Big-O complexity issues, and over-engineering anti-patterns. Produces a severity-ranked audit report with actionable quick wins.
Trigger: security audit, codebase review, technical debt assessment, architecture analysis. Comprehensive audit of any codebase detecting frameworks, languages, architecture patterns, and pain points with pros/cons tables.
Trigger: scan design system, detect CSS architecture, analyze frontend tokens, detect Tailwind, BEM, Atomic Design. Scan projects for design system patterns, component trees, and branding tokens.
Git diff security and risk auditor. Evaluates ONLY changed code (staged, commit range, or patch file). Detects security leaks, data-loss dangers, and dependency risks. Outputs structured YAML. Blocks critical/high findings with mandatory fix actions.