create-quiver 0.9.1 → 0.12.0

package/specs/quiver-v22-guided-ai-workflow/slices/slice-00-spec-foundation/slice.json

@@ -0,0 +1,51 @@
+{
+  "slice_id": "slice-00-spec-foundation",
+  "ticket": "QUIVER-22-00",
+  "type": "docs",
+  "title": "Spec foundation and guided workflow planning artifacts",
+  "objective": "Create the complete documentation foundation for the guided AI workflow spec.",
+  "description": "Publish the spec, status, evidence report, execution plan, PR body, slice definitions, and handoffs before product implementation starts.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "guided-ai-workflow-spec-foundation",
+    "branch_name": "feature/QUIVER-22-00-guided-ai-workflow-spec-foundation"
+  },
+  "files": [
+    "specs/quiver-v22-guided-ai-workflow/**"
+  ],
+  "depends_on": [],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "slice-00 must land before every other slice.",
+  "must": [
+    "Create SPEC.md.",
+    "Create STATUS.md.",
+    "Create EVIDENCE_REPORT.md.",
+    "Create EXECUTION_PLAN.md.",
+    "Create pr.md.",
+    "Create slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md for every slice.",
+    "Avoid product code changes."
+  ],
+  "not_included": [
+    "Implementing commands.",
+    "Changing README or CHANGELOG.",
+    "Running AI providers.",
+    "Creating commits automatically."
+  ],
+  "acceptance": [
+    "Spec folder exists under specs/quiver-v22-guided-ai-workflow.",
+    "Mandatory slice-00 exists.",
+    "Every slice has slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "Every slice.json parses successfully.",
+    "No product code is modified."
+  ],
+  "tests": [
+    "git diff --check",
+    "find specs/quiver-v22-guided-ai-workflow -name \"slice.json\" -print -exec node -e \"JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8'))\" {} \\;"
+  ],
+  "estimated_hours": 2,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-21T11:16:22-0300"
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-01-docs-source-of-truth-sync/CLOSURE_BRIEF.md

@@ -0,0 +1,31 @@
+# CLOSURE BRIEF - slice-01: Documentation source-of-truth sync
+
+## Resumen de lo realizado
+
+Se sincronizaron los documentos raiz con la version `0.10.0` y con el estado real de los specs v20, v21 y v22.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Docs sincronizadas con `0.10.0`.
+- [x] Flujo actual y futuro diferenciados.
+- [x] No se modifico codigo de producto.
+
+## Cambios relevantes
+
+- `README.md`: corregida la seccion de informacion confirmada/pendiente para reflejar `0.10.0`.
+- `README_FOR_AI.md`: agregado recordatorio de que v20/v21 estan completos y v22 sigue planificado.
+- `CHANGELOG.md`: agregada entrada `0.10.0`.
+- `ROADMAP.md`: alineado v20/v21 con los specs reales completados y v22 como plan activo.
+- `BACKLOG.md`: promovida la entrada de orquestacion al spec v22 y marcada la parte diferida como dependiente de demanda real.
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+La documentacion todavia mantiene una nota de deuda sobre `engines` de Node y scripts legacy del repo fuente; no forman parte de esta slice.
+
+## Recomendaciones futuras
+
+Ejecutar `slice-02-prepare-command-diagnostics` para agregar el primer comando guiado del workflow.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-01-docs-source-of-truth-sync/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-01: Documentation source-of-truth sync
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-01-docs-source-of-truth-sync
+**Tipo:** docs
+
+## Contexto
+
+Quiver depende de sus docs para onboarding de agentes. Hay drift entre la version publicada `0.10.0` y algunos documentos raiz.
+
+## Objetivo
+
+Sincronizar la documentacion antes de implementar mas automatizacion.
+
+## Alcance
+
+- `README.md`
+- `README_FOR_AI.md`
+- `CHANGELOG.md`
+- `ROADMAP.md`
+- `BACKLOG.md`
+- traducciones relevantes bajo `i18n/es/`
+
+## Criterios de aceptacion
+
+- No quedan contradicciones conocidas con `0.10.0`.
+- El flujo actual se describe como actual.
+- El guided workflow nuevo se describe como plan futuro, no como funcionalidad ya disponible.
+- No se modifica codigo de producto.
+
+## Plan tecnico resumido
+
+Leer los documentos raiz, comparar contra package/version y specs v20/v21, y corregir solo texto desactualizado o ambiguo.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `package.json`, `README_FOR_AI.md`, `SPEC.md` de v20 y v21.
+2. Actualizar README y changelog.
+3. Limpiar roadmap/backlog para evitar señales viejas.
+4. Alinear i18n si aplica.
+5. Ejecutar validaciones documentales y tests acotados.
+
+## Restricciones
+
+- No tocar CLI ni tests salvo que una referencia documental rota lo requiera.
+- No cambiar version de paquete.
+
+## Riesgos
+
+- Presentar comportamiento futuro como disponible.
+- Eliminar contexto util del roadmap/backlog.
+
+## Checklist de finalizacion
+
+- [ ] Docs sincronizadas.
+- [ ] Drift de version corregido.
+- [ ] Futuro vs actual queda claro.
+- [ ] `git diff --check` pasa.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-01-docs-source-of-truth-sync/slice.json

