create-quiver 0.9.1 → 0.12.0

package/specs/quiver-v23-guided-flow-productization/pr.md

@@ -0,0 +1,119 @@
+## Title
+
+Quiver v23 - Guided flow productization
+
+## Summary
+
+Productizes the current prompt-driven Quiver workflow into a guided AI-first flow. The goal is to reduce long prompt pasting, guide users through the next safe step, persist planner/executor profiles, version criteria and plan iterations, generate minimal executor prompts, and support safe delegated slice execution.
+
+## Scope
+
+- Short `quiver` command path or documented alias
+- Guided flow/status command
+- Planner, executor, reviewer, and researcher profiles
+- Token-efficient context preparation and onboarding prompt templates
+- Versioned criteria and technical-plan drafts
+- Production-readiness plan review
+- Spec creation from reviewed approved plans
+- Minimal executor prompt generation
+- Delegated slice execution with safe workspaces
+- PR and cleanup flow polish
+- Docs, templates, and smoke coverage
+
+## Files
+
+- `specs/quiver-v23-guided-flow-productization/SPEC.md`
+- `specs/quiver-v23-guided-flow-productization/STATUS.md`
+- `specs/quiver-v23-guided-flow-productization/EVIDENCE_REPORT.md`
+- `specs/quiver-v23-guided-flow-productization/EXECUTION_PLAN.md`
+- `specs/quiver-v23-guided-flow-productization/pr.md`
+- `specs/quiver-v23-guided-flow-productization/slices/**`
+
+Future implementation slices are expected to touch CLI routing, AI commands, provider/profile helpers, prompt templates, approval state, flow status, delegated execution, docs, tests, and smoke scripts as declared by each slice.
+
+## How to Test (DETAILED - REQUIRED)
+
+### Required Environment
+
+- Node.js compatible with the current repo setup. The CI line uses Node 22.
+- npm available locally.
+- Git worktree on `feature/QUIVER-22-guided-ai-workflow`.
+- No real paid provider calls are required for the automated checks.
+
+### Worktree Access
+
+Run from the repo root:
+
+```bash
+git status --short
+git branch --show-current
+```
+
+Expected:
+
+- Worktree is clean before PR creation.
+- Current branch is `feature/QUIVER-22-guided-ai-workflow`.
+
+### Run the Project
+
+Quiver is a CLI package. Use the local binary for inspection:
+
+```bash
+node bin/create-quiver.js --help
+node bin/create-quiver.js flow --json
+```
+
+### Use Cases
+
+- A user asks Quiver what step comes next.
+- A user configures planner and executor agent profiles.
+- A planner onboards from generated context without reading unnecessary docs.
+- A planner generates and revises acceptance criteria.
+- A reviewer checks the technical plan for production readiness.
+- A reviewed approved plan creates spec/slices/handoffs/execution plan/PR body.
+- An executor receives a minimal slice prompt.
+- Quiver delegates or prints safe execution commands for slices.
+- Quiver opens the PR from `pr.md` after checks pass.
+- Quiver closes the spec worktree after merge.
+
+### Technical Verification
+
+Documentation-only `slice-00`:
+
+```bash
+git diff --check
+find specs/quiver-v23-guided-flow-productization -name "slice.json" -print -exec node -e "JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8'))" {} \;
+```
+
+Full validation:
+
+```bash
+node --test tests/**/*.test.js
+npm run smoke:create-quiver
+npm run smoke:guided-workflow
+npm run smoke:tiered-pack
+npm run package:quiver
+npm --cache /private/tmp/quiver-npm-cache pack --dry-run
+```
+
+## Evidence
+
+- `node --test tests/**/*.test.js` passed with 223 tests.
+- `git diff --check` passed.
+- All `slice.json` files under `specs/quiver-v23-guided-flow-productization/` parse successfully.
+- `npm run smoke:create-quiver` passed.
+- `npm run smoke:guided-workflow` passed.
+- `npm run smoke:tiered-pack` passed.
+- `npm --cache /private/tmp/quiver-npm-cache pack --dry-run` passed.
+- Plain `npm pack --dry-run` was blocked by root-owned files in the user's global npm cache; the package was validated with an isolated temporary cache.
+
+## Rollback
+
+Revert the smallest failing slice commit. Since the spec requires one slice per commit, rollback should target the affected slice commit rather than the full PR when possible.
+
+## Risks / Notes
+
+- This spec does not automate PR merge.
+- Real provider CLIs are not called in CI.
+- `quiver` command naming must not confuse package installation.
+- Delegated parallel execution must remain conservative until isolation is proven.

package/specs/quiver-v23-guided-flow-productization/slices/slice-00-spec-foundation/CLOSURE_BRIEF.md

