create-quiver 0.10.0 → 0.12.1

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-02-cli-command-routing-version-errors/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-02: CLI command routing and version mismatch errors
+
+## Resumen de lo realizado
+
+- El parser ahora rechaza un primer argumento desconocido como comando no soportado, en vez de tratarlo como nombre legacy de proyecto.
+- La compatibilidad `--name "Project"` sigue funcionando para inicialización.
+- El error de comando no soportado muestra el comando, `--help`, el comando correcto de init y la recomendación de actualizar si el comando existe en documentación más nueva.
+- `doctor` ahora advierte cuando scripts `package.json` que llaman a `npx create-quiver` apuntan a comandos, subcomandos `ai` o subcomandos `spec` no soportados por esta versión.
+
+## Validación contra criterios de aceptación
+
+- [x] Unknown subcommands fail clearly.
+- [x] Legacy `--name` remains supported.
+- [x] Modern command-like tokens do not trigger init alias behavior.
+- [x] Version/script mismatch guidance is actionable.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `tests/commands/init-profiles.test.js`
+- `tests/commands/doctor.test.js`
+
+## Pendientes
+
+Sin pendientes del slice.
+
+## Riesgos remanentes
+
+El shortcut posicional no documentado `npx create-quiver "Project"` deja de funcionar; el camino documentado y preservado es `npx create-quiver --name "Project"` o `npx create-quiver init --name "Project"`.
+
+## Recomendaciones futuras
+
+Keep parser behavior explicit and avoid compatibility fallthrough for command-like tokens.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-02-cli-command-routing-version-errors/EXECUTION_BRIEF.md

@@ -0,0 +1,50 @@
+# EXECUTION BRIEF - slice-02: CLI command routing and version mismatch errors
+
+## Contexto
+
+During dogfooding, a modern command executed through an older installed package was interpreted as a project name. This is high-friction because it makes `prepare` look like an init request.
+
+## Objetivo
+
+Make command routing fail safe and make version/script mismatches understandable.
+
+## Alcance
+
+- Unknown subcommand handling.
+- Legacy `--name` alias preservation.
+- Version/script mismatch diagnostics in doctor/flow where appropriate.
+- Tests for ambiguous commands.
+
+## Criterios de aceptación
+
+- Unknown subcommands fail clearly.
+- Modern command names are not treated as project names.
+- Legacy `--name` remains valid.
+- Diagnostics suggest update/help actions.
+
+## Plan técnico resumido
+
+Tighten argument parsing and add tests around command mode resolution. Prefer small helpers over parser rewrites.
+
+## Pasos sugeridos de ejecución
+
+1. Locate command mode parsing.
+2. Add explicit unknown-command path.
+3. Preserve compatibility alias only for no-command plus `--name`.
+4. Add mismatch diagnostics where command surfaces are checked.
+5. Test success and failure cases.
+
+## Restricciones
+
+- Do not remove supported commands.
+- Do not require network access to detect version mismatch.
+
+## Riesgos
+
+- Parser changes can regress documented examples.
+
+## Checklist de finalización
+
+- [ ] Parser tests added.
+- [ ] Legacy alias tested.
+- [ ] Error copy reviewed.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-02-cli-command-routing-version-errors/slice.json