@@ -0,0 +1,55 @@
+{
+  "slice_id": "slice-01-docs-source-of-truth-sync",
+  "ticket": "QUIVER-22-01",
+  "type": "docs",
+  "title": "Documentation source-of-truth sync",
+  "objective": "Synchronize Quiver's visible documentation with the current 0.10.0 AI-first workflow before behavior changes.",
+  "description": "Update README, CHANGELOG, ROADMAP, BACKLOG, and AI guidance so future agents do not plan from stale information.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "guided-ai-docs-sync",
+    "branch_name": "feature/QUIVER-22-01-guided-ai-docs-sync"
+  },
+  "files": [
+    "README.md",
+    "README_FOR_AI.md",
+    "CHANGELOG.md",
+    "ROADMAP.md",
+    "BACKLOG.md",
+    "i18n/es/README.md",
+    "i18n/es/README_FOR_AI.md"
+  ],
+  "depends_on": [
+    "slice-00-spec-foundation"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Documentation source of truth must be corrected before later slices depend on it.",
+  "must": [
+    "Remove stale references that contradict package version 0.10.0.",
+    "Explain the guided AI workflow as planned work, not already shipped behavior.",
+    "Keep README_FOR_AI aligned with README guidance.",
+    "Mark unresolved decisions explicitly instead of inventing them."
+  ],
+  "not_included": [
+    "Implementing commands.",
+    "Changing package version.",
+    "Publishing npm."
+  ],
+  "acceptance": [
+    "Root docs no longer say package.json is still 0.9.0.",
+    "CHANGELOG includes the 0.10.0 release status or clearly marks the missing entry as resolved.",
+    "ROADMAP and BACKLOG do not present shipped v20/v21 behavior as merely future work.",
+    "README explains current AI-first commands and clearly separates future guided workflow work.",
+    "No product code is modified."
+  ],
+  "tests": [
+    "git diff --check",
+    "node --test tests/commands/analyze.test.js tests/commands/ai-plan.test.js tests/commands/ai-pr.test.js"
+  ],
+  "estimated_hours": 3,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 1,
+  "completed_at": "2026-05-21T11:21:08-0300"
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-02-prepare-command-diagnostics/CLOSURE_BRIEF.md

@@ -0,0 +1,30 @@
+# CLOSURE BRIEF - slice-02: Prepare command and setup diagnostics
+
+## Resumen de lo realizado
+
+Se implemento `npx create-quiver prepare` como comando de diagnostico no destructivo con soporte de `--dry-run`, preflight opcional de provider, guia de GitHub CLI, validacion de identidad SSH y siguientes comandos seguros.
+
+## Validacion contra criterios de aceptacion
+
+- [x] `prepare --dry-run` no escribe.
+- [x] Diagnosticos implementados.
+- [x] Guia cross-platform cubierta.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/commands/prepare.js`
+- `tests/commands/prepare.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+El comando reporta herramientas faltantes como guia y no como bloqueo duro. Esto es intencional para mantener `prepare` seguro y util en proyectos parcialmente configurados.
+
+## Recomendaciones futuras
+
+Conectar `prepare` con el refresco de contexto de `slice-03` para que el onboarding de IA quede mas completo.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-02-prepare-command-diagnostics/EXECUTION_BRIEF.md

@@ -0,0 +1,57 @@
+# EXECUTION BRIEF - slice-02: Prepare command and setup diagnostics
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-02-prepare-command-diagnostics
+**Tipo:** feature
+
+## Contexto
+
+El usuario necesita un primer comando seguro que le diga si el proyecto esta listo para trabajar con IA.
+
+## Objetivo
+
+Agregar un comando de preparacion guiada con diagnosticos claros y modo dry-run.
+
+## Alcance
+
+- Registrar el comando en el CLI.
+- Agregar `prepare`.
+- Reutilizar checks existentes de doctor, provider preflight y GitHub preflight donde convenga.
+- Reportar herramientas faltantes y proximos pasos.
+
+## Criterios de aceptacion
+
+- `prepare --dry-run` no escribe archivos.
+- `prepare` informa checks ejecutados y proximos pasos.
+- Faltantes de `gh`, auth, provider CLI o SSH se explican con guia para macOS, Linux y Windows.
+- No se instalan herramientas ni se modifica SSH sin autorizacion explicita.
+
+## Plan tecnico resumido
+
+Crear un comando fino que orqueste checks existentes y produzca un reporte humano. Mantener escritura deshabilitada en dry-run y evitar automatizaciones destructivas.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar parser de `src/create-quiver/index.js`.
+2. Crear `commands/prepare.js`.
+3. Componer checks existentes.
+4. Agregar salida clara para success/warn/fail.
+5. Cubrir dry-run y faltantes con tests.
+
+## Restricciones
+
+- No refrescar todavia docs de contexto profundas.
+- No crear specs.
+- No crear commits.
+
+## Riesgos
+
+- Duplicar logica de doctor.
+- Hacer que prepare parezca que instala herramientas cuando solo guia.
+
+## Checklist de finalizacion
+
+- [ ] Comando registrado.
+- [ ] Dry-run cubierto.
+- [ ] Guia cross-platform cubierta.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-02-prepare-command-diagnostics/slice.json

@@ -0,0 +1,57 @@
+{
+  "slice_id": "slice-02-prepare-command-diagnostics",
+  "ticket": "QUIVER-22-02",
+  "type": "feature",
+  "title": "Prepare command and setup diagnostics",
+  "objective": "Add a guided preparation command that tells users whether the project is ready for AI-assisted work.",
+  "description": "Create the safe first command for project preparation: analysis, diagnostics, missing-tool guidance, dry-run, and next-step reporting.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "guided-prepare-diagnostics",
+    "branch_name": "feature/QUIVER-22-02-guided-prepare-diagnostics"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/prepare.js",
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/lib/ai/preflight.js",
+    "src/create-quiver/lib/ai/github.js",
+    "src/create-quiver/lib/init-layout.js",
+    "tests/commands/prepare.test.js",
+    "tests/lib/doctor.test.js"
+  ],
+  "depends_on": [
+    "slice-01-docs-source-of-truth-sync"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This establishes the public entrypoint used by later workflow slices.",
+  "must": [
+    "Add a dry-run mode that writes nothing.",
+    "Report project readiness, missing docs, missing tools, provider CLI availability, gh availability, gh auth, and SSH alias guidance.",
+    "Support macOS, Linux, and Windows guidance.",
+    "Print clear next commands.",
+    "Avoid installing tools or editing credentials automatically."
+  ],
+  "not_included": [
+    "Refreshing rich context docs.",
+    "Persisting approvals.",
+    "Creating specs or worktrees."
+  ],
+  "acceptance": [
+    "prepare dry-run reports planned checks and writes nothing.",
+    "prepare reports missing gh with OS-specific guidance.",
+    "prepare reports missing provider CLI with actionable guidance.",
+    "prepare does not install tools or edit SSH config.",
+    "prepare recommends the next safe command after success."
+  ],
+  "tests": [
+    "node --test tests/commands/prepare.test.js tests/lib/doctor.test.js tests/lib/ai-github.test.js tests/lib/ai-providers.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-21T11:28:26-0300"
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-03-context-doc-refresh/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-03: Context documentation refresh
+
+## Resumen de lo realizado
+
+Se mejoro `analyze` para refrescar `docs/AI_CONTEXT.md` con un resumen AI-facing, mantener `docs/PROJECT_MAP.md` como mapa visible y preservar el raw scan interno en `.quiver/scans/PROJECT_SCAN.json`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Contexto AI-facing actualizado.
+- [x] Secretos y ruido excluidos.
+- [x] Supuestos documentados.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/init-docs.js`
+- `src/create-quiver/lib/ai/safety.js`
+- `tests/commands/analyze.test.js`
+- `tests/lib/ai-context-packs.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+`analyze` refresca `docs/AI_CONTEXT.md`; si un equipo lo edita manualmente, debe considerar ese archivo como regenerable o revisar el diff antes de commitear.
+
+## Recomendaciones futuras
+
+Implementar `slice-04` para persistir criterios y planes aprobados, usando el contexto refrescado como input del planner.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-03-context-doc-refresh/EXECUTION_BRIEF.md

@@ -0,0 +1,56 @@
+# EXECUTION BRIEF - slice-03: Context documentation refresh
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-03-context-doc-refresh
+**Tipo:** feature
+
+## Contexto
+
+El analisis actual genera mapa y scan, pero el flujo ideal necesita docs de contexto mas utiles para onboarding de IA con menos tokens.
+
+## Objetivo
+
+Mejorar la generacion/refresco de contexto sin exponer secretos ni archivos ruidosos.
+
+## Alcance
+
+- Mejorar scan/map/contexto visible.
+- Reutilizar exclusiones de seguridad.
+- Reportar supuestos y faltantes.
+- Mantener raw scan en `.quiver/scans/`.
+
+## Criterios de aceptacion
+
+- Contexto AI-facing queda actualizado y conciso.
+- Secretos y ruido quedan fuera.
+- Supuestos y faltantes quedan visibles.
+- Tests cubren exclusiones principales.
+
+## Plan tecnico resumido
+
+Extender el analizador/context writer con filtros seguros y salidas humanas. No inferir dominio si el repo no lo declara.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `runAnalyze`, `project-scan` y context packs.
+2. Definir salidas a refrescar.
+3. Aplicar exclusiones compartidas.
+4. Agregar tests con fixtures de archivos sensibles/ruidosos.
+5. Actualizar docs necesarias.
+
+## Restricciones
+
+- No persistir aprobaciones.
+- No ejecutar proveedores IA.
+
+## Riesgos
+
+- Generar contexto demasiado largo.
+- Ocultar informacion util por filtros demasiado agresivos.
+
+## Checklist de finalizacion
+
+- [ ] Context docs refrescados.
+- [ ] Exclusiones cubiertas.
+- [ ] Supuestos reportados.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-03-context-doc-refresh/slice.json

@@ -0,0 +1,56 @@
+{
+  "slice_id": "slice-03-context-doc-refresh",
+  "ticket": "QUIVER-22-03",
+  "type": "feature",
+  "title": "Context documentation refresh and safe analyzer output",
+  "objective": "Improve project context generation so AI onboarding can use concise, safe, updated docs.",
+  "description": "Enhance analysis/preparation to refresh AI-facing context docs while excluding secrets, generated files, dependency folders, large artifacts, and local AI tool state.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "context-doc-refresh",
+    "branch_name": "feature/QUIVER-22-03-context-doc-refresh"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/project-scan.js",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/ai/context-packs.js",
+    "src/create-quiver/lib/ai/safety.js",
+    "tests/commands/analyze.test.js",
+    "tests/lib/ai-context-packs.test.js"
+  ],
+  "depends_on": [
+    "slice-02-prepare-command-diagnostics"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Context generation feeds planner phases and must be stable first.",
+  "must": [
+    "Refresh useful AI context docs from detected project facts.",
+    "Keep raw scan under .quiver/scans.",
+    "Exclude secrets, env files, build outputs, dependency folders, package caches, and local AI tool state.",
+    "Report assumptions and information that still needs human completion.",
+    "Avoid pretending analysis understands business rules not present in the repo."
+  ],
+  "not_included": [
+    "Planner approval persistence.",
+    "Spec generation changes.",
+    "Provider execution changes."
+  ],
+  "acceptance": [
+    "analyze or prepare refreshes concise AI context docs without exposing unsafe paths.",
+    "docs/PROJECT_MAP.md remains the visible stack and command source.",
+    ".quiver/scans/PROJECT_SCAN.json remains internal raw scan output.",
+    "Generated context includes assumptions and missing information.",
+    "Large/noisy/secret paths are excluded by tests."
+  ],
+  "tests": [
+    "node --test tests/commands/analyze.test.js tests/lib/ai-context-packs.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 7,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-21T11:37:41-0300"
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-04-planner-approval-state/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-04: Planner approval state
+
+## Resumen de lo realizado
+
+Se agrego persistencia de borradores y aprobaciones para fases planner, con bloqueo entre fases, uso de inputs aprobados por defecto y estado visible mediante `npx create-quiver ai approvals`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Fases bloquean inputs no aprobados.
+- [x] Aprobaciones persistidas.
+- [x] Status disponible.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/approvals.js`
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/index.js`
+- `tests/lib/approvals.test.js`
+- `tests/commands/ai-plan.test.js`
+- `tests/commands/ai-plan-spec-phase.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+El estado `stale` depende de timestamps y existencia del archivo fuente. Si se edita manualmente `.quiver/approvals/`, Quiver puede marcar el estado como inconsistente.
+
+## Recomendaciones futuras
+
+Usar las aprobaciones persistidas como base para el ciclo de vida de worktree por spec en `slice-05`.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-04-planner-approval-state/EXECUTION_BRIEF.md

@@ -0,0 +1,56 @@
+# EXECUTION BRIEF - slice-04: Planner approval state
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-04-planner-approval-state
+**Tipo:** feature
+
+## Contexto
+
+El flujo requiere iterar criterios y planes, pero solo usar versiones aprobadas para avanzar.
+
+## Objetivo
+
+Persistir borradores y aprobaciones explicitas para acceptance criteria y technical plan.
+
+## Alcance
+
+- Estado de aprobaciones en `.quiver/`.
+- Comandos o subcomandos de aprobacion.
+- Bloqueos entre fases.
+- Estado legible para el usuario.
+
+## Criterios de aceptacion
+
+- Nada no aprobado alimenta la fase siguiente.
+- Las aprobaciones tienen metadata minima.
+- El usuario puede ver que falta aprobar.
+- La fase spec usa el plan aprobado por defecto.
+
+## Plan tecnico resumido
+
+Crear una capa de approvals reutilizable por `ai plan`, con guardas de fase y tests de transiciones.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `phase-gates.js`.
+2. Definir formato interno de aprobaciones.
+3. Agregar persistencia y lectura.
+4. Integrar comandos.
+5. Agregar tests de bloqueo y avance.
+
+## Restricciones
+
+- No versionar borradores internos salvo decision explicita.
+- No modificar codigo de producto.
+
+## Riesgos
+
+- Que el estado interno y los archivos visibles diverjan.
+- Que una aprobacion vieja alimente una spec nueva.
+
+## Checklist de finalizacion
+
+- [ ] Draft/approved diferenciado.
+- [ ] Bloqueos entre fases cubiertos.
+- [ ] Status legible.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-04-planner-approval-state/slice.json

@@ -0,0 +1,58 @@
+{
+  "slice_id": "slice-04-planner-approval-state",
+  "ticket": "QUIVER-22-04",
+  "type": "feature",
+  "title": "Planner approval state for criteria and technical plans",
+  "objective": "Persist draft and approved planner outputs so each phase consumes an explicit approved input.",
+  "description": "Add approval state for acceptance criteria and technical plans, preventing Quiver from generating specs from unapproved or ambiguous outputs.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "planner-approval-state",
+    "branch_name": "feature/QUIVER-22-04-planner-approval-state"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/phase-gates.js",
+    "src/create-quiver/lib/ai/spec-generator.js",
+    "src/create-quiver/lib/state.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-plan.test.js",
+    "tests/commands/ai-plan-spec-phase.test.js",
+    "tests/lib/approvals.test.js"
+  ],
+  "depends_on": [
+    "slice-03-context-doc-refresh"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Approval state is the contract consumed by spec generation.",
+  "must": [
+    "Persist draft acceptance criteria.",
+    "Persist approved acceptance criteria only after explicit approval.",
+    "Persist draft technical plan.",
+    "Persist approved technical plan only after explicit approval.",
+    "Block spec generation when the approved plan is missing.",
+    "Show status of draft versus approved artifacts."
+  ],
+  "not_included": [
+    "Creating worktrees.",
+    "Executing slices.",
+    "Opening PRs."
+  ],
+  "acceptance": [
+    "Unapproved acceptance criteria cannot feed the technical-plan phase.",
+    "Unapproved technical plans cannot feed spec generation.",
+    "Approvals are stored with timestamp, source file or run id, and phase.",
+    "A status command shows what is draft, approved, missing, or stale.",
+    "Spec generation consumes approved input by default."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-plan.test.js tests/commands/ai-plan-spec-phase.test.js tests/lib/approvals.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-21T11:46:03-0300"
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-05-spec-worktree-lifecycle/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-05: Spec worktree lifecycle
+
+## Resumen de lo realizado
+
+Se agrego el flujo de worktree a nivel spec con comandos `spec start` y `spec status`. Tambien se bloqueo `start-slice` para slices posteriores cuando `slice-00` no esta completada.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Worktree por spec implementado.
+- [x] `slice-00` bloquea slices posteriores.
+- [x] Estado visible.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- Nuevo helper `src/create-quiver/lib/spec-worktrees.js`.
+- Nuevo comando `npx create-quiver spec start <spec-dir>`.
+- Nuevo comando `npx create-quiver spec status <spec-dir>`.
+- `start-slice` valida que `slice-00` este completado antes de iniciar slices posteriores.
+- `feature` y `bugfix` aceptan `main` o `develop` como base branch.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+La limpieza post-merge del worktree no esta incluida en esta slice; queda para `slice-09`.
+
+## Recomendaciones futuras
+
+Mantener `spec close` separado de `spec start/status` para no mezclar creacion segura con limpieza destructiva.