create-quiver 0.10.0 → 0.12.0

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.

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

@@ -0,0 +1,56 @@
+# EXECUTION BRIEF - slice-05: Spec worktree lifecycle
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-05-spec-worktree-lifecycle
+**Tipo:** feature
+
+## Contexto
+
+El flujo deseado usa un worktree por SPEC, no una mezcla manual de ramas y worktrees por cada tarea.
+
+## Objetivo
+
+Agregar ciclo de vida de worktree a nivel spec y bloquear ejecucion hasta que `slice-00` este completada.
+
+## Alcance
+
+- Comandos de spec start/status.
+- Seleccion segura de base branch.
+- Reuso seguro de worktree existente.
+- Estado de slices dentro del spec.
+
+## Criterios de aceptacion
+
+- Un spec tiene un worktree dedicado.
+- `slice-00` es obligatoria primero.
+- El estado muestra rama, path y pendientes.
+- No se borra ni pisa trabajo local.
+
+## Plan tecnico resumido
+
+Extraer o extender helpers de lifecycle para soportar spec-level worktrees, manteniendo compatibilidad con start-slice existente.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `lifecycle.js`, `slice.js` y `git.js`.
+2. Definir metadata de spec worktree.
+3. Agregar comando start/status.
+4. Cubrir main/develop y paths con espacios.
+5. Agregar tests.
+
+## Restricciones
+
+- No cerrar worktrees en esta slice.
+- No crear PR en esta slice.
+
+## Riesgos
+
+- Romper `start-slice` existente.
+- Mantener supuestos viejos de `develop` cuando el repo usa `main`.
+
+## Checklist de finalizacion
+
+- [ ] Spec worktree start/status listo.
+- [ ] Base branch segura.
+- [ ] Bloqueo de slice-00 cubierto.
+- [ ] Tests pasan.

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

