create-quiver 0.10.0 → 0.12.0

package/specs/quiver-v23-guided-flow-productization/slices/slice-02-flow-status-wizard/EXECUTION_BRIEF.md

@@ -0,0 +1,29 @@
+# EXECUTION BRIEF - slice-02: Flow status and next-step wizard
+
+## Objetivo
+
+Implementar un comando que muestre estado, bloqueos y proximo paso seguro.
+
+## Alcance
+
+- Leer estado de `.quiver/`, docs, approvals y specs.
+- Reutilizar doctor/status existentes donde convenga.
+- Imprimir salida breve y accionable.
+
+## Criterios de aceptacion
+
+- No falla con proyectos no inicializados.
+- No llama proveedores.
+- No escribe archivos salvo que una opcion futura lo pida explicitamente.
+- Tiene tests por etapa relevante.
+
+## Restricciones
+
+- No resolver perfiles de agentes en esta slice.
+- No crear specs ni ejecutar slices.
+
+## Checklist de finalizacion
+
+- [ ] Tests por estado.
+- [ ] Docs actualizadas.
+- [ ] Evidencia registrada.

package/specs/quiver-v23-guided-flow-productization/slices/slice-02-flow-status-wizard/slice.json

@@ -0,0 +1,55 @@
+{
+  "slice_id": "slice-02-flow-status-wizard",
+  "ticket": "QUIVER-23-02",
+  "type": "feature",
+  "title": "Flow status and next-step wizard",
+  "objective": "Tell the user where they are in the Quiver workflow and what the next safe command is.",
+  "description": "Add a status/wizard layer that reads project state, docs, approvals, specs, slices, and worktrees to produce actionable next steps.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "flow-status-wizard",
+    "branch_name": "feature/QUIVER-23-02-flow-status-wizard"
+  },
+  "files": [
+    "src/create-quiver/commands/flow.js",
+    "src/create-quiver/lib/**",
+    "src/create-quiver/index.js",
+    "docs/WORKFLOW.md.template",
+    "docs/COMMANDS.md.template",
+    "tests/commands/*.test.js"
+  ],
+  "depends_on": [
+    "slice-01-short-command-and-flow-entrypoint"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Depends on command routing and shared workflow state inspection.",
+  "must": [
+    "Report current workflow stage.",
+    "Report blockers.",
+    "Print the next safe command.",
+    "Handle uninitialized projects gracefully.",
+    "Avoid provider calls."
+  ],
+  "not_included": [
+    "Agent profile management.",
+    "Executing provider commands.",
+    "Creating specs."
+  ],
+  "acceptance": [
+    "Uninitialized project receives init guidance.",
+    "Initialized project without analysis receives analyze/prepare guidance.",
+    "Project with draft criteria receives approval guidance.",
+    "Project with ready slices receives execution guidance.",
+    "Output is concise and copy-pasteable."
+  ],
+  "tests": [
+    "node --test tests/commands/flow*.test.js tests/lib/doctor.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 3,
+  "completed_at": "2026-05-21T14:46:40-0300"
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-03-agent-profiles/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-03: Agent profiles
+
+## Resumen de lo realizado
+
+Se agregaron perfiles reutilizables para `planner`, `executor`, `reviewer` y `researcher` bajo `.quiver/agents/profiles.json`, con comandos `ai agent set/list/show`, validacion de provider y etiquetas de modelo libres.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Perfiles persistidos.
+- [x] Sin secretos.
+- [x] Provider validado.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/agent-profiles.js`: storage, validacion de roles/providers y rechazo de valores con forma de secreto.
+- `src/create-quiver/commands/ai.js`: subcomando `ai agent` y provider default desde perfil para planner.
+- `src/create-quiver/lib/ai/executor.js` y `execution-plan.js`: provider default desde perfil executor.
+- `src/create-quiver/commands/flow.js`: wizard recomienda configurar perfiles antes de planificar.
+- `package.json`, `package.template.json` e `init-layout.js`: script `quiver:ai:agent`.
+- Docs y tests de lib/CLI.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+Los modelos se guardan como etiquetas de configuracion y no se pasan como argumentos al provider hasta definir compatibilidad por CLI en un slice posterior.
+
+## Recomendaciones futuras
+
+Usar estos perfiles en prompts de onboarding y preparacion de contexto desde `slice-04`.

package/specs/quiver-v23-guided-flow-productization/slices/slice-03-agent-profiles/EXECUTION_BRIEF.md

@@ -0,0 +1,29 @@
+# EXECUTION BRIEF - slice-03: Agent profiles
+
+## Objetivo
+
+Permitir que el usuario guarde perfiles reutilizables para planner, executor, reviewer y researcher.
+
+## Alcance
+
+- Estado local bajo `.quiver/`.
+- Comandos para set/list/show.
+- Integracion basica con providers existentes.
+
+## Criterios de aceptacion
+
+- Perfiles persistidos sin secretos.
+- Provider validado.
+- Modelos guardados como etiquetas/configuracion.
+- Tests unitarios y CLI.
+
+## Restricciones
+
+- No prometer disponibilidad real de modelos.
+- No llamar APIs externas.
+
+## Checklist de finalizacion
+
+- [ ] Estado definido.
+- [ ] CLI documentado.
+- [ ] Tests pasan.

package/specs/quiver-v23-guided-flow-productization/slices/slice-03-agent-profiles/slice.json

@@ -0,0 +1,54 @@
+{
+  "slice_id": "slice-03-agent-profiles",
+  "ticket": "QUIVER-23-03",
+  "type": "feature",
+  "title": "Agent profiles for planner, executor, reviewer, and researcher",
+  "objective": "Persist reusable AI agent profiles so users do not repeat provider/model choices in every command.",
+  "description": "Add profile commands and state for planner, executor, reviewer, and optional researcher roles.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "agent-profiles",
+    "branch_name": "feature/QUIVER-23-03-agent-profiles"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/providers.js",
+    "src/create-quiver/lib/**",
+    "docs/COMMANDS.md.template",
+    "tests/lib/*.test.js",
+    "tests/commands/*.test.js"
+  ],
+  "depends_on": [
+    "slice-02-flow-status-wizard"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Defines shared AI state consumed by later prompts and execution commands.",
+  "must": [
+    "Persist planner, executor, reviewer, and researcher profile settings.",
+    "Support provider and model-like free-form fields without hardcoding unstable model names.",
+    "Validate provider support.",
+    "Never store secrets.",
+    "Expose list/show/set commands."
+  ],
+  "not_included": [
+    "Calling providers.",
+    "Plan review behavior.",
+    "Delegated execution."
+  ],
+  "acceptance": [
+    "Profiles can be set, listed, and read.",
+    "Unknown providers are rejected with supported provider guidance.",
+    "Free-form model labels are preserved as configuration, not treated as verified availability.",
+    "No secrets are requested or stored."
+  ],
+  "tests": [
+    "node --test tests/lib/agent-profiles.test.js tests/commands/ai*.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 4,
+  "completed_at": "2026-05-21T14:54:02-0300"
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-04-context-preparation-onboarding/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-04: Context preparation and onboarding
+
+## Resumen de lo realizado
+
+Se productizo el onboarding planner como plantilla empaquetada e index-first, compartida por `ai onboard` y `prepare`. El dry-run ahora reporta fuente del prompt, docs seleccionados y deuda documental.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Prompt index-first.
+- [x] Omitidos reportados.
+- [x] Supuestos y riesgos reportados.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/ai/onboarding-template.js`: plan de contexto, docs seleccionados, deuda, omisiones y prompt planner.
+- `src/create-quiver/commands/ai.js`: `ai onboard --dry-run` muestra prompt source, selected docs y documentation debt.
+- `src/create-quiver/commands/prepare.js`: reporte de onboarding context sin leer todo `docs/`.
+- `docs/AI_ONBOARDING_PROMPT.md.template`: lectura index-first y selectiva.
+- Tests de `prepare`, `ai onboard` y safety.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+La plantilla reporta deuda documental por rutas esperadas aunque algunos proyectos minimalistas pueden no necesitarlas todas; el flujo lo trata como guia, no como bloqueo.
+
+## Recomendaciones futuras
+
+Usar el plan de contexto compartido para prompts mas especificos en criterios, plan tecnico y review.

package/specs/quiver-v23-guided-flow-productization/slices/slice-04-context-preparation-onboarding/EXECUTION_BRIEF.md

@@ -0,0 +1,30 @@
+# EXECUTION BRIEF - slice-04: Context preparation and onboarding
+
+## Objetivo
+
+Convertir el prompt largo de onboarding planificador en una plantilla mantenida por Quiver y una experiencia de preparacion de contexto.
+
+## Alcance
+
+- Templates de onboarding.
+- Comando de prepare/onboard.
+- Reglas index-first y WDD/SDD.
+- Reporte de documentos leidos, omitidos, supuestos y riesgos.
+
+## Criterios de aceptacion
+
+- Prompt generado es mas corto y especifico que el prompt manual.
+- No lee todo `docs/` por defecto.
+- Mantiene trazabilidad documental.
+- Tests pasan.
+
+## Restricciones
+
+- No modificar codigo de producto durante onboarding.
+- No inventar docs inexistentes.
+
+## Checklist de finalizacion
+
+- [ ] Template actualizado.
+- [ ] Dry-run validado.
+- [ ] Tests pasan.

package/specs/quiver-v23-guided-flow-productization/slices/slice-04-context-preparation-onboarding/slice.json

@@ -0,0 +1,59 @@
+{
+  "slice_id": "slice-04-context-preparation-onboarding",
+  "ticket": "QUIVER-23-04",
+  "type": "feature",
+  "title": "Context preparation and onboarding prompt productization",
+  "objective": "Turn the long planner onboarding prompt into a maintained token-efficient Quiver flow.",
+  "description": "Productize context preparation so the planner reads the index first, selects relevant docs, reports assumptions, and avoids unnecessary docs.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "context-preparation-onboarding",
+    "branch_name": "feature/QUIVER-23-04-context-preparation-onboarding"
+  },
+  "files": [
+    "src/create-quiver/commands/prepare.js",
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/ai/**",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "docs/AI_CONTEXT.md.template",
+    "docs/INDEX.md.template",
+    "tests/commands/*.test.js",
+    "tests/lib/*.test.js"
+  ],
+  "depends_on": [
+    "slice-03-agent-profiles"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Touches onboarding templates and AI command behavior.",
+  "must": [
+    "Keep onboarding token-efficient.",
+    "Start from docs/INDEX.md when present.",
+    "Report selected docs and why.",
+    "Avoid reading all docs by default.",
+    "Keep WDD/SDD constraints explicit.",
+    "Preserve no-product-code rule during onboarding."
+  ],
+  "not_included": [
+    "Plan review command.",
+    "Executor prompt generation.",
+    "Delegated execution."
+  ],
+  "acceptance": [
+    "Generated onboarding prompt includes index-first navigation.",
+    "Dry-run shows prompt source and context pack.",
+    "Missing referenced docs are reported as documentation debt.",
+    "Context preparation excludes secrets and noisy paths.",
+    "README snippets remain short."
+  ],
+  "tests": [
+    "node --test tests/commands/prepare.test.js tests/commands/ai-onboard.test.js tests/lib/ai-safety.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 4,
+  "completed_at": "2026-05-21T14:59:09-0300"
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-05-planner-iteration-history/CLOSURE_BRIEF.md

@@ -0,0 +1,31 @@
+# CLOSURE BRIEF - slice-05: Planner iteration history
+
+## Resumen de lo realizado
+
+Se agrego historial versionado para drafts de `acceptance` y `technical-plan`, manteniendo compatibilidad con `draft.md` y `approved.md`. Ahora se puede aprobar una version concreta con `ai approve --version`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Drafts versionados.
+- [x] Aprobacion explicita.
+- [x] Bloqueos preservados.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/approvals.js`: drafts versionados, metadata de version y deteccion de stale cuando se aprueba una version anterior.
+- `src/create-quiver/commands/ai.js` e `index.js`: soporte `ai approve --version <n>`.
+- `tests/lib/approvals.test.js` y `tests/commands/ai-plan.test.js`: multiples drafts y aprobacion por version.
+- Docs de comandos y README actualizados.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+Los archivos legacy `draft.md` y `approved.md` siguen existiendo como punteros/copia para compatibilidad; el historial canonico de drafts vive en `drafts/`.
+
+## Recomendaciones futuras
+
+Usar el historial versionado como entrada de la revision de plan de produccion en `slice-06`.

package/specs/quiver-v23-guided-flow-productization/slices/slice-05-planner-iteration-history/EXECUTION_BRIEF.md

@@ -0,0 +1,29 @@
+# EXECUTION BRIEF - slice-05: Planner iteration history
+
+## Objetivo
+
+Guardar versiones de criterios y planes para que el usuario pueda iterar y aprobar una version concreta.
+
+## Alcance
+
+- Estado de drafts y approvals.
+- Comandos de listado/status.
+- Reglas de bloqueo para fases posteriores.
+
+## Criterios de aceptacion
+
+- Varias iteraciones conviven.
+- La aprobacion apunta a una version concreta.
+- Las fases usan aprobados por defecto.
+- Tests pasan.
+
+## Restricciones
+
+- No crear specs sin plan aprobado.
+- No borrar historial sin comando explicito.
+
+## Checklist de finalizacion
+
+- [ ] Historial persistido.
+- [ ] Estado mostrado.
+- [ ] Tests pasan.

package/specs/quiver-v23-guided-flow-productization/slices/slice-05-planner-iteration-history/slice.json

@@ -0,0 +1,53 @@
+{
+  "slice_id": "slice-05-planner-iteration-history",
+  "ticket": "QUIVER-23-05",
+  "type": "feature",
+  "title": "Planner iteration history for criteria and plans",
+  "objective": "Make acceptance criteria and technical-plan iterations explicit, versioned, and approvable.",
+  "description": "Persist drafts, revisions, approved versions, and status for criteria and technical plans.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "planner-iteration-history",
+    "branch_name": "feature/QUIVER-23-05-planner-iteration-history"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/lib/**",
+    "docs/COMMANDS.md.template",
+    "tests/lib/approvals.test.js",
+    "tests/commands/ai-plan.test.js"
+  ],
+  "depends_on": [
+    "slice-04-context-preparation-onboarding"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Extends planner approval state consumed by later slices.",
+  "must": [
+    "Store multiple criteria drafts.",
+    "Store multiple technical plan drafts.",
+    "Show draft history and approved version.",
+    "Approve a selected version explicitly.",
+    "Block later phases on missing approval."
+  ],
+  "not_included": [
+    "Production plan review.",
+    "Spec generation changes beyond using approved versions."
+  ],
+  "acceptance": [
+    "Multiple drafts can exist without overwriting approved artifacts.",
+    "Status output shows draft, approved, stale, and missing states.",
+    "Technical plan uses approved criteria by default.",
+    "Spec generation blocks without approved plan."
+  ],
+  "tests": [
+    "node --test tests/lib/approvals.test.js tests/commands/ai-plan.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 7,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 4,
+  "completed_at": "2026-05-21T15:03:43-0300"
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-06-production-plan-review/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-06: Production plan review
+
+## Resumen de lo realizado
+
+Se agrego la fase `ai review-plan` para revisar el draft del plan tecnico antes de aprobarlo y antes de generar specs. El review usa el perfil `reviewer`, imprime metadata en dry-run, persiste el resultado en `.quiver/approvals/plan-review/` y bloquea la generacion de spec si el plan tecnico no esta revisado y aprobado.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Review generado.
+- [x] Review persistido.
+- [x] Bloqueos aplicados.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- Nuevo modulo `src/create-quiver/lib/ai/plan-review.js`.
+- Nuevo subcomando `npx create-quiver ai review-plan`.
+- `flow` ahora guia al usuario a revisar el plan tecnico antes de aprobarlo.
+- `ai approvals` muestra el estado `plan-review`.
+- La generacion de spec exige plan tecnico revisado y aprobado.
+- README, templates, generated docs y smokes quedaron alineados con el nuevo paso.
+
+## Pendientes
+
+- La UX futura podria simplificar `--version <n>` para el plan tecnico revisado, pero no bloquea este slice.
+
+## Riesgos remanentes
+
+- El comando usa CLIs locales de proveedores; en automatizacion se debe seguir usando `--dry-run` o mocks para evitar llamadas pagas.
+
+## Recomendaciones futuras
+
+- En `slice-07`, hacer que la experiencia de creacion de spec explique claramente que la entrada valida es el plan tecnico revisado y aprobado.

package/specs/quiver-v23-guided-flow-productization/slices/slice-06-production-plan-review/EXECUTION_BRIEF.md

@@ -0,0 +1,30 @@
+# EXECUTION BRIEF - slice-06: Production plan review
+
+## Objetivo
+
+Formalizar el prompt de revision del plan como una fase antes de crear specs.
+
+## Alcance
+
+- Nuevo comando o fase de review.
+- Prompt mantenido por Quiver.
+- Persistencia de resultado.
+- Bloqueo opcional/obligatorio para spec creation.
+
+## Criterios de aceptacion
+
+- Detecta supuestos fragiles, huecos, ambiguedades y riesgos.
+- No cuestiona el alcance aprobado.
+- No modifica codigo.
+- Tests pasan.
+
+## Restricciones
+
+- No implementar fixes.
+- No abrir nuevas preguntas si la ambiguedad no bloquea; documentar supuestos.
+
+## Checklist de finalizacion
+
+- [ ] Review command probado.
+- [ ] Estado persistido.
+- [ ] Tests pasan.

package/specs/quiver-v23-guided-flow-productization/slices/slice-06-production-plan-review/slice.json

@@ -0,0 +1,54 @@
+{
+  "slice_id": "slice-06-production-plan-review",
+  "ticket": "QUIVER-23-06",
+  "type": "feature",
+  "title": "Production-readiness plan review phase",
+  "objective": "Add a review phase that checks the technical plan for fragile assumptions, missing cases, and ambiguity before spec creation.",
+  "description": "Productize the user's plan-review prompt as a Quiver command and persisted review artifact.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "production-plan-review",
+    "branch_name": "feature/QUIVER-23-06-production-plan-review"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/**",
+    "src/create-quiver/lib/**",
+    "docs/COMMANDS.md.template",
+    "tests/commands/*.test.js",
+    "tests/lib/*.test.js"
+  ],
+  "depends_on": [
+    "slice-05-planner-iteration-history"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Adds a new planner gate consumed by spec generation.",
+  "must": [
+    "Review technical-plan drafts before plan approval and spec generation.",
+    "Report fragile assumptions, uncovered cases, ambiguous criteria, risks, and recommended fixes.",
+    "Do not question approved scope.",
+    "Persist the review result.",
+    "Block spec creation if required review is missing when configured as mandatory."
+  ],
+  "not_included": [
+    "Implementing the plan.",
+    "Creating specs directly.",
+    "Changing provider API integration."
+  ],
+  "acceptance": [
+    "Dry-run prints review prompt metadata.",
+    "Review output is stored as a draft/review artifact.",
+    "The command never modifies product code.",
+    "Spec generation requires reviewed and approved plan state.",
+    "Tests cover missing plan, dry-run, provider failure, and persisted review."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-plan*.test.js tests/lib/approvals.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "completed_at": "2026-05-21",
+  "blocked_reason": null
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-07-spec-create-experience/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-07: Spec create experience
+
+## Resumen de lo realizado
+
+Se agrego `npx create-quiver spec create` como paso explicito para crear specs reales desde el plan tecnico revisado y aprobado. El comando soporta `--dry-run`, valida colisiones antes de escribir, crea todos los artefactos esperados y muestra los proximos comandos seguros.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Inputs aprobados/revisados usados.
+- [x] Artefactos generados.
+- [x] `slice-00` generado.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- Nuevo modulo `src/create-quiver/commands/spec.js`.
+- Nuevo subcomando `spec create`.
+- Nuevo script `quiver:spec:create` en paquetes generados.
+- `flow` ahora recomienda `spec create --dry-run` cuando el plan esta revisado y aprobado.
+- README, templates y docs generadas usan `spec create` como flujo principal.
+- Tests agregados en `tests/commands/spec-create.test.js`.
+
+## Pendientes
+
+- `ai plan --phase spec` sigue existiendo por compatibilidad; en la documentacion principal queda desplazado por `spec create`.
+
+## Riesgos remanentes
+
+- La UX todavia requiere que el usuario conozca o revise el numero de version aprobado del plan tecnico.
+
+## Recomendaciones futuras
+
+- En `slice-08`, usar el spec generado por `spec create` como fuente para prompts minimos de executor.

package/specs/quiver-v23-guided-flow-productization/slices/slice-07-spec-create-experience/EXECUTION_BRIEF.md

@@ -0,0 +1,30 @@
+# EXECUTION BRIEF - slice-07: Spec create experience
+
+## Objetivo
+
+Hacer que la creacion de specs sea un paso claro despues de plan revisado y aprobado.
+
+## Alcance
+
+- UX del comando.
+- Validaciones de inputs aprobados.
+- Generacion de artefactos.
+- Proximo paso sugerido.
+
+## Criterios de aceptacion
+
+- Bloquea si falta aprobacion/review.
+- Crea todos los artefactos esperados.
+- `slice-00` es obligatorio.
+- Tests pasan.
+
+## Restricciones
+
+- No ejecutar slices.
+- No abrir PR.
+
+## Checklist de finalizacion
+
+- [ ] Spec generation validado.
+- [ ] JSON validado.
+- [ ] Tests pasan.