@@ -0,0 +1,52 @@
+{
+  "slice_id": "slice-02-cli-command-routing-version-errors",
+  "ticket": "QUIVER-24-02",
+  "type": "feature",
+  "title": "CLI command routing and version mismatch errors",
+  "objective": "Prevent unknown or unsupported subcommands from being interpreted as legacy project names and make CLI version mismatches actionable.",
+  "description": "Harden command parsing, improve unknown-command errors, and report when generated scripts target commands unsupported by the installed package.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "cli-routing-version-errors",
+    "branch_name": "feature/QUIVER-24-02-cli-routing-version-errors"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/flow.js",
+    "src/create-quiver/lib/doctor.js",
+    "tests/commands/flow.test.js",
+    "tests/commands/doctor.test.js",
+    "tests/commands/init-profiles.test.js"
+  ],
+  "depends_on": [
+    "slice-00-spec-foundation"
+  ],
+  "parallel_safe": "yes",
+  "parallel_safe_reason": "Can run in parallel with template and analyzer work if parser edits in index.js are coordinated.",
+  "must": [
+    "Unknown subcommands fail clearly.",
+    "Legacy --name alias remains supported.",
+    "Modern subcommand names are not treated as project names by old-style routing.",
+    "Version/script mismatch diagnostics are actionable.",
+    "Errors recommend --help or update path."
+  ],
+  "not_included": [
+    "Changing command names.",
+    "Removing legacy --name compatibility.",
+    "Implementing doctor --fix."
+  ],
+  "acceptance": [
+    "Unsupported subcommands do not trigger init alias behavior.",
+    "Error output names the unsupported command and shows next steps.",
+    "`npx create-quiver --name \"Project\"` still works.",
+    "Doctor can warn when generated scripts reference unsupported commands.",
+    "Tests cover modern command names with older/unsupported routing behavior."
+  ],
+  "tests": [
+    "node --test tests/commands/init-profiles.test.js tests/commands/doctor.test.js tests/commands/flow.test.js"
+  ],
+  "estimated_hours": 4,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-03-doctor-fix-doc-link-checks/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-03: Doctor fixes and documentation link checks
+
+## Resumen de lo realizado
+
+- `doctor --fix --dry-run` ahora muestra un plan de reparaciones seguras sin escribir archivos.
+- `doctor --fix` aplica reparaciones no destructivas e idempotentes para `.gitignore`, `.quiver/.gitignore`, `.quiver/config.json` y scripts `quiver:*` faltantes.
+- `doctor` valida links Markdown locales en docs generadas y advierte cuando apuntan a archivos inexistentes.
+- Los fixes preservan contenido existente y solo agregan líneas/scripts faltantes.
+
+## Validación contra criterios de aceptación
+
+- [x] `doctor --fix --dry-run` writes nothing.
+- [x] `doctor --fix` is safe and idempotent.
+- [x] Docs link checks detect missing local files.
+- [x] Optional generated docs are not reported when they are not linked by the selected profile.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/doctor.js`
+- `tests/commands/doctor.test.js`
+
+## Pendientes
+
+Sin pendientes del slice.
+
+## Riesgos remanentes
+
+El link checker cubre links Markdown locales explícitos; no intenta validar rutas escritas en texto plano o dentro de bloques de código.
+
+## Recomendaciones futuras
+
+Mantener `doctor --fix` limitado a reparaciones aditivas y auditables; cualquier rewrite de contenido debe ir en otro flujo con confirmación explícita.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-03-doctor-fix-doc-link-checks/EXECUTION_BRIEF.md

@@ -0,0 +1,50 @@
+# EXECUTION BRIEF - slice-03: Doctor fixes and documentation link checks
+
+## Contexto
+
+Init hygiene can still leave older projects with missing `.gitignore`, stale scripts, or generated docs links. Users need a safe way to see and apply repairs.
+
+## Objetivo
+
+Add previewable, idempotent repair behavior and docs link validation.
+
+## Alcance
+
+- `doctor --fix --dry-run`.
+- `doctor --fix` for safe non-destructive repairs.
+- Local Markdown link checks for generated docs.
+- Tests for idempotency and no-write dry-run.
+
+## Criterios de aceptación
+
+- Dry-run writes nothing.
+- Fix mode is idempotent.
+- User-owned content is preserved.
+- Missing generated-doc links are detected.
+
+## Plan técnico resumido
+
+Extend doctor report generation with a repair plan, then execute only approved safe operations when `--fix` is provided.
+
+## Pasos sugeridos de ejecución
+
+1. Model fix candidates separately from applying fixes.
+2. Render the fix plan in doctor output.
+3. Apply safe fixes only when not dry-run.
+4. Add docs link validation.
+5. Test idempotency and failure output.
+
+## Restricciones
+
+- No destructive writes.
+- No link checking over dependency folders or generated caches.
+
+## Riesgos
+
+- Link checker could over-report optional docs. Keep optional handling explicit.
+
+## Checklist de finalización
+
+- [ ] Dry-run no-write test.
+- [ ] Idempotency test.
+- [ ] Link-check test.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-03-doctor-fix-doc-link-checks/slice.json

@@ -0,0 +1,53 @@
+{
+  "slice_id": "slice-03-doctor-fix-doc-link-checks",
+  "ticket": "QUIVER-24-03",
+  "type": "feature",
+  "title": "Doctor fixes and documentation link checks",
+  "objective": "Add safe repair previews and generated-doc link validation to reduce manual cleanup after init.",
+  "description": "Introduce `doctor --fix --dry-run`, safe `doctor --fix`, and a docs link check that understands generated profiles and optional files.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "doctor-fix-doc-link-checks",
+    "branch_name": "feature/QUIVER-24-03-doctor-fix-doc-link-checks"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/commands/prepare.js",
+    "tests/lib/doctor.test.js",
+    "tests/commands/doctor.test.js",
+    "tests/commands/prepare.test.js"
+  ],
+  "depends_on": [
+    "slice-01-init-template-hygiene",
+    "slice-02-cli-command-routing-version-errors"
+  ],
+  "parallel_safe": "yes",
+  "parallel_safe_reason": "Can run after init/parser contracts are stable; owns doctor/link-check behavior.",
+  "must": [
+    "Add `doctor --fix --dry-run` with a planned change list.",
+    "Add safe `doctor --fix` for non-destructive repairs only.",
+    "Validate local docs links for generated docs.",
+    "Avoid deleting or rewriting user-owned content.",
+    "Make fixes idempotent."
+  ],
+  "not_included": [
+    "AI context generation.",
+    "Evidence capture.",
+    "Remote validation behavior."
+  ],
+  "acceptance": [
+    "`doctor --fix --dry-run` reports changes and writes nothing.",
+    "`doctor --fix` applies only non-destructive changes.",
+    "Running `doctor --fix` twice produces no duplicate content.",
+    "Docs link validation catches real missing local files.",
+    "Optional docs are either ignored or clearly reported as optional."
+  ],
+  "tests": [
+    "node --test tests/lib/doctor.test.js tests/commands/doctor.test.js tests/commands/prepare.test.js"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-04-prepare-output-ai-context-drafts/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-04: Prepare output and AI context preparation drafts
+
+## Resumen de lo realizado
+
+Se aclaró la salida de `prepare --dry-run` para separar guidance del framework de docs del proyecto, y se agregó `ai prepare-context` para previsualizar o escribir borradores de contexto IA solo en documentación.
+
+## Validación contra criterios de aceptación
+
+- [x] Prepare output is clear.
+- [x] Context preparation dry-run writes nothing.
+- [x] Write mode stays docs-only.
+- [x] Uncertainty is explicitly marked.
+- [x] Generated scripts and command docs include `quiver:ai:prepare-context`.
+
+## Cambios relevantes
+
+- `prepare --dry-run` ya no reporta `README_FOR_AI.md missing` como deuda falsa en proyectos generados.
+- Nuevo subcomando `npx create-quiver ai prepare-context`.
+- `ai prepare-context --dry-run` reporta docs propuestas, archivos considerados, supuestos, riesgos y rutas omitidas.
+- Write mode toca solo `docs/AI_CONTEXT.md`, `docs/AI_ONBOARDING_PROMPT.md`, `docs/CONTEXTO.md`, `docs/STATUS.md` y `docs/DECISIONS.md`.
+- Scripts generados y docs de comandos incluyen `quiver:ai:prepare-context`.
+
+## Pendientes
+
+Sin pendientes del slice.
+
+## Riesgos remanentes
+
+Los borradores escritos reemplazan los docs/context aprobados. El flujo recomendado sigue siendo ejecutar `--dry-run`, revisar supuestos/riesgos y recién después escribir.
+
+## Recomendaciones futuras
+
+Use this context preparation output as the input for planner onboarding.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-04-prepare-output-ai-context-drafts/EXECUTION_BRIEF.md

@@ -0,0 +1,50 @@
+# EXECUTION BRIEF - slice-04: Prepare output and AI context preparation drafts
+
+## Contexto
+
+`prepare --dry-run` currently reports missing root `README_FOR_AI.md` in generated projects, which can look like project debt. Users also expect a command that prepares context docs after analysis.
+
+## Objetivo
+
+Clarify prepare output and add safe docs-only context preparation for IA onboarding.
+
+## Alcance
+
+- Prepare report wording.
+- `ai prepare-context --dry-run`.
+- Optional write mode for context docs only.
+- Assumptions, risks, omitted paths, and uncertainty markers.
+
+## Criterios de aceptación
+
+- No false `README_FOR_AI.md` debt.
+- Dry-run writes nothing.
+- Write mode only touches approved docs.
+- Product code is untouched.
+
+## Plan técnico resumido
+
+Reuse existing context-pack and onboarding planning helpers where possible. Add a command path that renders proposed docs and tracks uncertainty.
+
+## Pasos sugeridos de ejecución
+
+1. Adjust prepare source wording.
+2. Add command routing for `ai prepare-context`.
+3. Build proposed context doc outputs from project map and existing docs.
+4. Add no-write and docs-only write tests.
+5. Update templates and docs.
+
+## Restricciones
+
+- Do not invent confirmed facts.
+- Do not read dependency folders or local AI state.
+
+## Riesgos
+
+- Generated context can become too verbose; keep summaries concise and traceable.
+
+## Checklist de finalización
+
+- [ ] Prepare wording test.
+- [ ] `ai prepare-context --dry-run` test.
+- [ ] Docs-only write test.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-04-prepare-output-ai-context-drafts/slice.json

@@ -0,0 +1,70 @@
+{
+  "slice_id": "slice-04-prepare-output-ai-context-drafts",
+  "ticket": "QUIVER-24-04",
+  "type": "feature",
+  "title": "Prepare output and AI context preparation drafts",
+  "objective": "Make prepare output clearer and add a safe AI context preparation command that produces reviewable project context drafts.",
+  "description": "Improve `prepare --dry-run` wording around framework sources and implement `ai prepare-context` with dry-run-first behavior, assumptions, risks, and docs-only writes.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "prepare-ai-context-drafts",
+    "branch_name": "feature/QUIVER-24-04-prepare-ai-context-drafts"
+  },
+  "files": [
+    "package.json",
+    "package.template.json",
+    "README.md",
+    "README_FOR_AI.md",
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/prepare.js",
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/context-packs.js",
+    "src/create-quiver/lib/ai/onboarding-template.js",
+    "src/create-quiver/lib/init-layout.js",
+    "docs/COMMANDS.md.template",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "docs/AI_CONTEXT.md.template",
+    "docs/CONTEXTO.md.template",
+    "docs/STATUS.md.template",
+    "docs/DECISIONS.md.template",
+    "scripts/ci/smoke-create-quiver.sh",
+    "tests/commands/prepare.test.js",
+    "tests/commands/ai-onboard.test.js",
+    "tests/commands/doctor.test.js",
+    "tests/lib/ai-context-packs.test.js",
+    "tests/lib/init-layout.test.js"
+  ],
+  "depends_on": [
+    "slice-01-init-template-hygiene",
+    "slice-02-cli-command-routing-version-errors"
+  ],
+  "parallel_safe": "yes",
+  "parallel_safe_reason": "Can run after parser and init docs contracts are stable; owns prepare/AI context output.",
+  "must": [
+    "Change misleading `README_FOR_AI.md missing` output.",
+    "Add `ai prepare-context --dry-run`.",
+    "Allow docs-only context draft writes with explicit uncertainty markers.",
+    "Report assumptions, risks, files considered, and omitted paths.",
+    "Never modify product code."
+  ],
+  "not_included": [
+    "Calling real provider APIs in tests.",
+    "Generating implementation specs.",
+    "Changing approval gates."
+  ],
+  "acceptance": [
+    "`prepare --dry-run` distinguishes framework source guidance from generated project docs.",
+    "`ai prepare-context --dry-run` reports proposed context docs without writing files.",
+    "Write mode touches only approved docs/context files.",
+    "Uncertain statements are marked as TODO, Assumption, or Pending confirmation.",
+    "Product code is never modified by context preparation."
+  ],
+  "tests": [
+    "node --test tests/commands/prepare.test.js tests/commands/ai-onboard.test.js tests/lib/ai-context-packs.test.js tests/commands/doctor.test.js tests/lib/init-layout.test.js",
+    "npm run smoke:create-quiver"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-05-local-slice-validation-base-guidance/CLOSURE_BRIEF.md

@@ -0,0 +1,36 @@
+# CLOSURE BRIEF - slice-05: Local slice validation and base branch guidance
+
+## Resumen de lo realizado
+
+- `check-slice --local` valida estructura local sin exigir remoto/base.
+- El modo local reporta explícitamente que omite validaciones de existencia en remoto/base y overlap basado en base remota.
+- El modo normal conserva la validación contra base/remoto y ahora recomienda `--local`, `--base <branch>` o configurar/fetchear el remoto cuando no existe base.
+- `check-slice` acepta `--base` y `--remote` para seleccionar la base/remoto de validación.
+
+## Validación contra criterios de aceptación
+
+- [x] Local mode validates without remote.
+- [x] Omitted remote/base checks are visible.
+- [x] Default mode still protects PR readiness.
+- [x] Explicit local base branch works.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/readiness.js`
+- `tests/lib/check-slice.test.js`
+- `README.md`
+- `README_FOR_AI.md`
+- `docs/COMMANDS.md.template`
+
+## Pendientes
+
+Sin pendientes del slice.
+
+## Riesgos remanentes
+
+Documentation must avoid implying `--local` is enough for PR merge readiness.
+
+## Recomendaciones futuras
+
+Consider reusing this separation in `check-pr` diagnostics.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-05-local-slice-validation-base-guidance/EXECUTION_BRIEF.md