@@ -0,0 +1,54 @@
+{
+  "slice_id": "slice-05-spec-worktree-lifecycle",
+  "ticket": "QUIVER-22-05",
+  "type": "feature",
+  "title": "Spec worktree lifecycle",
+  "objective": "Formalize one dedicated worktree per spec and make slice-00 the first executable step.",
+  "description": "Add commands and guardrails for starting, inspecting, and managing a spec-level worktree before slice execution.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "spec-worktree-lifecycle",
+    "branch_name": "feature/QUIVER-22-05-spec-worktree-lifecycle"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/lifecycle.js",
+    "src/create-quiver/lib/slice.js",
+    "src/create-quiver/lib/git.js",
+    "src/create-quiver/lib/spec-worktrees.js",
+    "tests/lib/lifecycle.test.js",
+    "tests/commands/spec-worktree.test.js"
+  ],
+  "depends_on": [
+    "slice-04-planner-approval-state"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Spec worktree behavior is required before execution and PR automation.",
+  "must": [
+    "Represent one spec as one worktree and one PR branch.",
+    "Start the spec worktree from the correct base branch.",
+    "Require slice-00 to be first.",
+    "Show spec status, worktree path, branch, and pending slices.",
+    "Avoid deleting or overwriting active worktrees."
+  ],
+  "not_included": [
+    "Post-merge cleanup.",
+    "PR creation.",
+    "Parallel slice execution."
+  ],
+  "acceptance": [
+    "Spec start creates or reuses one dedicated worktree for the spec.",
+    "Spec status shows branch, path, slice-00 status, and pending slices.",
+    "Commands refuse to start later slices before slice-00 is complete.",
+    "Base branch selection supports main or develop without hardcoding the wrong target.",
+    "Existing dirty worktrees are not overwritten."
+  ],
+  "tests": [
+    "node --test tests/lib/lifecycle.test.js tests/commands/spec-worktree.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-06-executor-commit-recovery/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-06: Executor commit and recovery
+
+## Resumen de lo realizado
+
+Se extendio `ai execute-slice` para ejecutar validaciones declaradas, bloquear commits ante fallos y crear un unico commit del slice cuando el usuario habilita `--commit`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Commit unico post-validacion.
+- [x] Fallos bloquean commit.
+- [x] Recovery visible.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- Nuevo flag `--commit` para commit opt-in despues de provider, scope y validaciones.
+- Nuevo flag `--allow-dirty` para permitir dirty worktree preexistente de forma explicita.
+- Validaciones declaradas en `slice.json.tests` se ejecutan antes del commit.
+- Fallos de provider, scope, validacion o commit agregan guia de retry/abort.
+- Tests cubren provider failure, scope violation, validation failure, dirty worktree, commit exitoso y dry-run CLI.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+Los comandos de validacion se ejecutan como comandos del proyecto; deben venir de `slice.json.tests` revisado por el equipo.
+
+## Recomendaciones futuras
+
+Las waves de `slice-07` deben reutilizar este ejecutor en vez de duplicar logica de validacion o commit.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-06-executor-commit-recovery/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-06: Executor commit and recovery
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-06-executor-commit-recovery
+**Tipo:** feature
+
+## Contexto
+
+El executor debe poder modificar codigo dentro del slice, pero el flujo necesita validacion, reporte y un commit por slice.
+
+## Objetivo
+
+Agregar commit opcional post-validacion y recuperacion clara ante fallos.
+
+## Alcance
+
+- Ejecutar slice con contexto acotado.
+- Validar scope.
+- Ejecutar validaciones declaradas.
+- Crear commit unico si corresponde.
+- Reportar retry/abort cuando algo falla.
+
+## Criterios de aceptacion
+
+- No hay commit si falla provider, scope o validaciones.
+- Si todo pasa y commit esta habilitado, se crea un commit.
+- El usuario ve que hacer ante fallos.
+- El worktree sucio se bloquea por default.
+
+## Plan tecnico resumido
+
+Extender `ai execute-slice` y helpers del executor con una etapa posterior a validacion. Mantener commit automation explicita y testeada.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `executor.js` y tests actuales.
+2. Agregar opcion de commit.
+3. Implementar commit message por slice.
+4. Agregar reporte de fallo recuperable.
+5. Cubrir casos happy/error.
+
+## Restricciones
+
+- No ejecutar multiples slices.
+- No abrir PR.
+- No hacer rollback destructivo automatico.
+
+## Riesgos
+
+- Commit accidental con cambios fuera de scope.
+- Mensajes de error poco accionables.
+
+## Checklist de finalizacion
+
+- [ ] Commit opt-in listo.
+- [ ] Scope bloquea commit.
+- [ ] Fallos reportan recovery.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-06-executor-commit-recovery/slice.json

@@ -0,0 +1,57 @@
+{
+  "slice_id": "slice-06-executor-commit-recovery",
+  "ticket": "QUIVER-22-06",
+  "type": "feature",
+  "title": "Executor validation, recovery, and commit per slice",
+  "objective": "Let executor agents modify approved slice scope and create one commit after validation passes.",
+  "description": "Extend slice execution with recoverable failure reporting, retry/abort guidance, optional commit automation, and strict one-slice-one-commit behavior.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "executor-commit-recovery",
+    "branch_name": "feature/QUIVER-22-06-executor-commit-recovery"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/scope.js",
+    "src/create-quiver/lib/git.js",
+    "src/create-quiver/lib/slice-runner.js",
+    "tests/commands/ai-execute-slice.test.js",
+    "tests/lib/ai-executor.test.js",
+    "tests/lib/scope.test.js"
+  ],
+  "depends_on": [
+    "slice-05-spec-worktree-lifecycle"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run in parallel with PR creation only if file scopes remain separate.",
+  "must": [
+    "Keep executor context limited to approved slice data.",
+    "Require a clean worktree before execution unless explicitly overridden by existing safe options.",
+    "Validate changed files against slice scope after execution.",
+    "Run declared validation commands or report why they were skipped.",
+    "Create exactly one commit when validation passes and commit automation is enabled.",
+    "Write or print a recovery report when execution fails."
+  ],
+  "not_included": [
+    "Parallel execution waves.",
+    "PR creation.",
+    "Post-merge cleanup."
+  ],
+  "acceptance": [
+    "Executor refuses to run with dirty worktree by default.",
+    "Executor reports provider failure without hiding local changes.",
+    "Scope violations block commit automation.",
+    "Validation failures block commit automation.",
+    "Successful execution with commit enabled creates one slice commit.",
+    "Retry and abort guidance is shown after failures."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-execute-slice.test.js tests/lib/ai-executor.test.js tests/lib/scope.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-07: Execution waves and safe delegation
+
+## Resumen de lo realizado
+
+Se agrego `ai execute-plan` para imprimir o ejecutar olas de slices. El plan detecta conflictos por archivos, scope desconocido y fuerza fallback secuencial cuando no es seguro paralelizar.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Olas respetan dependencias.
+- [x] Paralelo bloqueado ante conflictos.
+- [x] Dry-run no ejecuta providers.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `execution-plan` ahora incluye `execution_groups`, `fallback_reason` y `unknown_scope_slices`.
+- `parallel_ready` solo queda activo si hay mas de un slice, todos declaran files y no hay overlap.
+- `ai execute-plan --dry-run --commit` imprime comandos de executor por slice.
+- `ai execute-plan --execute --commit` ejecuta slices usando el executor validado y corta ante el primer fallo.
+- La ejecucion real exige `--commit` para preservar un commit por slice.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+La ejecucion paralela real queda representada como grupos `parallel-ready`; la ejecucion local integrada corre de forma controlada para no mezclar agentes en el mismo worktree.
+
+## Recomendaciones futuras
+
+Si se agrega paralelismo real automatico, debe crear worktrees separados por slice antes de llamar providers en paralelo.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-07: Execution waves and safe delegation
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-07-execution-waves-delegation
+**Tipo:** feature
+
+## Contexto
+
+El usuario quiere que Quiver indique que slices van secuenciales y cuales pueden ir en paralelo con agentes ejecutores baratos.
+
+## Objetivo
+
+Agregar ejecucion por olas con fallback seguro a secuencial.
+
+## Alcance
+
+- Planificar olas desde dependencias.
+- Validar conflictos por archivos.
+- Imprimir comandos en dry-run.
+- Ejecutar olas cuando este habilitado.
+- Respetar un commit por slice.
+
+## Criterios de aceptacion
+
+- `slice-00` siempre va primero.
+- Paralelo solo se permite sin conflictos.
+- Scope desconocido cae a secuencial.
+- Una falla corta la ola requerida.
+- Dry-run no llama providers.
+
+## Plan tecnico resumido
+
+Extender `execution-plan` y agregar un comando de execute-plan que use el executor ya validado. Mantener primero modo print-only/dry-run.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `execution-plan.js` y `slice-graph.js`.
+2. Agregar deteccion de conflicto por files.
+3. Agregar comando dry-run.
+4. Integrar ejecucion real con flags explicitos.
+5. Agregar tests de waves y conflictos.
+
+## Restricciones
+
+- No asumir que paralelo es seguro sin files declarados.
+- No abrir PR.
+
+## Riesgos
+
+- Ejecutar dos agentes que toquen la misma zona.
+- Dejar un wave a medio completar sin reporte claro.
+
+## Checklist de finalizacion
+
+- [ ] Olas generadas.
+- [ ] Conflictos detectados.
+- [ ] Dry-run print-only listo.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/slice.json

@@ -0,0 +1,55 @@
+{
+  "slice_id": "slice-07-execution-waves-delegation",
+  "ticket": "QUIVER-22-07",
+  "type": "feature",
+  "title": "Execution waves and safe delegation",
+  "objective": "Execute or print execution waves that respect dependencies, slice-00, and file-scope conflicts.",
+  "description": "Turn the existing execution plan into a guided flow that can run sequential waves and safely identify parallel-ready slices for cheaper executor agents.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "execution-waves-delegation",
+    "branch_name": "feature/QUIVER-22-07-execution-waves-delegation"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/slice-graph.js",
+    "src/create-quiver/lib/slice-runner.js",
+    "tests/lib/ai-execution-plan.test.js",
+    "tests/commands/ai-execute-plan.test.js"
+  ],
+  "depends_on": [
+    "slice-06-executor-commit-recovery"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This slice coordinates multi-slice execution and should not be developed alongside executor changes.",
+  "must": [
+    "Always put slice-00 before all implementation slices.",
+    "Group ready slices into waves.",
+    "Detect file-scope conflicts before suggesting parallel execution.",
+    "Fall back to sequential execution when scope is unknown or conflicting.",
+    "Support a dry-run or print-only mode before real execution.",
+    "Keep one commit per slice when execution is enabled."
+  ],
+  "not_included": [
+    "Provider account billing controls.",
+    "Fully autonomous merge.",
+    "PR creation."
+  ],
+  "acceptance": [
+    "Execution plan shows waves with sequential and parallel groups.",
+    "Unknown or overlapping file scopes force sequential mode.",
+    "Dry-run prints commands and does not call providers.",
+    "Real execution stops the wave on failed required slice.",
+    "Successful slices keep one commit per slice."
+  ],
+  "tests": [
+    "node --test tests/lib/ai-execution-plan.test.js tests/commands/ai-execute-plan.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 9,
+  "status": "completed",
+  "blocked_reason": null
+}