@ancleto/spec 0.6.2 → 0.6.4

package/README.md

@@ -1,120 +1,213 @@
-# ancleto
-
-Orquestador SDD liviano con subagentes optimizados para costo/tokens. Toolkit personal
-de desarrollo asistido por IA para opencode: ciclo spec-driven completo (OpenSpec),
-agents y skills, más un CLI de inicialización y descubrimiento técnico del repositorio.
-
-Binarios: `ancleto` (alias: `aspec`).
-
-## Qué incluye
-
-- **Agents (10)**: orchestrator, coder, tester, spec-writer, reviewer, documenter,
-  technical-discovery, technical-seed-writer, memory-keeper, context-resolver.
-- **Commands (12)**: `opsx-*` — ciclo de vida de changes OpenSpec (new, propose, ff,
-  apply, verify, sync, archive, bulk-archive, continue, explore, onboard, recall).
-- **Skills (7)**: `ancleto-commit`, `ancleto-pr`, `ancleto-technical-discovery`, `ancleto-upgrade`,
-  `triage-clarifier`, `openspec-recall`, `openspec-sync-specs`.
-- **Templates**: `AGENTS.md`, `PRODUCT.md` para proyectos nuevos.
-- **CLI `ancleto`**: instalación (`ancleto install`), init de proyectos (`ancleto init`) y
-  descubrimiento técnico (`ancleto discovery`, pack con Repomix).
-- **Motor de memoria (v0.2.0)**: base local `.ancleto/memory.db` sobre `node:sqlite`
-  (zero-deps, Node >= 24). Tres tools para el LLM — `searchMemory` (BM25, FTS5),
-  `recordRule` y `recordDecision` — con supersesión atómica por `memory_key`; reglas
-  inyectadas proactivamente en `<ProjectMemoryRules>` y decisiones recuperadas
-  reactivamente.
-- **Documentación**: `docs/` — `ancleto-cli-framework.md` (guía del framework),
-  `guia-configuracion.md` (puesta a punto del entorno) y `skill-ancleto-upgrade.md`.
-
-## Instalación
+<div align="center">
+
+# ☕ ANCLETO (aspec)
+**Orquestador SDD (Spec-Driven Development) y Toolkit Personal Asistido por IA**
+
+[![Node.js](https://img.shields.io/badge/Node.js-%3E%3D%2024.0.0-43853D?style=flat-square&logo=node.js&logoColor=white)](#requisitos)
+[![Version](https://img.shields.io/badge/version-v0.6.2-blue?style=flat-square)](#uso-rápido)
+[![Zero Dependencies](https://img.shields.io/badge/dependencies-zero-brightgreen?style=flat-square)](#requisitos)
+
+*Descubrimiento técnico, memoria persistente y control estricto de tokens para tu IDE.*
+
+</div>
+
+---
+
+## 📖 Tabla de Contenidos
+
+- [¿Qué es Ancleto?](#-qué-es-ancleto)
+- [¿Por qué fue creado?](#-por-qué-fue-creado)
+- [Características Principales](#-características-principales)
+- [Requisitos](#-requisitos)
+- [Instalación](#-instalación)
+- [Configuración y Tiers de Costo](#-configuración-y-tiers-de-costo)
+- [Uso Rápido](#-uso-rápido)
+- [Referencia de Comandos CLI](#-referencia-de-comandos-cli)
+- [Motor de Memoria Persistente](#-motor-de-memoria-persistente)
+- [Comandos del Ciclo SDD en tu IDE](#-comandos-del-ciclo-sdd-en-tu-ide)
+- [Azure DevOps (Opcional)](#-azure-devops-opcional)
+
+---
+
+## 🚀 ¿Qué es Ancleto?
+
+**Ancleto** (cuyo alias de CLI es `aspec`) es un orquestador ligero diseñado para potenciar el desarrollo de software asistido por Inteligencia Artificial bajo el paradigma **SDD (Spec-Driven Development)**.
+
+Funciona como un conjunto de herramientas y agentes que viven en tu entorno de desarrollo local (como OpenCode, Cursor, VS Code, Roo, etc.), permitiéndote automatizar la escritura de especificaciones, el descubrimiento topológico del código y la retención de memoria de las decisiones técnicas.
+
+Todo esto está envuelto en una CLI moderna, interactiva y construida bajo una filosofía estricta de **cero dependencias (Zero-Deps)**.
+
+## 💡 ¿Por qué fue creado?
+
+Al trabajar en repositorios complejos con asistentes de IA, surgen tres problemas críticos:
+
+1. **La "Memoria de Pez" de los LLMs:** Los agentes olvidan las convenciones del proyecto o las decisiones arquitectónicas pasadas en cuanto se limpia la ventana de contexto.
+2. **El Costo Oculto (Token Budgeting):** Empaquetar todo un monorepo para darle contexto a la IA consume presupuestos de tokens masivos y encarece el uso de las APIs.
+3. **Falta de Estandarización:** Cada agente de IA actúa por su cuenta, sin seguir un ciclo de vida definido de especificación -> revisión -> implementación -> verificación.
+
+**Ancleto** nace para resolver esto. Centraliza las reglas de negocio en un motor de memoria local (`node:sqlite`), empaqueta inteligentemente el contexto según el nivel de tu suscripción (Tiers) y orquesta 10 subagentes nativos para que el código que escriba la IA cumpla estrictamente con tus estándares, minimizando la fricción y los costos.
+
+---
+
+## ✨ Características Principales
+
+- 🤖 **Catálogo Multi-Agente (10 Agents):** Orquestador, Coder, Tester, Spec-Writer, Reviewer, Documenter, Technical-Discovery, Technical-Seed-Writer, Memory-Keeper y Context-Resolver.
+- 🧠 **Motor de Memoria Persistente (FTS5):** Base local SQLite (`.ancleto/memory.db`) que provee al LLM herramientas para registrar y recuperar reglas arquitectónicas y decisiones pasadas proactivamente.
+- 🗺️ **Discovery Engine:** Un escáner topológico rápido que genera mapas del repositorio (`.discovery-map.json`) y empaqueta el contexto vía Repomix con presupuestos de tokens dinámicos.
+- 💸 **Gestión de Tiers de Costo:** Control absoluto sobre qué modelos y cuánto contexto se envía (`normal`, `minimo`, `gratis`), protegiendo tus cuotas de API.
+- ⚡ **Agentic OpenSpec Engine:** Totalmente independiente, sin binarios externos. Las 11 skills del ciclo de vida (`new`, `propose`, `apply`, `verify`, `archive`, `bulk-archive`, `continue`, `explore`, `ff`, `onboard`, `workflow`) se instalan e inyectan nativamente en tu IDE favorito, más skills auxiliares (`ancleto-commit`, `ancleto-pr`, `triage-clarifier`, entre otras).
+- 🎨 **Wizard Interactivo:** Inicialización por TTY con banner animado y menús navegables con flechas, sin requerir librerías pesadas (Zero-Deps).
+
+---
+
+## 🛠 Requisitos
+
+Dado que Ancleto mantiene una política de cero dependencias externas, aprovecha las capacidades nativas más recientes de Node:
+
+- **Node.js >= 24.0.0** (requerido estrictamente para el módulo nativo `node:sqlite`).
+- **Repomix** (utilizado dinámicamente vía `npx` si no está instalado globalmente, para el empaquetado de contexto).
+
+---
+
+## 📦 Instalación
+
+Puedes instalar la herramienta a nivel global o por proyecto.
 
 ```bash
-ancleto install                          # global: disponible en todos tus proyectos
-ancleto install --project /ruta/repo     # por proyecto: .opencode/ + templates en la raiz
-ancleto install --no-mcp                 # igual, sin tocar la config MCP de opencode
-ancleto update                           # re-instala la ultima version
+# Instalación global (disponible en todos tus proyectos)
+npm install -g @ancleto/spec
+
+# O alternativamente a través de la CLI de ancleto:
+ancleto install
+
+# Instalación circunscrita a un proyecto específico (inyecta templates y .opencode/)
+ancleto install --project /ruta/repo
+
+# Instalación sin modificar la configuración MCP de tu IDE
+ancleto install --no-mcp
+
+# Actualizar a la última versión manteniendo tus personalizaciones
+ancleto update
 ```
 
-El instalador configura por defecto los MCP locales **engram** (memoria persistente) y
-**caveman** (compresion de contexto) en `~/.config/opencode/opencode.json`, fusionandose
-con la config existente (no pisa nada). Si un binario no se encuentra en el sistema, ese
-MCP se omite con un warning.
+*(El instalador configura por defecto los MCP locales **engram** y **caveman**. Si un binario no se encuentra en tu sistema, se omitirá con un warning sin romper el flujo).*
 
-## Tiers de costo
+---
 
-En la primera configuración (`ancleto install`) se pregunta el nivel de gasto de los
-agents; también se elige con `--tier`:
+## ⚙️ Configuración y Tiers de Costo
+
+Al ejecutar la CLI por primera vez, un **Wizard interactivo (ASCII animado)** te guiará para configurar el Agente (IDE) y tu nivel de gasto. También puedes pasarlos por flags:
 
 ```bash
-ancleto install --tier normal     # modelos opencode-go balanceados (default)
-ancleto install --tier minimo     # todo al modelo pagado mas economico viable
-ancleto install --tier gratis     # solo modelos gratuitos (ej. opencode/big-pickle)
+ancleto init --agent opencode --tier normal
 ```
 
-El nivel elegido queda guardado (`.ancleto-tier`) y `ancleto update` lo re-aplica sin
-volver a preguntar. Al llegar al tope mensual de la suscripcion, opencode cae
-automaticamente a los modelos gratuitos.
+**Tiers Disponibles:**
+
+* `normal`: Modelos balanceados sin restricciones agresivas de contexto (default).
+* `minimo`: Enfoque en el modelo pago más económico viable, con alta compresión de contexto y exclusión de tests/docs en el discovery.
+* `gratis`: Bloqueado a modelos gratuitos (ej. `opencode/big-pickle`), empaquetado ultra-agresivo y un límite estricto (budget) de tokens enviado al LLM.
+
+La configuración se preserva en `.ancletorc` (raíz del proyecto) y `.ancleto-tier` (junto a la configuración instalada).
+
+---
 
-## Requisitos
+## 💻 Uso Rápido
 
-- Node.js >= 24.0.0 (el motor de memoria v0.2.0 usa `node:sqlite`)
-- `openspec` CLI (`npm i -g @openspec/cli`) para el ciclo de changes
-- Repomix (usado por `ancleto discovery`, se resuelve via `npx` si no esta instalado)
+El ciclo diario con Ancleto consiste en preparar el terreno técnico para tu Agente y luego usar los comandos del ciclo SDD dentro de tu IDE.
 
-## Uso rápido
+### 1. Inicialización en un Repositorio
 
 ```bash
-ancleto init                             # prepara .ancletorc en el repo actual
-ancleto init --with-azure                # lo mismo, con Azure habilitado
-ancleto discovery --check                # estado del technical seed (READY/STALE/PARTIAL/MISSING)
-ancleto discovery                        # empaca el repo con Repomix y guarda estado
-# en opencode: /opsx-new, /opsx-propose, /opsx-ff para iniciar un change
+cd tu-proyecto
+ancleto init              # Crea .ancletorc, plantillas AGENTS.md y PRODUCT.md
 ```
 
-## Azure DevOps (opcional)
-
-Azure viene **desactivado por defecto**. Para activarlo en un proyecto:
+### 2. Descubrimiento Técnico de Contexto
 
 ```bash
-ancleto init --with-azure    # escribe .ancletorc con azure.enabled: true
+ancleto discovery --check # Verifica si el 'technical seed' requiere actualización (READY/STALE)
+ancleto discovery         # Genera .discovery-map.json y empaqueta el repo
 ```
 
-Luego completar la seccion `Azure DevOps` de `PRODUCT.md` (Organization URL, Team Project)
-e instalar el CLI: `az extension add --name azure-devops`. Con `azure.enabled: false` (o sin
-`.ancletorc`), los flujos tratan cada request como sin Work Item y `ancleto-pr` usa GitHub.
+### 3. Integración Diaria
+
+Utiliza los comandos barra (`/`) expuestos en el chat de tu IDE (ej. Cursor, OpenCode):
+
+* `/cleto-new` y `/cleto-propose`: Para planificar un nuevo feature.
+* `/cleto-verify` y `/cleto-apply`: Para validar reglas, chequear tests y aplicar el código.
+* `/cleto-archive`: Para consolidar el historial y registrar aprendizajes en la memoria de Ancleto.
+
+---
 
-## Flujo de release
+## 📟 Referencia de Comandos CLI
 
-Publicación automática vía GitHub Actions (`publish.yml`):
+Todos los comandos de mantenimiento que puedes necesitar en el día a día:
 
 ```bash
-# 1. Bump local (regla: todo commit de feature lleva su version bump)
-npm version patch --no-git-tag-version        # o: minor, segun el cambio
-git add package.json package-lock.json
-git commit -m "chore: bump version to X.Y.Z"
-git push origin development
-
-# 2. Merge development -> main
-git checkout main
-git pull origin main
-git merge development
-
-# 3. Tag anotado y push
-git tag -a vX.Y.Z -m "vX.Y.Z - <resumen>"
-git push origin main
-git push origin vX.Y.Z
-
-# 4. GitHub Release
-# En GitHub: Releases -> Draft a new release -> elegir el tag vX.Y.Z -> Publish release
+ancleto init [--agent <nombre>] [--tier <nivel>] [--with-azure]
+                          # Configura el proyecto (interactivo en TTY)
+
+ancleto install [--project <dir>] [--tier <nivel>] [--agent <nombre>] [--no-mcp]
+                          # Instala agents, skills y templates
+
+ancleto update            # Re-instala la última versión sobre lo existente
+
+ancleto upgrade           # Re-aplica templates y skills respetando tus personalizaciones
+
+ancleto check             # Verifica la integridad de la instalación (0 faltantes, 0 huérfanos)
+
+ancleto doctor            # Diagnostica el entorno (Node, node:sqlite, opencode.json)
+
+ancleto memory context [--scope <project|feature|task>] [--out <archivo>]
+                          # Muestra el bloque de memoria activa del proyecto
+
+ancleto memory doctor [--rebuild]
+                          # Diagnostica la base de memoria (y reconstruye el índice con --rebuild)
+
+ancleto discovery [--compress] [--include <glob>] [--ignore <glob>] [--token-budget <n>]
+                          # Empaqueta el repo con Repomix según tu tier
 ```
 
-Al publicar la Release, el workflow `publish.yml` se dispara (`on.release.types: [published]`):
-corre `node --test` en `ubuntu-latest` (Node 24, checkout@v5/setup-node@v5) y publica a npm con
-`NODE_AUTH_TOKEN` (secret `NPM_TOKEN` del repo).
+---
+
+## 🧠 Motor de Memoria Persistente
+
+Ancleto **no** usa bases de datos vectoriales pesadas. Implementa una solución elegante en **SQLite nativo** con búsqueda full-text (FTS5) y BM25.
+
+El LLM tiene a su disposición 3 herramientas (tools):
+
+* `searchMemory`: Recupera contexto de decisiones previas.
+* `recordRule`: Guarda una regla arquitectónica estricta de manera jerárquica (Proyecto > Feature > Tarea).
+* `recordDecision`: Inmortaliza el "por qué" de un cambio en el código.
+
+El orquestador inyecta proactivamente los bloques `<ProjectMemoryRules>` y `<ProjectTopology>` (contexto desde el día cero, incluso sin reglas previas) en el System Prompt de tu Agente para que **nunca repita los mismos errores**.
+
+---
+
+## 🔄 Comandos del Ciclo SDD en tu IDE
 
-## Estado
+Una vez instalado, tu IDE expone el ciclo de vida completo como comandos barra (`/`):
+
+| Comando | Para qué sirve |
+|---|---|
+| `/cleto-new` | Iniciar la especificación de un feature |
+| `/cleto-propose` | Proponer el diseño técnico |
+| `/cleto-ff` | Avanzar rápido con contexto recuperado |
+| `/cleto-apply` | Aplicar el código del change |
+| `/cleto-verify` | Verificar reglas, tests y memoria antes de cerrar |
+| `/cleto-sync` | Sincronizar specs con el estado del repo |
+| `/cleto-archive` | Archivar el change y registrar aprendizajes |
+| `/cleto-continue`, `/cleto-explore`, `/cleto-onboard` | Retomar, explorar y orientarse en el proyecto |
+
+---
+
+## 🔗 Azure DevOps (Opcional)
+
+Por defecto, los comandos asumen el uso de **GitHub** (`ancleto-pr`). Si tu equipo utiliza Azure DevOps:
+
+```bash
+ancleto init --with-azure
+```
 
-- [x] Paquete y CLI de instalación
-- [x] Agents/skills/commands adaptados (sin referencias corporativas)
-- [x] Motor de descubrimiento (`ancleto discovery`, Repomix + `--check` por hash)
-- [x] Skills base: `triage-clarifier`, `openspec-recall`, `openspec-sync-specs`
-- [x] Motor de memoria core (v0.2.0): `.ancleto/memory.db`, 3 tools, supersesión atómica
+Esto escribe `azure.enabled: true` en tu `.ancletorc`. Solo deberás completar la sección de Azure en el archivo `PRODUCT.md` e instalar su extensión (`az extension add --name azure-devops`).

package/agents/spec-writer.md

@@ -28,7 +28,7 @@ Generate an OpenSpec change in:
 
 - `openspec/changes/{change-name}/`
 
-using the `openspec-workflow` skill and the conventions of:
+using the `ancleto-workflow` skill and the conventions of:
 
 - `AGENTS.md`
 
@@ -36,7 +36,7 @@ using the `openspec-workflow` skill and the conventions of:
 
 1. Use the repository context received in the delegation, including its cited source paths and seed state; exploratory sweeping is prohibited. You MAY open a specific path that the received context cites when a detail needs confirmation.
 2. Read relevant source-of-truth specs in `openspec/specs/` when they exist
-3. Load and follow the `openspec-workflow` skill
+3. Load and follow the `ancleto-workflow` skill
 4. Create a clear `change-name`
 5. Generate the minimum correct set of artifacts for the requested change:
    - `proposal.md`

package/commands/{opsx-apply.md → cleto-apply.md}

@@ -4,7 +4,7 @@ description: Implement tasks from an OpenSpec change (Experimental)
 
 Implement tasks from an OpenSpec change.
 
-**Input**: Optionally specify a change name (e.g., `/opsx-apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+**Input**: Optionally specify a change name (e.g., `/cleto-apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
 **Steps**
 
@@ -16,7 +16,7 @@ Implement tasks from an OpenSpec change.
    - Auto-select if only one active change exists
    - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
 
-   Always announce: "Using change: <name>" and how to override (e.g., `/opsx-apply <other>`).
+   Always announce: "Using change: <name>" and how to override (e.g., `/cleto-apply <other>`).
 
 2. **Check status to understand the schema**
 
@@ -44,7 +44,7 @@ Implement tasks from an OpenSpec change.
 
    **Handle states:**
 
-   - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx-continue`
+   - If `state: "blocked"` (missing artifacts): show message, suggest using `/cleto-continue`
    - If `state: "all_done"`: congratulate, suggest archive
    - Otherwise: proceed to implementation
 
@@ -119,7 +119,7 @@ Working on task 4/7: <task description>
 - [x] Task 2
 ...
 
-All tasks complete! You can archive this change with `/opsx-archive`.
+All tasks complete! You can archive this change with `/cleto-archive`.
 ```
 
 **Output On Pause (Issue Encountered)**

package/commands/{opsx-archive.md → cleto-archive.md}

@@ -4,7 +4,7 @@ description: Archive a completed change in the experimental workflow
 
 Archive a completed change in the experimental workflow.
 
-**Input**: Optionally specify a change name after `/opsx-archive` (e.g., `/opsx-archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+**Input**: Optionally specify a change name after `/cleto-archive` (e.g., `/cleto-archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
 **Steps**
 
@@ -61,7 +61,7 @@ Archive a completed change in the experimental workflow.
    - If changes needed: "Sync now (recommended)", "Archive without syncing"
    - If already synced: "Archive now", "Sync anyway", "Cancel"
 
-   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke ancleto-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
 
 5. **Perform the archive**
 
@@ -167,5 +167,5 @@ Target archive directory already exists.
 - Don't block archive on warnings - just inform and confirm
 - Preserve .openspec.yaml when moving to archive (it moves with the directory)
 - Show clear summary of what happened
-- If sync is requested, use the Skill tool to invoke `openspec-sync-specs` (agent-driven)
+- If sync is requested, use the Skill tool to invoke `ancleto-sync-specs` (agent-driven)
 - If delta specs exist, always run the sync assessment and show the combined summary before prompting

package/commands/{opsx-bulk-archive.md → cleto-bulk-archive.md}

@@ -124,7 +124,7 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
 
    a. **Sync specs** if delta specs exist:
 
-   - Use the openspec-sync-specs approach (agent-driven intelligent merge)
+   - Use the ancleto-sync-specs approach (agent-driven intelligent merge)
    - For conflicts, apply in resolved order
    - Track if sync was done
 

package/commands/{opsx-continue.md → cleto-continue.md}

@@ -4,7 +4,7 @@ description: Continue working on a change - create the next artifact (Experiment
 
 Continue working on a change by creating the next artifact.
 
-**Input**: Optionally specify a change name after `/opsx-continue` (e.g., `/opsx-continue add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+**Input**: Optionally specify a change name after `/cleto-continue` (e.g., `/cleto-continue add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
 **Steps**
 
@@ -53,7 +53,7 @@ Continue working on a change by creating the next artifact.
 
    - Congratulate the user
    - Show final status including the schema used
-   - Suggest: "All artifacts created! You can now implement this change with `/opsx-apply` or archive it with `/opsx-archive`."
+   - Suggest: "All artifacts created! You can now implement this change with `/cleto-apply` or archive it with `/cleto-archive`."
    - STOP
 
    ***
@@ -102,7 +102,7 @@ After each invocation, show:
 - Schema workflow being used
 - Current progress (N/M complete)
 - What artifacts are now unlocked
-- Prompt: "Run `/opsx-continue` to create the next artifact"
+- Prompt: "Run `/cleto-continue` to create the next artifact"
 
 **Artifact Creation Guidelines**
 

package/commands/{opsx-explore.md → cleto-explore.md}

@@ -8,7 +8,7 @@ Enter explore mode. Think deeply. Visualize freely. Follow the conversation wher
 
 **This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
 
-**Input**: The argument after `/opsx-explore` is whatever the user wants to think about. Could be:
+**Input**: The argument after `/cleto-explore` is whatever the user wants to think about. Could be:
 
 - A vague idea: "real-time collaboration"
 - A specific problem: "the auth system is getting unwieldy"

package/commands/{opsx-ff.md → cleto-ff.md}

@@ -4,7 +4,7 @@ description: Create a change and generate all artifacts needed for implementatio
 
 Fast-forward through artifact creation - generate everything needed to start implementation.
 
-**Input**: The argument after `/opsx-ff` is the change name (kebab-case), OR a description of what the user wants to build.
+**Input**: The argument after `/cleto-ff` is the change name (kebab-case), OR a description of what the user wants to build.
 
 **Steps**
 
@@ -108,7 +108,7 @@ After completing all artifacts, summarize:
 - Change name and location
 - List of artifacts created with brief descriptions
 - What's ready: "All artifacts created! Ready for implementation."
-- Prompt: "Run `/opsx-apply` to start implementing."
+- Prompt: "Run `/cleto-apply` to start implementing."
 
 **Artifact Creation Guidelines**
 

package/commands/{opsx-new.md → cleto-new.md}

@@ -1,10 +1,10 @@
 ---
-description: Start a new change using the experimental artifact workflow (OPSX)
+description: Start a new change using the experimental artifact workflow
 ---
 
 Start a new change using the experimental artifact-driven approach.
 
-**Input**: The argument after `/opsx-new` is the change name (kebab-case), OR a description of what the user wants to build.
+**Input**: The argument after `/cleto-new` is the change name (kebab-case), OR a description of what the user wants to build.
 
 **Steps**
 
@@ -106,12 +106,12 @@ After completing the steps, summarize:
 - Schema/workflow being used and its artifact sequence
 - Current status (0/N artifacts complete)
 - The template for the first artifact
-- Prompt: "Ready to create the first artifact? Run `/opsx-continue` or just describe what this change is about and I'll draft it."
+- Prompt: "Ready to create the first artifact? Run `/cleto-continue` or just describe what this change is about and I'll draft it."
 
 **Guardrails**
 
 - Do NOT create any artifacts yet - just show the instructions
 - Do NOT advance beyond showing the first artifact template
 - If the name is invalid (not kebab-case), ask for a valid name
-- If a change with that name already exists, suggest using `/opsx-continue` instead
+- If a change with that name already exists, suggest using `/cleto-continue` instead
 - Pass --schema if using a non-default workflow

package/commands/{opsx-onboard.md → cleto-onboard.md}

@@ -19,7 +19,7 @@ openspec --version 2>&1 || echo "CLI_NOT_INSTALLED"
 
 **If CLI not installed:**
 
-> OpenSpec CLI is not installed. Install it first, then come back to `/opsx-onboard`.
+> OpenSpec CLI is not installed. Install it first, then come back to `/cleto-onboard`.
 
 Stop here if not installed.
 
@@ -149,7 +149,7 @@ Spend 1-2 minutes investigating the relevant code:
 │   [Optional: ASCII diagram if helpful]  │
 └─────────────────────────────────────────┘
 
-Explore mode (`/opsx-explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
+Explore mode (`/cleto-explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
 
 Now let's create a change to hold our work.
 ```
@@ -483,25 +483,25 @@ This same rhythm works for any size change—a small fix or a major feature.
 
 | Command | What it does |
 |---------|--------------|
-| `/opsx-propose` | Create a change and generate all artifacts |
-| `/opsx-explore` | Think through problems before/during work |
-| `/opsx-apply` | Implement tasks from a change |
-| `/opsx-archive` | Archive a completed change |
+| `/cleto-propose` | Create a change and generate all artifacts |
+| `/cleto-explore` | Think through problems before/during work |
+| `/cleto-apply` | Implement tasks from a change |
+| `/cleto-archive` | Archive a completed change |
 
 **Additional commands:**
 
 | Command | What it does |
 |---------|--------------|
-| `/opsx-new` | Start a new change, step through artifacts one at a time |
-| `/opsx-continue` | Continue working on an existing change |
-| `/opsx-ff` | Fast-forward: create all artifacts at once |
-| `/opsx-verify` | Verify implementation matches artifacts |
+| `/cleto-new` | Start a new change, step through artifacts one at a time |
+| `/cleto-continue` | Continue working on an existing change |
+| `/cleto-ff` | Fast-forward: create all artifacts at once |
+| `/cleto-verify` | Verify implementation matches artifacts |
 
 ---
 
 ## What's Next?
 
-Try `/opsx-propose` on something you actually want to build. You've got the rhythm now!
+Try `/cleto-propose` on something you actually want to build. You've got the rhythm now!
 ```
 
 ---
@@ -516,8 +516,8 @@ If the user says they need to stop, want to pause, or seem disengaged:
 No problem! Your change is saved at `openspec/changes/<name>/`.
 
 To pick up where we left off later:
-- `/opsx-continue <name>` - Resume artifact creation
-- `/opsx-apply <name>` - Jump to implementation (if tasks exist)
+- `/cleto-continue <name>` - Resume artifact creation
+- `/cleto-apply <name>` - Jump to implementation (if tasks exist)
 
 The work won't be lost. Come back whenever you're ready.
 ```
@@ -535,21 +535,21 @@ If the user says they just want to see the commands or skip the tutorial:
 
 | Command | What it does |
 |---------|--------------|
-| `/opsx-propose <name>` | Create a change and generate all artifacts |
-| `/opsx-explore` | Think through problems (no code changes) |
-| `/opsx-apply <name>` | Implement tasks |
-| `/opsx-archive <name>` | Archive when done |
+| `/cleto-propose <name>` | Create a change and generate all artifacts |
+| `/cleto-explore` | Think through problems (no code changes) |
+| `/cleto-apply <name>` | Implement tasks |
+| `/cleto-archive <name>` | Archive when done |
 
 **Additional commands:**
 
 | Command | What it does |
 |---------|--------------|
-| `/opsx-new <name>` | Start a new change, step by step |
-| `/opsx-continue <name>` | Continue an existing change |
-| `/opsx-ff <name>` | Fast-forward: all artifacts at once |
-| `/opsx-verify <name>` | Verify implementation |
+| `/cleto-new <name>` | Start a new change, step by step |
+| `/cleto-continue <name>` | Continue an existing change |
+| `/cleto-ff <name>` | Fast-forward: all artifacts at once |
+| `/cleto-verify <name>` | Verify implementation |
 
-Try `/opsx-propose` to start your first change.
+Try `/cleto-propose` to start your first change.
 ```
 
 Exit gracefully.

package/commands/{opsx-propose.md → cleto-propose.md}

@@ -10,11 +10,11 @@ I'll create a change with artifacts:
 - design.md (how)
 - tasks.md (implementation steps)
 
-When ready to implement, run /opsx-apply
+When ready to implement, run /cleto-apply
 
 ---
 
-**Input**: The argument after `/opsx-propose` is the change name (kebab-case), OR a description of what the user wants to build.
+**Input**: The argument after `/cleto-propose` is the change name (kebab-case), OR a description of what the user wants to build.
 
 **Steps**
 
@@ -118,7 +118,7 @@ After completing all artifacts, summarize:
 - Change name and location
 - List of artifacts created with brief descriptions
 - What's ready: "All artifacts created! Ready for implementation."
-- Prompt: "Run `/opsx-apply` to start implementing."
+- Prompt: "Run `/cleto-apply` to start implementing."
 
 **Artifact Creation Guidelines**
 

package/commands/{opsx-recall.md → cleto-recall.md}

@@ -4,13 +4,13 @@ description: Recuperar memoria episódica del proyecto (.ancleto/memory.db) sobr
 
 Recuperar de la memoria compartida del repositorio lo que se aprendió en changes anteriores sobre un tema.
 
-Este comando es la invocación **a mano** de la memoria. La invocación automática vive dentro de `/opsx-new`, `/opsx-propose` y `/opsx-ff`, que ejecutan el mismo paso al iniciar un change. El contrato completo está en la skill `openspec-recall`.
+Este comando es la invocación **a mano** de la memoria. La invocación automática vive dentro de `/cleto-new`, `/cleto-propose` y `/cleto-ff`, que ejecutan el mismo paso al iniciar un change. El contrato completo está en la skill `ancleto-recall`.
 
-**Input**: el argumento después de `/opsx-recall` es el tema a consultar. Por ejemplo:
+**Input**: el argumento después de `/cleto-recall` es el tema a consultar. Por ejemplo:
 
-- `/opsx-recall autenticación JWT en LiteLLM`
-- `/opsx-recall por qué elegimos pgvector`
-- `/opsx-recall` (sin argumento — ver paso 1)
+- `/cleto-recall autenticación JWT en LiteLLM`
+- `/cleto-recall por qué elegimos pgvector`
+- `/cleto-recall` (sin argumento — ver paso 1)
 
 **Steps**
 
@@ -53,5 +53,5 @@ Este comando es la invocación **a mano** de la memoria. La invocación automát
 
 **Referencia**
 
-- Contrato completo: skill `openspec-recall`
+- Contrato completo: skill `ancleto-recall`
 - Contrato de lectura y modelo de scope: `AGENTS.md` (Memoria Persistente)

package/commands/{opsx-sync.md → cleto-sync.md}

@@ -6,7 +6,7 @@ Sync delta specs from a change to main specs.
 
 This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
 
-**Input**: Optionally specify a change name after `/opsx-sync` (e.g., `/opsx-sync add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+**Input**: Optionally specify a change name after `/cleto-sync` (e.g., `/cleto-sync add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
 **Steps**
 

package/commands/{opsx-verify.md → cleto-verify.md}

@@ -4,7 +4,7 @@ description: Verify implementation matches change artifacts before archiving
 
 Verify that an implementation matches the change artifacts (specs, tasks, design).
 
-**Input**: Optionally specify a change name after `/opsx-verify` (e.g., `/opsx-verify add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+**Input**: Optionally specify a change name after `/cleto-verify` (e.g., `/cleto-verify add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
 **Steps**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ancleto/spec",
-  "version": "0.6.2",
+  "version": "0.6.4",
   "description": "Orquestador SDD liviano con subagentes optimizados para costo/tokens",
   "type": "module",
   "bin": {

package/skills/{openspec-apply → ancleto-apply}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-apply
+name: ancleto-apply
 description: Implement tasks from a change step by step, tracking progress in tasks.md. Use when artifacts are ready and implementation should start. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -78,7 +78,7 @@ For each pending task (`- [ ]`):
 **Change:** <change-name>
 **Progress:** N/N tasks complete ✓
 
-All tasks complete! You can archive this change with `openspec-archive`.
+All tasks complete! You can archive this change with `ancleto-archive`.
 ```
 
 **On pause:**

package/skills/{openspec-archive → ancleto-archive}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-archive
+name: ancleto-archive
 description: Archive a completed change, syncing delta specs first when needed. Use when implementation and verification are done. Captures lessons into persistent memory. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.

package/skills/{openspec-bulk-archive → ancleto-bulk-archive}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-bulk-archive
+name: ancleto-bulk-archive
 description: Archive multiple completed changes in one batch, resolving spec conflicts by checking the codebase. Use when several changes are done and should be archived together. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.

package/skills/{openspec-continue → ancleto-continue}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-continue
+name: ancleto-continue
 description: Continue working on an existing change by creating its next missing artifact. Use to resume artifact creation one step at a time. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -29,7 +29,7 @@ Read `openspec/changes/<name>/` and check for artifact files in this fixed depen
 
 The first item in this order that is absent (or, for `specs/`, contains no `spec.md`) is the next artifact to create.
 
-- **If all four are present**: congratulate the user, show the status, and suggest "All artifacts created! You can now implement this change with `openspec-apply` or archive it with `openspec-archive`." STOP.
+- **If all four are present**: congratulate the user, show the status, and suggest "All artifacts created! You can now implement this change with `ancleto-apply` or archive it with `ancleto-archive`." STOP.
 - **If the change directory does not exist**: report it and stop.
 
 ### 2. Load context files
@@ -38,7 +38,7 @@ Read every artifact that IS present — they constrain what you write next. If a
 
 ### 3. Create exactly ONE artifact
 
-Draft the missing artifact using the same templates as `openspec-propose`:
+Draft the missing artifact using the same templates as `ancleto-propose`:
 
 - **proposal.md** (first artifact): problem statement, proposed change, scope, risks. If Work Item context is available, use its title/description as the problem statement, acceptance criteria as the requirements basis, and include a `## Related Work Item` section: `**#{id}** — {title} ({type}) · Project: {project}`.
 - **specs/\<capability\>/spec.md**: one spec file per capability the change touches, with `## ADDED Requirements` / `#### Scenario:` blocks in WHEN/THEN form.
@@ -54,7 +54,7 @@ Report:
 - Which artifact was created.
 - Current progress (N/4 complete).
 - What is unlocked next.
-- Prompt: "Run `openspec-continue` to create the next artifact."
+- Prompt: "Run `ancleto-continue` to create the next artifact."
 
 Create ONE artifact per invocation, then STOP.
 

package/skills/{openspec-explore → ancleto-explore}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-explore
+name: ancleto-explore
 description: Enter explore mode — think through ideas, investigate problems, and clarify requirements without implementing. Consults prior team memory first. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.

package/skills/{openspec-ff → ancleto-ff}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-ff
+name: ancleto-ff
 description: Fast-forward artifact creation — create a change and generate everything needed for implementation in one go. Use when the path is clear and no step-by-step guidance is wanted. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -57,7 +57,7 @@ Summarize:
 - Change name and location
 - List of artifacts created with brief descriptions
 - What's ready: "All artifacts created! Ready for implementation."
-- Prompt: "Run `openspec-apply` to start implementing."
+- Prompt: "Run `ancleto-apply` to start implementing."
 
 ## Artifact Creation Guidelines
 

package/skills/{openspec-new → ancleto-new}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-new
+name: ancleto-new
 description: Start a new spec-driven change without external binaries. Use when the user wants to begin structured work on a feature, fix, or modification. Creates the change directory, recalls prior memory, and shows the first artifact template.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -84,7 +84,7 @@ After completing the steps, summarize:
 - Change name and location
 - Artifact sequence and current status (0/4 artifacts complete)
 - The template for the first artifact
-- Prompt: "Ready to create the first artifact? Run `openspec-propose` or just describe what this change is about and I'll draft it."
+- Prompt: "Ready to create the first artifact? Run `ancleto-propose` or just describe what this change is about and I'll draft it."
 
 ## Guardrails
 

package/skills/{openspec-onboard → ancleto-onboard}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-onboard
+name: ancleto-onboard
 description: Guided onboarding — walk through a complete spec-driven cycle (idea to archive) on a real small task, with narration. Use for a first-time user of the workflow. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -119,16 +119,16 @@ Congratulate, recap the cycle (Explore → New → Proposal → Specs → Design
 
 | Command | What it does |
 |---------|--------------|
-| `openspec-propose` | Create a change and generate all artifacts |
-| `openspec-explore` | Think through problems before/during work |
-| `openspec-apply` | Implement tasks from a change |
-| `openspec-archive` | Archive a completed change |
-| `openspec-new` | Start a new change, step by step |
-| `openspec-continue` | Continue an existing change |
-| `openspec-ff` | Fast-forward: all artifacts at once |
-| `openspec-verify` | Verify implementation |
-
-**Graceful exits:** if the user wants to stop mid-way, point at the saved change directory and the resume skills (`openspec-continue`, `openspec-apply`). If they only want the reference, show the table and exit.
+| `ancleto-propose` | Create a change and generate all artifacts |
+| `ancleto-explore` | Think through problems before/during work |
+| `ancleto-apply` | Implement tasks from a change |
+| `ancleto-archive` | Archive a completed change |
+| `ancleto-new` | Start a new change, step by step |
+| `ancleto-continue` | Continue an existing change |
+| `ancleto-ff` | Fast-forward: all artifacts at once |
+| `ancleto-verify` | Verify implementation |
+
+**Graceful exits:** if the user wants to stop mid-way, point at the saved change directory and the resume skills (`ancleto-continue`, `ancleto-apply`). If they only want the reference, show the table and exit.
 
 ## Guardrails
 

package/skills/{openspec-propose → ancleto-propose}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: openspec-propose
-description: Draft all artifacts for a change in one step (proposal, design, tasks, delta specs). Use after openspec-new, or directly with a change name or description. No external binaries required.
+name: ancleto-propose
+description: Draft all artifacts for a change in one step (proposal, design, tasks, delta specs). Use after ancleto-new, or directly with a change name or description. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
 metadata:
@@ -18,7 +18,7 @@ Create a change and generate all its artifacts in one step, writing files direct
 
 ### 1. Resolve context and derive the change name
 
-Same as `openspec-new` step 1: use in-session Work Item context if available (record id/title/project for traceability, skip entirely when Azure DevOps is not configured), otherwise ask what the user wants to build and derive a kebab-case name.
+Same as `ancleto-new` step 1: use in-session Work Item context if available (record id/title/project for traceability, skip entirely when Azure DevOps is not configured), otherwise ask what the user wants to build and derive a kebab-case name.
 
 **IMPORTANT**: Do NOT proceed without a change name. If a change with that name already exists, ask whether to continue it or create a new one.
 
@@ -122,7 +122,7 @@ After completing all artifacts, summarize:
 - Change name and location
 - List of artifacts created with brief descriptions
 - What's ready: "All artifacts created! Ready for implementation."
-- Prompt: "Run `openspec-apply` to start implementing."
+- Prompt: "Run `ancleto-apply` to start implementing."
 
 ## Artifact Creation Guidelines
 

package/skills/{openspec-recall → ancleto-recall}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-recall
+name: ancleto-recall
 description: Recupera memoria episódica del proyecto (.ancleto/memory.db) para precargar contexto de changes anteriores. Se invoca al iniciar un change, antes de generar artifacts. Opcional y no bloqueante.
 license: MIT
 compatibility: Requires the memory engine configured in the repo. Optional — degrades silently when unavailable.
@@ -10,14 +10,14 @@ metadata:
 
 Retrieve shared episodic memory for this repository and inject it as starting context for a change.
 
-This skill is the **single source of truth** for the recall contract. The change-creation flows (`opsx-new`, `opsx-propose`, `opsx-ff`) carry this step inline; those inline blocks must stay in sync with this file.
+This skill is the **single source of truth** for the recall contract. The change-creation flows (`cleto-new`, `cleto-propose`, `cleto-ff`) carry this step inline; those inline blocks must stay in sync with this file.
 
 **Two invocation paths, one contract:**
 
 | Path | Trigger | On failure or empty result |
 | --- | --- | --- |
 | **Automatic** | Inside the change-creation flows, before generating artifacts | Silent — omit the section, never block |
-| **Manual** | The `/opsx-recall` command, invoked by the user | **Report it** — the user asked explicitly |
+| **Manual** | The `/cleto-recall` command, invoked by the user | **Report it** — the user asked explicitly |
 
 Steps 1 to 3 are identical for both. Only the failure behaviour differs, and it differs for a reason: silence is correct when nobody asked, and wrong when somebody did.
 

package/skills/{openspec-sync-specs → ancleto-sync-specs}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-sync-specs
+name: ancleto-sync-specs
 description: Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
 license: MIT
 compatibility: Requires openspec CLI.

package/skills/ancleto-upgrade/SKILL.md

@@ -431,7 +431,7 @@ build: sí/no | lint: sí/no | test: sí/no | test:ci: sí/no | typecheck: sí/n
 - tasks.md ✅ ({N} tareas en 6 fases)
 - design.md ✅
 
-Para implementar: /opsx-apply {CHANGE_NAME}
+Para implementar: /cleto-apply {CHANGE_NAME}
 ```
 
 ---
@@ -439,7 +439,7 @@ Para implementar: /opsx-apply {CHANGE_NAME}
 ## Guardrails
 
 Este skill solo genera artefactos OpenSpec — no modifica ningún archivo del repo.
-Todo cambio real lo ejecuta el desarrollador con `/opsx-apply`, que tiene su propio
+Todo cambio real lo ejecuta el desarrollador con `/cleto-apply`, que tiene su propio
 ciclo de revisión. Modificar el repo desde este skill saltearía ese control.
 
 - No tocar archivos fuera de `openspec/changes/{CHANGE_NAME}/`

package/skills/{openspec-verify → ancleto-verify}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-verify
+name: ancleto-verify
 description: Verify an implementation against its change artifacts (completeness, correctness, coherence). Use before archiving a change. Captures architectural findings into persistent memory. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.

package/skills/{openspec-workflow → ancleto-workflow}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: openspec-workflow
+name: ancleto-workflow
 description: Router for the spec-driven lifecycle — know which stage you're in and which skill runs next. Use when unsure where a request fits, or to explain the full cycle. No external binaries required.
 license: MIT
 compatibility: No external binaries required. Works with any agent runtime.
@@ -28,28 +28,28 @@ explore → new/propose/ff → continue* → apply → verify → archive
 
 | User wants to… | Run |
 |---|---|
-| Think through an idea or problem, no commitment yet | `openspec-explore` |
-| Start structured work on something new | `openspec-new` (step by step) or `openspec-propose` (all artifacts at once) |
-| Skip straight to a full draft when the path is clear | `openspec-ff` |
-| Resume a change with missing artifacts | `openspec-continue` (repeat until complete) |
-| Implement tasks from ready artifacts | `openspec-apply` |
-| Check implementation against artifacts before closing | `openspec-verify` |
-| Close one finished change (syncing its specs) | `openspec-archive` |
-| Close several finished changes at once | `openspec-bulk-archive` |
-| Learn the whole cycle hands-on | `openspec-onboard` |
+| Think through an idea or problem, no commitment yet | `ancleto-explore` |
+| Start structured work on something new | `ancleto-new` (step by step) or `ancleto-propose` (all artifacts at once) |
+| Skip straight to a full draft when the path is clear | `ancleto-ff` |
+| Resume a change with missing artifacts | `ancleto-continue` (repeat until complete) |
+| Implement tasks from ready artifacts | `ancleto-apply` |
+| Check implementation against artifacts before closing | `ancleto-verify` |
+| Close one finished change (syncing its specs) | `ancleto-archive` |
+| Close several finished changes at once | `ancleto-bulk-archive` |
+| Learn the whole cycle hands-on | `ancleto-onboard` |
 | Recall what the team learned about a topic | `searchMemory` directly (or the recall contract) |
 
 **By change state** (read `openspec/changes/<name>/`):
 
 | State | Run |
 |---|---|
-| Directory missing → nothing to continue | `openspec-new` (or propose/ff) |
-| `proposal.md` missing | `openspec-continue` |
-| `specs/` or `design.md` missing | `openspec-continue` |
-| `tasks.md` missing | `openspec-continue` |
-| All artifacts present, tasks unchecked | `openspec-apply` |
-| All tasks checked | `openspec-verify`, then `openspec-archive` |
-| Several changes complete | `openspec-bulk-archive` |
+| Directory missing → nothing to continue | `ancleto-new` (or propose/ff) |
+| `proposal.md` missing | `ancleto-continue` |
+| `specs/` or `design.md` missing | `ancleto-continue` |
+| `tasks.md` missing | `ancleto-continue` |
+| All artifacts present, tasks unchecked | `ancleto-apply` |
+| All tasks checked | `ancleto-verify`, then `ancleto-archive` |
+| Several changes complete | `ancleto-bulk-archive` |
 
 ## Handoff Contract
 

package/skills/triage-clarifier/SKILL.md

@@ -96,6 +96,6 @@ If option 4 happened and the answer still does not remove the main ambiguity, cl
 ## What not to do
 
 - do not create specs, design, tasks, or proposals
-- do not trigger opsx or any workflow handoff
+- do not trigger cleto or any workflow handoff
 - do not ask more than one clarification question
 - do not replace the orchestrator's final responsibility for classification

package/src/cli/index.js

@@ -1,4 +1,5 @@
 #!/usr/bin/env node
+import { existsSync } from 'node:fs'
 import { cp, mkdir, access, writeFile, readFile, readdir } from 'node:fs/promises'
 import { spawnSync } from 'node:child_process'
 import { createHash } from 'node:crypto'
@@ -86,17 +87,21 @@ function globalConfigDir() {
     : join(homedir(), '.config', 'opencode')
 }
 
+function binName(base) {
+  return process.platform === 'win32' ? `${base}.exe` : base
+}
+
 function resolveBin(name, fallbacks = []) {
   const probe = process.platform === 'win32' ? 'where' : 'which'
   const r = spawnSync(probe, [name], { encoding: 'utf8' })
   if (r.status === 0 && r.stdout) {
-    const first = r.stdout.split(/\r?\n/)
-      .map((s) => s.trim())
-      .find((s) => s && !/^informacion:/i.test(s))
-    if (first) return first
+    for (const line of r.stdout.split(/\r?\n/)) {
+      const candidate = line.trim()
+      if (candidate && !/^informacion:/i.test(candidate)) return candidate
+    }
   }
   for (const fb of fallbacks) {
-    if (fb) return fb
+    if (fb && existsSync(fb)) return fb
   }
   return null
 }
@@ -104,16 +109,21 @@ function resolveBin(name, fallbacks = []) {
 function buildDefaultMcp() {
   const mcp = {}
 
-  const engramBin = resolveBin('engram', [join(homedir(), 'go', 'bin', 'engram.exe')])
+  const engramFallbacks = [
+    join(homedir(), 'go', 'bin', binName('engram')),
+    join(homedir(), '.local', 'bin', binName('engram'))
+  ]
+  const engramBin = resolveBin('engram', engramFallbacks)
   if (engramBin) {
     mcp.engram = { type: 'local', enabled: true, command: [engramBin, 'mcp', '--tools=agent'] }
   } else {
     console.warn('ancleto: no se encontro engram (memoria) en PATH; se omitio su MCP')
   }
 
-  const cavemanBin = resolveBin('caveman-mcp', [
-    join(homedir(), '.caveman', 'bin', 'caveman-mcp.exe')
-  ])
+  const cavemanFallbacks = [
+    join(homedir(), '.caveman', 'bin', binName('caveman-mcp'))
+  ]
+  const cavemanBin = resolveBin('caveman-mcp', cavemanFallbacks)
   if (cavemanBin) {
     mcp.caveman = { type: 'local', enabled: true, command: [cavemanBin] }
   } else {
@@ -280,13 +290,13 @@ const AGENT_SKILLS_DIR = {
   roo: '.roo/skills'
 }
 
-const OPENSPEC_SKILLS = ['openspec-new', 'openspec-propose', 'openspec-apply', 'openspec-verify', 'openspec-archive', 'openspec-bulk-archive', 'openspec-continue', 'openspec-explore', 'openspec-ff', 'openspec-onboard', 'openspec-workflow']
+const ANCLETO_SKILLS = ['ancleto-new', 'ancleto-propose', 'ancleto-apply', 'ancleto-verify', 'ancleto-archive', 'ancleto-bulk-archive', 'ancleto-continue', 'ancleto-explore', 'ancleto-ff', 'ancleto-onboard', 'ancleto-workflow']
 
 async function installAgentSkills(projectDir, agent) {
   const dir = AGENT_SKILLS_DIR[agent] || AGENT_SKILLS_DIR.opencode
   const dest = join(projectDir, dir)
   await mkdir(dest, { recursive: true })
-  for (const name of OPENSPEC_SKILLS) {
+  for (const name of ANCLETO_SKILLS) {
     const src = join(ROOT, 'skills', name)
     if (!(await exists(src))) {
       console.warn(`ancleto: skill no encontrada en el paquete: ${name}`)
@@ -450,7 +460,7 @@ async function upgradeCmd(args) {
   })
   console.log(`ancleto: upgrade completo (v${manifest.version}, agente: ${agent})`)
   console.log('  ✔ templates re-aplicados (bloques LOCKED actualizados, EXTENSIBLE intacto)')
-  console.log(`  ✔ skills actualizadas en ${agentSkillsDir} (${OPENSPEC_SKILLS.length} skills)`)
+  console.log(`  ✔ skills actualizadas en ${agentSkillsDir} (${ANCLETO_SKILLS.length} skills)`)
   console.log('  ✔ manifiesto .ancletorc actualizado')
 }