@@ -0,0 +1,49 @@
+# EXECUTION BRIEF - slice-05: Local slice validation and base branch guidance
+
+## Contexto
+
+`check-slice` currently assumes a remote/base branch and can fail in a brand-new local repo with a misleading `origin/develop` message.
+
+## Objetivo
+
+Allow local structural validation while preserving stricter PR/base validation.
+
+## Alcance
+
+- `check-slice --local`.
+- Base/remote guidance.
+- Omitted-checks reporting.
+- Tests for local repos and remote-less repos.
+
+## Criterios de aceptación
+
+- Local mode passes without remote when slice structure is valid.
+- Local output lists omitted remote/base checks.
+- Normal mode recommends recovery steps when remote/base is missing.
+
+## Plan técnico resumido
+
+Split readiness checks into local structural checks and remote/base checks. Route `--local` through the structural subset.
+
+## Pasos sugeridos de ejecución
+
+1. Identify readiness checks that require Git remote/base.
+2. Add local-mode option.
+3. Add output section for omitted validations.
+4. Add explicit base guidance.
+5. Test both modes.
+
+## Restricciones
+
+- Do not weaken default PR readiness checks.
+- Do not assume `develop` when `main` is the only local base.
+
+## Riesgos
+
+- Users may confuse local readiness with PR readiness; output must distinguish them.
+
+## Checklist de finalización
+
+- [ ] Local mode test.
+- [ ] Missing remote guidance test.
+- [ ] Existing default behavior test.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-05-local-slice-validation-base-guidance/slice.json