@@ -0,0 +1,30 @@
+# CLOSURE BRIEF - slice-00: Spec foundation
+
+## Resumen de lo realizado
+
+- Se creo la base documental de Quiver v23.
+- Se agregaron spec, status, evidencia, plan de ejecucion, cuerpo de PR y handoffs por slice.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Spec folder creado.
+- [x] `slice-00` creado.
+- [x] Todos los slices tienen `slice.json`, `EXECUTION_BRIEF.md` y `CLOSURE_BRIEF.md`.
+- [x] JSON validado.
+- [x] No se modifico codigo de producto.
+
+## Cambios relevantes
+
+- Nueva carpeta `specs/quiver-v23-guided-flow-productization/`.
+
+## Pendientes
+
+- Implementar `slice-01` en adelante.
+
+## Riesgos remanentes
+
+- Las decisiones sobre el binario corto `quiver` y perfiles de modelo se resolveran en slices posteriores.
+
+## Recomendaciones futuras
+
+- Ejecutar los slices en el orden recomendado por `EXECUTION_PLAN.md`.

package/specs/quiver-v23-guided-flow-productization/slices/slice-00-spec-foundation/EXECUTION_BRIEF.md

@@ -0,0 +1,61 @@
+# EXECUTION BRIEF - slice-00: Spec foundation
+
+**Spec:** quiver-v23-guided-flow-productization
+**Slice:** slice-00-spec-foundation
+**Tipo:** docs
+
+## Contexto
+
+Esta slice sube al repo la base documental del flujo guiado productizado. Es obligatoria y debe ejecutarse antes de cualquier slice de implementacion.
+
+## Objetivo
+
+Crear y validar la estructura completa de spec, slices, handoffs, plan de ejecucion y cuerpo de PR para Quiver v23.
+
+## Alcance
+
+- Crear `SPEC.md`.
+- Crear `STATUS.md`.
+- Crear `EVIDENCE_REPORT.md`.
+- Crear `EXECUTION_PLAN.md`.
+- Crear `pr.md`.
+- Crear `slice.json`, `EXECUTION_BRIEF.md` y `CLOSURE_BRIEF.md` para cada slice.
+
+## Criterios de aceptacion
+
+- La carpeta `specs/quiver-v23-guided-flow-productization/` existe.
+- `slice-00` existe y precede al resto.
+- Cada slice tiene `slice.json`, `EXECUTION_BRIEF.md` y `CLOSURE_BRIEF.md`.
+- Todos los JSON parsean correctamente.
+- No se modifica codigo de producto.
+
+## Plan tecnico resumido
+
+Crear artefactos documentales siguiendo el patron real del repo bajo `specs/`. Mantener `slice-00` como base documental y declarar dependencias para las slices posteriores.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `README_FOR_AI.md`.
+2. Crear estructura `specs/quiver-v23-guided-flow-productization/`.
+3. Agregar archivos top-level de spec.
+4. Agregar cada slice y handoff.
+5. Validar JSON y whitespace.
+6. Preparar commit unico de slice-00.
+
+## Restricciones
+
+- No tocar codigo de producto.
+- No resolver implementacion en esta slice.
+- No abrir PR todavia.
+
+## Riesgos
+
+- Diseñar una spec demasiado amplia sin dependencias claras.
+- Dejar handoffs incompletos para agentes executor.
+
+## Checklist de finalizacion
+
+- [ ] `git diff --check` pasa.
+- [ ] Todos los `slice.json` parsean.
+- [ ] No hay cambios fuera de `specs/quiver-v23-guided-flow-productization/`.
+- [ ] El commit representa solo slice-00.

package/specs/quiver-v23-guided-flow-productization/slices/slice-00-spec-foundation/slice.json

@@ -0,0 +1,51 @@
+{
+  "slice_id": "slice-00-spec-foundation",
+  "ticket": "QUIVER-23-00",
+  "type": "docs",
+  "title": "Spec foundation and guided flow planning artifacts",
+  "objective": "Create the complete documentation foundation for the guided flow productization 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-flow-productization-spec-foundation",
+    "branch_name": "feature/QUIVER-23-00-guided-flow-productization-spec-foundation"
+  },
+  "files": [
+    "specs/quiver-v23-guided-flow-productization/**"
+  ],
+  "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 package behavior.",
+    "Running AI providers.",
+    "Opening a PR."
+  ],
+  "acceptance": [
+    "Spec folder exists under specs/quiver-v23-guided-flow-productization.",
+    "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-v23-guided-flow-productization -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-21T00:00:00-0300"
+}

package/specs/quiver-v23-guided-flow-productization/slices/slice-01-short-command-and-flow-entrypoint/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-01: Short command and flow entrypoint
+
+## Resumen de lo realizado
+
+Se agrego la superficie inicial del flujo guiado: el paquete publica `quiver` como alias del mismo binario `create-quiver`, el CLI acepta `flow`, y el comando imprime el estado inicial y el proximo comando seguro sin escribir archivos ni llamar proveedores.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Compatibilidad `create-quiver`.
+- [x] Decision `quiver` documentada.
+- [x] Entry point seguro.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- `package.json` y `package-lock.json`: alias binario `quiver` y script `quiver:flow`.
+- `src/create-quiver/commands/flow.js`: comando read-only con salida texto y JSON.
+- `src/create-quiver/index.js`: routing, usage y export del comando `flow`.
+- `src/create-quiver/lib/init-layout.js` y `package.template.json`: script generado `quiver:flow`.
+- `README.md`, `README_FOR_AI.md` y `docs/COMMANDS.md.template`: decision de alias y uso de `flow`.
+- `tests/commands/flow.test.js`: cobertura del alias, script generado, read-only behavior y JSON.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+El alias `quiver` es un shortcut local/publicado por el paquete; el bootstrap remoto sigue siendo `npx create-quiver`, porque `npx quiver` podria resolver otro paquete si no existe una instalacion local.
+
+## Recomendaciones futuras
+
+Extender `flow` en `slice-02` para mostrar estado mas completo, blockers y wizard de siguiente paso.

