create-quiver 0.9.0 → 0.10.0

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-03-ai-phase-gated-planner/slice.json

@@ -0,0 +1,62 @@
+{
+  "slice_id": "slice-03-ai-phase-gated-planner",
+  "ticket": "QUIVER-20-03",
+  "type": "feature",
+  "title": "Add phase-gated planner commands",
+  "objective": "Add quiver ai onboard and quiver ai plan flows with explicit approval phases and no file writes before the spec phase.",
+  "description": "Expose initial AI commands that use the provider runner and context packs. The planner flow must separate acceptance criteria, technical plan, and spec generation so the user can approve each phase before advancing.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "ai-phase-gated-planner",
+    "branch_name": "feature/QUIVER-20-03-ai-phase-gated-planner"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/ai/phase-gates.js",
+    "specs/quiver-v20-ai-cli-orchestration/slices/slice-03-ai-phase-gated-planner/CLOSURE_BRIEF.md",
+    "specs/quiver-v20-ai-cli-orchestration/slices/slice-03-ai-phase-gated-planner/slice.json",
+    "specs/quiver-v20-ai-cli-orchestration/EVIDENCE_REPORT.md",
+    "specs/quiver-v20-ai-cli-orchestration/STATUS.md",
+    "tests/commands/ai-plan.test.js",
+    "tests/commands/ai-onboard.test.js"
+  ],
+  "depends_on": [
+    "slice-01-ai-provider-runner",
+    "slice-02-context-packs-token-budget"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Requires provider runner and context packs.",
+  "must": [
+    "Add command parsing for npx create-quiver ai onboard.",
+    "Add command parsing for npx create-quiver ai plan.",
+    "Support --provider, --role, --context, --input, --dry-run, and --timeout where applicable.",
+    "Default ai onboard to planner role and full context.",
+    "Default ai plan acceptance phase to planning context.",
+    "Prevent file writes in acceptance and technical-plan phases.",
+    "Require explicit phase selection before spec artifact generation.",
+    "Print phase output to console."
+  ],
+  "not_included": [
+    "Generating spec files in this slice.",
+    "Executing slices.",
+    "Opening PRs."
+  ],
+  "acceptance": [
+    "ai onboard --dry-run prints provider, role, context pack, and command plan.",
+    "ai plan acceptance phase does not write files.",
+    "ai plan technical-plan phase does not write files.",
+    "ai plan spec phase delegates to a generator placeholder or clear not-yet-implemented path until slice-04.",
+    "Missing input file fails with a clear error.",
+    "Provider errors propagate with actionable context."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-plan.test.js tests/commands/ai-onboard.test.js tests/lib/ai-providers.test.js tests/lib/ai-context-packs.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 5,
+  "actual_hours": 5,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-04-spec-slice-handoff-pr-generation/CLOSURE_BRIEF.md

@@ -0,0 +1,36 @@
+# CLOSURE BRIEF - slice-04: Spec, slice, handoff, and PR generation
+
+## Resumen de lo realizado
+
+Se implemento la fase `spec` de `ai plan` con un generador local que crea `SPEC.md`, `STATUS.md`, `EVIDENCE_REPORT.md`, `EXECUTION_PLAN.md`, `pr.md`, `slice-00` y slices posteriores, valida los `slice.json`, y falla sin overwrite cuando el directorio de spec ya existe.
+
+## Validacion contra criterios de aceptacion
+
+- [x] `SPEC.md` generado.
+- [x] `slice-00` generado.
+- [x] Handoffs generados para cada slice.
+- [x] `EXECUTION_PLAN.md` generado.
+- [x] `pr.md` generado.
+- [x] Colisiones fallan sin overwrite.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/ai/spec-generator.js`
+- `src/create-quiver/lib/ai/spec-templates.js`
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/lib/ai/phase-gates.js`
+- `tests/lib/ai-spec-generator.test.js`
+- `tests/commands/ai-plan-spec-phase.test.js`
+- `tests/commands/ai-plan.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+- La primera version depende de `--input` como fuente aprobada. Si el input no trae una forma clara de spec, el generador usa una plantilla segura.
+
+## Recomendaciones futuras
+
+Persistir la salida de fases anteriores para que `spec` pueda consumir un contrato estructurado en lugar de solo el input aprobado.

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-04-spec-slice-handoff-pr-generation/EXECUTION_BRIEF.md

@@ -0,0 +1,63 @@
+# EXECUTION BRIEF - slice-04: Spec, slice, handoff, and PR generation
+
+**Spec:** quiver-v20-ai-cli-orchestration
+**Slice:** slice-04-spec-slice-handoff-pr-generation
+**Tipo:** feature
+
+## Contexto
+
+Una vez aprobado el plan tecnico, Quiver debe crear artefactos ejecutables para que el trabajo se pueda dividir por slices y PR.
+
+## Objetivo
+
+Implementar generacion de `SPEC.md`, `slice-00`, slices, handoffs, `EXECUTION_PLAN.md` y `pr.md`.
+
+## Alcance
+
+- Generador de spec directory.
+- Template de slice obligatoria `slice-00`.
+- Handoffs por slice.
+- Validacion de JSON generado.
+- Prevencion de overwrite accidental.
+
+## Criterios de aceptacion
+
+- Toda spec generada tiene `slice-00`.
+- Cada slice tiene `EXECUTION_BRIEF.md` y `CLOSURE_BRIEF.md`.
+- `pr.md` siempre existe.
+- Colision de directorio falla sin sobrescribir.
+- JSON generado parsea.
+
+## Plan tecnico resumido
+
+Crear `spec-generator.js` y `spec-templates.js`. Integrar la fase `spec` de `ai plan` con el generador. Validar antes de escribir y despues de escribir.
+
+## Pasos sugeridos de ejecucion
+
+1. Definir modelo de input aprobado.
+2. Crear templates internos.
+3. Implementar escritura atomica o segura.
+4. Validar paths y colisiones.
+5. Integrar con `ai plan --phase spec`.
+6. Agregar tests.
+
+## Restricciones
+
+- No commitear automaticamente.
+- No abrir PR.
+- No ejecutar slices.
+
+## Riesgos
+
+- Generar artefactos inconsistentes.
+- Sobrescribir una spec existente.
+- Handoffs demasiado genericos para executors.
+
+## Checklist de finalizacion
+
+- [ ] Tests de generador pasan.
+- [ ] Colision cubierta.
+- [ ] slice-00 cubierta.
+- [ ] pr.md cubierta.
+- [ ] JSON parse cubierto.
+

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-04-spec-slice-handoff-pr-generation/slice.json

@@ -0,0 +1,59 @@
+{
+  "slice_id": "slice-04-spec-slice-handoff-pr-generation",
+  "ticket": "QUIVER-20-04",
+  "type": "feature",
+  "title": "Generate specs, slices, handoffs, and PR body after approval",
+  "objective": "Implement the artifact generator used by the planner spec phase.",
+  "description": "After the user approves the technical plan, Quiver should generate a spec directory with mandatory slice-00, slice.json files, EXECUTION_BRIEF.md, CLOSURE_BRIEF.md, EXECUTION_PLAN.md, and pr.md.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "ai-spec-slice-handoff-generation",
+    "branch_name": "feature/QUIVER-20-04-ai-spec-slice-handoff-generation"
+  },
+  "files": [
+    "src/create-quiver/lib/ai/spec-generator.js",
+    "src/create-quiver/lib/ai/spec-templates.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/lib/ai-spec-generator.test.js",
+    "tests/commands/ai-plan-spec-phase.test.js"
+  ],
+  "depends_on": [
+    "slice-03-ai-phase-gated-planner"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Requires planner phase plumbing.",
+  "must": [
+    "Generate SPEC.md from approved criteria and plan.",
+    "Generate mandatory slice-00.",
+    "Generate one or more implementation slices.",
+    "Generate EXECUTION_BRIEF.md and CLOSURE_BRIEF.md for every slice.",
+    "Generate EXECUTION_PLAN.md with dependencies and parallelization.",
+    "Generate pr.md following GitFlow headings.",
+    "Avoid overwriting existing spec directories unless an explicit overwrite flag is added and approved.",
+    "Validate generated slice.json files before completing."
+  ],
+  "not_included": [
+    "Running executor agents.",
+    "Creating GitHub PRs.",
+    "Automatically committing generated artifacts."
+  ],
+  "acceptance": [
+    "Generated spec has slice-00.",
+    "Every later slice depends on slice-00 directly or indirectly.",
+    "Every slice has both execution and closure briefs.",
+    "pr.md is always created.",
+    "Existing spec directory collision fails safely.",
+    "Generated JSON parses successfully."
+  ],
+  "tests": [
+    "node --test tests/lib/ai-spec-generator.test.js tests/commands/ai-plan-spec-phase.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 5,
+  "started_at": "2026-05-19T17:00:18-0300",
+  "completed_at": "2026-05-19T17:00:18-0300"
+}

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-05-execution-plan-parallel-worktrees/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-05: Execution plan and parallel worktrees
+
+## Resumen de lo realizado
+
+Se implemento `src/create-quiver/lib/ai/execution-plan.js` para calcular ready levels, integrar la barrera de `slice-00` por spec, separar niveles paralelos y documentar el uso de worktrees temporales. Tambien se extendio `src/create-quiver/lib/slice-graph.js` con helpers para reconocer slices de foundation y se agregaron tests de plan de ejecucion, ciclos y dependencias faltantes.
+
+## Validacion contra criterios de aceptacion
+
+- [x] `slice-00` aparece primero en el plan.
+- [x] Ready levels respetan dependencias.
+- [x] Ciclos detectados.
+- [x] Dependencias faltantes detectadas.
+- [x] Smokes existentes siguen pasando.
+
+## Cambios relevantes
+
+- Nuevo planner de ejecucion en `src/create-quiver/lib/ai/execution-plan.js`.
+- Barrera de foundation por spec para evitar que slices posteriores adelanten a `slice-00`.
+- Metadatos de worktree temporal por nivel paralelo.
+- Cobertura de tests para ready levels, formatter y errores de grafo.
+
+## Pendientes
+
+- Slice-06, Slice-07 y Slice-08 siguen pendientes de implementacion.
+
+## Riesgos remanentes
+
+- Los comandos `plan/graph/next` siguen usando su comportamiento actual; si se quiere exponer este plan de ejecucion en CLI, falta cablearlo a un comando.
+
+## Recomendaciones futuras
+
+Conectar este planner con una salida de CLI o con `EXECUTION_PLAN.md` si se necesita una vista humana del nivel ready y del orden de integracion.

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-05-execution-plan-parallel-worktrees/EXECUTION_BRIEF.md

@@ -0,0 +1,61 @@
+# EXECUTION BRIEF - slice-05: Execution plan and parallel worktrees
+
+**Spec:** quiver-v20-ai-cli-orchestration
+**Slice:** slice-05-execution-plan-parallel-worktrees
+**Tipo:** feature
+
+## Contexto
+
+El planner debe decir que slices van secuenciales y cuales pueden correr en paralelo. Para paralelismo real, las slices no deben pisarse en la misma worktree.
+
+## Objetivo
+
+Agregar representacion de niveles de ejecucion, dependencias, paralelismo e integracion de worktrees temporales.
+
+## Alcance
+
+- Tratar `slice-00` como primer bloqueante.
+- Generar niveles ready.
+- Detectar ciclos y dependencias faltantes.
+- Documentar estrategia de worktrees temporales.
+- Mantener compatibilidad con plan/graph/next.
+
+## Criterios de aceptacion
+
+- El execution plan muestra `slice-00` primero.
+- Slices paralelas solo aparecen cuando sus dependencias estan satisfechas.
+- Ciclos fallan con diagnostico claro.
+- Dependencias faltantes fallan con diagnostico claro.
+- Smokes actuales siguen pasando.
+
+## Plan tecnico resumido
+
+Extender `slice-graph.js` y agregar `ai/execution-plan.js`. Reusar logica existente de plan/graph cuando sea posible. Evitar duplicar algoritmos de dependencias.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar graph/plan actual.
+2. Agregar modelo de ready levels.
+3. Agregar reglas de `slice-00`.
+4. Agregar diagnosticos de error.
+5. Agregar tests.
+6. Correr smoke.
+
+## Restricciones
+
+- No ejecutar agentes.
+- No mergear worktrees automaticamente.
+- No romper formatos existentes.
+
+## Riesgos
+
+- Regresion en `quiver:plan`, `quiver:graph`, `quiver:next`.
+- Ambiguedad entre paralelizable y paralelo ya ejecutado.
+
+## Checklist de finalizacion
+
+- [ ] Tests de execution plan pasan.
+- [ ] Tests de slice graph pasan.
+- [ ] Smoke create-quiver pasa.
+- [ ] Formatos existentes siguen compatibles.
+

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-05-execution-plan-parallel-worktrees/slice.json

@@ -0,0 +1,59 @@
+{
+  "slice_id": "slice-05-execution-plan-parallel-worktrees",
+  "ticket": "QUIVER-20-05",
+  "type": "feature",
+  "title": "Add execution plan and parallel worktree support",
+  "objective": "Represent slice dependencies, ready levels, parallel execution groups, and temporary worktree strategy for slices that can run concurrently.",
+  "description": "Extend Quiver's orchestration model so generated specs and existing slice graph commands can reason about slice-00, dependencies, sequential work, parallel-ready work, and integration order.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "ai-execution-plan-parallel-worktrees",
+    "branch_name": "feature/QUIVER-20-05-ai-execution-plan-parallel-worktrees"
+  },
+  "files": [
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/git.js",
+    "src/create-quiver/lib/slice-graph.js",
+    "src/create-quiver/commands/plan.js",
+    "src/create-quiver/commands/graph.js",
+    "tests/lib/ai-execution-plan.test.js",
+    "tests/lib/slice-graph.test.js"
+  ],
+  "depends_on": [
+    "slice-04-spec-slice-handoff-pr-generation"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run in parallel with GitHub PR preflight after slice-04 if file ownership is respected.",
+  "must": [
+    "Treat slice-00 as the first required dependency for generated specs.",
+    "Represent ready levels for sequential and parallel execution.",
+    "Document when temporary worktrees are needed for parallel slices.",
+    "Provide integration order for parallel outputs.",
+    "Keep existing quiver:plan, quiver:graph, and quiver:next behavior compatible.",
+    "Handle dependency cycles and missing dependency references with clear errors."
+  ],
+  "not_included": [
+    "Running AI executors.",
+    "Opening PRs.",
+    "Merging temporary worktrees automatically without validation."
+  ],
+  "acceptance": [
+    "Execution plan output shows slice-00 first.",
+    "Parallel-ready slices are grouped only after dependencies are satisfied.",
+    "Dependency cycles fail with a clear diagnostic.",
+    "Missing dependencies fail with a clear diagnostic.",
+    "Existing plan/graph/next smokes still pass."
+  ],
+  "tests": [
+    "node --test tests/lib/ai-execution-plan.test.js tests/lib/slice-graph.test.js",
+    "npm run smoke:create-quiver",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 5,
+  "started_at": "2026-05-19T17:24:20-0300",
+  "completed_at": "2026-05-19T17:24:20-0300"
+}

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-06-ai-execute-slice-scope-enforcement/CLOSURE_BRIEF.md

@@ -0,0 +1,36 @@
+# CLOSURE BRIEF - slice-06: Execute slice with scope enforcement
+
+## Resumen de lo realizado
+
+Se implemento `ai execute-slice` con contexto executor minimo, validacion de `slice.json` y `EXECUTION_BRIEF.md`, dry-run sin provider, ejecucion del provider, captura de snapshot Git antes/despues y validacion estricta contra `slice.json.files`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] `ai execute-slice` disponible.
+- [x] Falta de `slice.json` falla.
+- [x] Falta de `EXECUTION_BRIEF.md` falla.
+- [x] Dry-run no ejecuta provider.
+- [x] Scope violation detectada.
+- [x] Executor no recibe onboarding completo.
+
+## Cambios relevantes
+
+- `src/create-quiver/lib/ai/executor.js`
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/scope.js`
+- `tests/commands/ai-execute-slice.test.js`
+- `tests/lib/ai-executor.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+- El executor requiere worktree limpio antes de correr para que la comparacion pre/post sea confiable.
+- La validacion de scope depende de `git status --porcelain`; proyectos sin Git no son un caso soportado para ejecucion automatica segura.
+
+## Recomendaciones futuras
+
+Mantener scope enforcement estricto aunque el provider complete la tarea correctamente.

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-06-ai-execute-slice-scope-enforcement/EXECUTION_BRIEF.md

@@ -0,0 +1,64 @@
+# EXECUTION BRIEF - slice-06: Execute slice with scope enforcement
+
+**Spec:** quiver-v20-ai-cli-orchestration
+**Slice:** slice-06-ai-execute-slice-scope-enforcement
+**Tipo:** feature
+
+## Contexto
+
+El executor es un agente de menor costo que puede modificar codigo directamente siguiendo el handoff. Para que sea seguro, Quiver debe controlar el scope antes y despues.
+
+## Objetivo
+
+Agregar `quiver ai execute-slice` con contexto minimo y validacion de scope.
+
+## Alcance
+
+- Subcomando `ai execute-slice`.
+- Requerir `--slice`.
+- Requerir `slice.json` y `EXECUTION_BRIEF.md`.
+- Preparar prompt executor con contexto `slice` o `minimal`.
+- Capturar diff antes/despues.
+- Ejecutar scope validation.
+
+## Criterios de aceptacion
+
+- Falla si falta `slice.json`.
+- Falla si falta `EXECUTION_BRIEF.md`.
+- Dry-run no ejecuta provider.
+- Detecta archivos fuera de scope.
+- No incluye onboarding full.
+- Error de provider sale con codigo no cero.
+
+## Plan tecnico resumido
+
+Crear `ai/executor.js` y conectar el subcomando en `commands/ai.js`. Reusar context packs, provider runner y scope validation existente.
+
+## Pasos sugeridos de ejecucion
+
+1. Implementar loader de slice y handoff.
+2. Implementar prompt executor.
+3. Integrar provider runner.
+4. Capturar diff pre/post.
+5. Validar scope.
+6. Agregar tests.
+
+## Restricciones
+
+- No commitear automaticamente.
+- No arreglar scope violations automaticamente.
+- No correr multiples executors en esta slice.
+
+## Riesgos
+
+- Scope validation incompleta.
+- Executor necesita mas contexto que el minimo.
+- Cambios de codigo fuera del handoff.
+
+## Checklist de finalizacion
+
+- [ ] Tests de execute-slice pasan.
+- [ ] Dry-run cubierto.
+- [ ] Scope violation cubierto.
+- [ ] Provider failure cubierto.
+

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-06-ai-execute-slice-scope-enforcement/slice.json

@@ -0,0 +1,65 @@
+{
+  "slice_id": "slice-06-ai-execute-slice-scope-enforcement",
+  "ticket": "QUIVER-20-06",
+  "type": "feature",
+  "title": "Add executor command with scope enforcement",
+  "objective": "Allow a low-cost executor agent to run a slice using minimal context, then verify that changes stayed inside the declared handoff scope.",
+  "description": "Implement quiver ai execute-slice with provider selection, executor role defaults, slice context pack, pre-run validation, post-run git diff inspection, and check-scope integration.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "ai-execute-slice-scope-enforcement",
+    "branch_name": "feature/QUIVER-20-06-ai-execute-slice-scope-enforcement"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/ai/context-packs.js",
+    "src/create-quiver/lib/scope.js",
+    "tests/commands/ai-execute-slice.test.js",
+    "tests/lib/ai-executor.test.js"
+  ],
+  "depends_on": [
+    "slice-01-ai-provider-runner",
+    "slice-02-context-packs-token-budget",
+    "slice-05-execution-plan-parallel-worktrees"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Requires provider runner, context packs, and execution planning.",
+  "must": [
+    "Add npx create-quiver ai execute-slice.",
+    "Default role to executor and context to slice or minimal.",
+    "Require --slice path.",
+    "Require slice.json and EXECUTION_BRIEF.md.",
+    "Build an executor prompt from only the slice context pack.",
+    "Allow executor to modify code directly within declared scope.",
+    "Capture git diff before and after execution.",
+    "Run scope validation after execution.",
+    "Report scope violations clearly and fail the command."
+  ],
+  "not_included": [
+    "Automatically committing the slice.",
+    "Automatically fixing scope violations.",
+    "Running multiple executors concurrently."
+  ],
+  "acceptance": [
+    "execute-slice fails if slice.json is missing.",
+    "execute-slice fails if EXECUTION_BRIEF.md is missing.",
+    "execute-slice --dry-run prints minimal context selection without provider execution.",
+    "Post-run validation detects files outside the slice file list.",
+    "Executor prompt does not include full onboarding context.",
+    "Provider failure exits non-zero and preserves the provider error summary."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-execute-slice.test.js tests/lib/ai-executor.test.js",
+    "npm run smoke:create-quiver",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "actual_hours": 5,
+  "started_at": "2026-05-19T20:01:48-0300",
+  "completed_at": "2026-05-19T20:01:48-0300",
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-07-github-pr-preflight/CLOSURE_BRIEF.md

@@ -0,0 +1,36 @@
+# CLOSURE BRIEF - slice-07: GitHub PR preflight
+
+## Resumen de lo realizado
+
+Se implemento el preflight de GitHub para `ai pr` y `ai doctor` con validacion cross-platform de `gh`, `gh auth status`, remote Git, worktree/rama, GitFlow guide e identidad SSH. Tambien se agregaron opciones separadas para `sshHostAlias` e `identityFile`, y se cubrio `--dry-run` sin abrir PRs.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Missing `gh` cubierto.
+- [x] Missing `gh auth` cubierto.
+- [x] Missing GitFlow guide cubierto.
+- [x] Missing identity file cubierto.
+- [x] `sshHostAlias` e `identityFile` separados.
+- [x] Dry-run no crea PR.
+
+## Cambios relevantes
+
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/ai/github.js`
+- `src/create-quiver/lib/git.js`
+- `tests/commands/ai-pr.test.js`
+- `tests/lib/ai-github.test.js`
+
+## Pendientes
+
+Ninguno para esta slice.
+
+## Riesgos remanentes
+
+- `gh auth status` valida el estado de login, pero no correlaciona la cuenta de GitHub con la identidad SSH.
+- El guia GitFlow todavia depende de que el archivo `docs/GITFLOW_PR_GUIDE.md` exista en el repo consumido.
+
+## Recomendaciones futuras
+
+Agregar la apertura real de PR cuando slice-08 deje listos los artefactos finales y el flujo documental.

package/specs/quiver-v20-ai-cli-orchestration/slices/slice-07-github-pr-preflight/EXECUTION_BRIEF.md

@@ -0,0 +1,66 @@
+# EXECUTION BRIEF - slice-07: GitHub PR preflight
+
+**Spec:** quiver-v20-ai-cli-orchestration
+**Slice:** slice-07-github-pr-preflight
+**Tipo:** feature
+
+## Contexto
+
+Quiver debe preparar PRs siguiendo `docs/GITFLOW_PR_GUIDE.md`, usando `gh` y configuracion SSH portable. macOS, Linux y Windows necesitan guias distintas.
+
+## Objetivo
+
+Agregar preflight para PR con `gh`, auth, remote, worktree, GitFlow guide, `sshHostAlias` e `identityFile`.
+
+## Alcance
+
+- Validar `gh`.
+- Validar `gh auth status`.
+- Validar remote Git.
+- Validar worktree/rama.
+- Validar guia GitFlow.
+- Separar alias SSH y identity file.
+- Guiar configuracion sin modificar credenciales automaticamente.
+
+## Criterios de aceptacion
+
+- Missing `gh` muestra guia macOS/Linux/Windows.
+- `gh` no autenticado muestra `gh auth login`.
+- Falta GitFlow guide detiene el flujo.
+- Falta identity file muestra path revisado.
+- `sshHostAlias` e `identityFile` son opciones separadas.
+- Dry-run no crea PR.
+
+## Plan tecnico resumido
+
+Crear `ai/github.js` y extender preflight. Reusar helpers de Git. Los comandos externos deben usar arrays y ser mockeables en tests.
+
+## Pasos sugeridos de ejecucion
+
+1. Implementar checks de `gh`.
+2. Implementar checks de auth.
+3. Implementar checks de remote/worktree.
+4. Implementar checks SSH.
+5. Integrar en `ai doctor` y `ai pr`.
+6. Agregar tests.
+
+## Restricciones
+
+- No instalar `gh`.
+- No editar SSH config.
+- No abrir PR en tests.
+
+## Riesgos
+
+- Cuenta `gh` distinta al remote SSH.
+- Alias SSH confundido con path de key.
+- Windows path handling.
+
+## Checklist de finalizacion
+
+- [ ] Tests de PR preflight pasan.
+- [ ] Missing gh cubierto.
+- [ ] Missing auth cubierto.
+- [ ] Missing SSH cubierto.
+- [ ] Dry-run cubierto.
+