@@ -0,0 +1,52 @@
+{
+  "slice_id": "slice-05-local-slice-validation-base-guidance",
+  "ticket": "QUIVER-24-05",
+  "type": "feature",
+  "title": "Local slice validation and base branch guidance",
+  "objective": "Separate local slice readiness from remote/base-branch PR readiness so new repos can validate slices without `origin/develop`.",
+  "description": "Add `check-slice --local`, configurable base/remote guidance, and clearer output for validations omitted in local mode.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "local-slice-validation-base-guidance",
+    "branch_name": "feature/QUIVER-24-05-local-slice-validation-base-guidance"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/readiness.js",
+    "src/create-quiver/lib/slice.js",
+    "src/create-quiver/lib/git.js",
+    "tests/lib/check-slice.test.js",
+    "tests/commands/flow.test.js"
+  ],
+  "depends_on": [
+    "slice-02-cli-command-routing-version-errors"
+  ],
+  "parallel_safe": "yes",
+  "parallel_safe_reason": "Can run after CLI routing is stable; owns slice readiness behavior.",
+  "must": [
+    "Add `check-slice --local`.",
+    "Make local mode validate JSON, handoffs, dependencies, file declarations, and status rules.",
+    "Make local mode explicitly report omitted remote/base checks.",
+    "Improve normal mode guidance when no remote/base exists.",
+    "Support explicit `--base` and existing config where appropriate."
+  ],
+  "not_included": [
+    "Changing PR creation checks.",
+    "Changing slice schema unless required.",
+    "Starting worktrees."
+  ],
+  "acceptance": [
+    "`check-slice --local` works in a repo without remotes.",
+    "Local mode reports which remote/base validations were omitted.",
+    "Normal mode without remote suggests `--local`, `--base`, or config.",
+    "Existing remote/base validation behavior remains available.",
+    "Tests cover new repo, missing remote, explicit base, and valid local slice cases."
+  ],
+  "tests": [
+    "node --test tests/lib/check-slice.test.js tests/commands/flow.test.js"
+  ],
+  "estimated_hours": 5,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-06-plan-graph-next-history-views/CLOSURE_BRIEF.md