package/specs/quiver-v23-guided-flow-productization/slices/slice-01-short-command-and-flow-entrypoint/EXECUTION_BRIEF.md

@@ -0,0 +1,35 @@
+# EXECUTION BRIEF - slice-01: Short command and flow entrypoint
+
+## Contexto
+
+Quiver actualmente se ejecuta como `npx create-quiver`. El objetivo de producto es que el usuario pueda pensar en `quiver` como la experiencia principal sin romper compatibilidad.
+
+## Objetivo
+
+Crear la superficie inicial de comando corto y flujo guiado.
+
+## Alcance
+
+- Revisar `package.json` y `bin/`.
+- Agregar o documentar el alias `quiver`.
+- Agregar entrypoint inicial de `flow`.
+- Actualizar docs y tests.
+
+## Criterios de aceptacion
+
+- `create-quiver` sigue funcionando.
+- La decision sobre `quiver` queda documentada.
+- El nuevo entrypoint no llama proveedores ni escribe estado inesperado.
+- Tests y `git diff --check` pasan.
+
+## Restricciones
+
+- No implementar perfiles de agentes.
+- No introducir breaking changes.
+
+## Checklist de finalizacion
+
+- [ ] Comando probado.
+- [ ] Docs actualizadas.
+- [ ] Tests actualizados.
+- [ ] Evidencia registrada.

package/specs/quiver-v23-guided-flow-productization/slices/slice-01-short-command-and-flow-entrypoint/slice.json

@@ -0,0 +1,56 @@
+{
+  "slice_id": "slice-01-short-command-and-flow-entrypoint",
+  "ticket": "QUIVER-23-01",
+  "type": "feature",
+  "title": "Short command and guided flow entrypoint",
+  "objective": "Expose a user-friendly guided flow entrypoint while preserving the existing create-quiver CLI.",
+  "description": "Add or document a `quiver` command path and introduce the first flow command surface without changing existing behavior.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "short-command-flow-entrypoint",
+    "branch_name": "feature/QUIVER-23-01-short-command-flow-entrypoint"
+  },
+  "files": [
+    "package.json",
+    "bin/**",
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/**",
+    "docs/COMMANDS.md.template",
+    "README.md",
+    "README_FOR_AI.md",
+    "tests/commands/*.test.js",
+    "scripts/ci/*.sh"
+  ],
+  "depends_on": [
+    "slice-00-spec-foundation"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Establishes the user-facing command surface and likely touches shared CLI routing.",
+  "must": [
+    "Preserve all existing `npx create-quiver` commands.",
+    "Define whether `quiver` is a binary alias or generated local script.",
+    "Add a flow entrypoint with dry-run-safe behavior.",
+    "Document the command decision clearly."
+  ],
+  "not_included": [
+    "Agent profile storage.",
+    "Planner iteration history.",
+    "Delegated execution."
+  ],
+  "acceptance": [
+    "Existing `create-quiver` CLI tests remain green.",
+    "The short command path is documented and tested.",
+    "The flow entrypoint prints clear guidance without requiring provider auth.",
+    "README_FOR_AI.md does not contradict the command decision."
+  ],
+  "tests": [
+    "node --test tests/commands/init-profiles.test.js tests/commands/prepare.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 4,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-21T14:42:19-0300"
+}

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

@@ -0,0 +1,31 @@
+# CLOSURE BRIEF - slice-02: Flow status and next-step wizard
+
+## Resumen de lo realizado
+
+Se extendio `npx create-quiver flow` para funcionar como wizard read-only: detecta estado de inicializacion, contexto, approvals, specs y slices, reporta blockers y muestra el proximo comando seguro.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Estado detectado.
+- [x] Bloqueos reportados.
+- [x] Proximo comando sugerido.
+- [x] Tests pasan.
+
+## Cambios relevantes
+
+- `src/create-quiver/commands/flow.js`: agrega lectura segura de approvals, docs, specs y slice graph.
+- `tests/commands/flow.test.js`: cubre proyecto no inicializado, contexto faltante, criterios draft, slices listos y salida JSON.
+- `docs/WORKFLOW.md.template`: recomienda `flow` cuando el siguiente paso seguro no esta claro.
+- `SPEC.md`, `STATUS.md` y `EVIDENCE_REPORT.md`: estado del slice actualizado.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+El wizard usa heuristicas conservadoras; si el grafo de slices esta roto, bloquea y deriva a `spec status`/`plan` en vez de intentar continuar.
+
+## Recomendaciones futuras
+
+Conectar perfiles de agentes en `slice-03` para que el wizard pueda mostrar provider/model configurados sin pedirlos en cada comando.

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.