@@ -0,0 +1,43 @@
+# CLOSURE BRIEF - slice-06: Historical plan, graph, and next views
+
+## Resumen de lo realizado
+
+- Se agregó `--include-completed` a `plan`, `graph` y `next`.
+- `plan` y `graph` mantienen el default pending-only; con el flag incluyen completados y siguen excluyendo `skipped`/`cancelled`.
+- `next --include-completed` no sugiere completados como trabajo accionable; solo agrega historial.
+- `graph --spec <slug>` ahora filtra consistentemente por spec y no mezcla slices de otros specs.
+- `readAllSlices` propaga `ticket`, por lo que el plan muestra tickets reales.
+
+## Validación contra criterios de aceptación
+
+- [x] Defaults are unchanged.
+- [x] Completed slices visible with explicit flag.
+- [x] JSON output remains parseable.
+- [x] `--spec` filtering is consistent across plan, graph, and next.
+- [x] Ticket values are preserved in plan output.
+
+## Cambios relevantes
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/commands/plan.js`
+- `src/create-quiver/commands/graph.js`
+- `src/create-quiver/commands/next.js`
+- `src/create-quiver/lib/slice-graph.js`
+- `tests/commands/plan.test.js`
+- `tests/commands/graph.test.js`
+- `tests/commands/next.test.js`
+- `README.md`
+- `README_FOR_AI.md`
+- `docs/COMMANDS.md.template`
+
+## Pendientes
+
+Sin pendientes del slice.
+
+## Riesgos remanentes
+
+History mode copy must not be mistaken for execution guidance.
+
+## Recomendaciones futuras
+
+Consider adding examples to docs after usage stabilizes.

package/specs/quiver-v24-dx-onboarding-hardening/slices/slice-06-plan-graph-next-history-views/EXECUTION_BRIEF.md

@@ -0,0 +1,53 @@
+# EXECUTION BRIEF - slice-06: Historical plan, graph, and next views
+
+## Contexto
+
+Completed demo specs currently produce "No pending slices found", which is accurate but not useful for explaining or auditing a completed flow.
+
+## Objetivo
+
+Add historical view flags while keeping normal work-planning behavior unchanged.
+
+## Alcance
+
+- `--include-completed` flag handling.
+- Human and JSON output updates.
+- Status semantics for history views.
+- Consistent `--spec <slug>` filtering across plan, graph, and next.
+- Ticket propagation in planning output.
+- Tests for plan, graph, and next.
+
+## Criterios de aceptación
+
+- Defaults remain pending-only.
+- Completed slices can be displayed explicitly.
+- JSON remains parseable.
+- `next` does not accidentally suggest completed work as actionable.
+- `--spec` filters do not leak slices from other specs.
+- Tickets from `slice.json` appear in plan output.
+
+## Plan técnico resumido
+
+Extend slice selection options rather than changing the graph library's default filtering semantics.
+
+## Pasos sugeridos de ejecución
+
+1. Add CLI option parsing.
+2. Extend plan collection filters.
+3. Reuse or pass options into graph/next.
+4. Update formatters and JSON.
+5. Add tests for defaults and history mode.
+
+## Restricciones
+
+- Do not break existing `--only-ready`, `--all-ready`, `--format`, or `--json`.
+
+## Riesgos
+
+- Status terminology can confuse users; label history output clearly.
+
+## Checklist de finalización
+
+- [ ] Default behavior tests pass.
+- [ ] History mode tests pass.
+- [ ] JSON output tests pass.