@ancleto/spec 0.6.4 → 0.6.5

package/commands/cleto-verify.md

@@ -10,7 +10,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 
 1. **If no change name provided, prompt for selection**
 
-   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+   Run `aspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
 
    Show changes that have implementation tasks (tasks artifact exists).
    Include the schema used for each change if available.
@@ -21,7 +21,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 2. **Check status to understand the schema**
 
    ```bash
-   openspec status --change "<name>" --json
+   aspec status --change "<name>" --json
    ```
 
    Parse the JSON to understand:
@@ -32,7 +32,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 3. **Get the change directory and load artifacts**
 
    ```bash
-   openspec instructions apply --change "<name>" --json
+   aspec instructions apply --change "<name>" --json
    ```
 
    This returns the change directory and `contextFiles` (artifact ID -> array of concrete file paths). Read all available artifacts from `contextFiles`.
@@ -60,7 +60,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 
    **Spec Coverage**:
 
-   - If delta specs exist in `openspec/changes/<name>/specs/`:
+   - If delta specs exist in `aspec/changes/<name>/specs/`:
      - Extract all requirements (marked with "### Requirement:")
      - For each requirement:
        - Search codebase for keywords related to the requirement

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ancleto/spec",
-  "version": "0.6.4",
+  "version": "0.6.5",
   "description": "Orquestador SDD liviano con subagentes optimizados para costo/tokens",
   "type": "module",
   "bin": {
@@ -31,7 +31,7 @@
   "license": "MIT",
   "keywords": [
     "opencode",
-    "openspec",
+    "aspec",
     "sdd",
     "ai",
     "agents",

package/skills/ancleto-apply/SKILL.md

@@ -8,24 +8,24 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Apply
+# aspec Apply
 
 Implement the tasks of a change, working directly from its artifact files. No external binaries are invoked: task state lives in `tasks.md` checkboxes.
 
-**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `openspec/changes/` and ask the user to select.
+**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `aspec/changes/` and ask the user to select.
 
 ## Steps
 
 ### 1. Select the change
 
 - If a name is provided, use it. Announce: "Using change: `<name>`" and how to override.
-- If omitted: infer from conversation context; auto-select if only one active change directory exists under `openspec/changes/`; otherwise list the directories and ask the user to choose.
+- If omitted: infer from conversation context; auto-select if only one active change directory exists under `aspec/changes/`; otherwise list the directories and ask the user to choose.
 
 **IMPORTANT**: Do NOT guess or auto-select when ambiguous. Always let the user choose.
 
 ### 2. Understand the change state
 
-Read the change directory `openspec/changes/<name>/` and load:
+Read the change directory `aspec/changes/<name>/` and load:
 
 - `proposal.md` — what & why (if present)
 - `design.md` — approach and decisions (if present)

package/skills/ancleto-archive/SKILL.md

@@ -8,11 +8,11 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Archive
+# aspec Archive
 
 Archive a completed change by moving its directory, after checking completion and syncing delta specs. No external binaries are invoked: completion is read from files, archiving is a directory move.
 
-**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `openspec/changes/` (excluding `archive/`) and ask the user to select.
+**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `aspec/changes/` (excluding `archive/`) and ask the user to select.
 
 **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
 
@@ -20,21 +20,21 @@ Archive a completed change by moving its directory, after checking completion an
 
 ### 1. Check task completion status
 
-Read `openspec/changes/<name>/tasks.md` (when it exists) and count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+Read `aspec/changes/<name>/tasks.md` (when it exists) and count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
 
 - **If incomplete tasks found**: display a warning showing the count, prompt the user for confirmation to continue, and proceed only if confirmed.
 - **If no tasks file exists**: proceed without a task-related warning.
 
 ### 2. Assess delta spec sync state
 
-Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without a sync prompt.
+Check for delta specs at `aspec/changes/<name>/specs/`. If none exist, proceed without a sync prompt.
 
 **If delta specs exist:**
 
-- Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`.
+- Compare each delta spec with its corresponding main spec at `aspec/specs/<capability>/spec.md`.
 - Determine what would change (adds, modifications, removals, renames) and show a combined summary.
 - Prompt the user: "Sync now (recommended)" vs "Archive without syncing" (or "Archive now" / "Sync anyway" / "Cancel" when already synced).
-- If the user chooses sync, apply the delta to the main spec directly, editing `openspec/specs/<capability>/spec.md`:
+- If the user chooses sync, apply the delta to the main spec directly, editing `aspec/specs/<capability>/spec.md`:
   - `## ADDED Requirements` → add the new requirement blocks (skip those already present).
   - `## MODIFIED Requirements` → update the matching requirement, preserving scenarios not mentioned in the delta.
   - `## REMOVED Requirements` → remove the entire requirement block.
@@ -43,12 +43,12 @@ Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, procee
 
 ### 3. Perform the archive
 
-Create the archive directory if it does not exist: `openspec/changes/archive/`.
+Create the archive directory if it does not exist: `aspec/changes/archive/`.
 
 Generate the target name using the current date: `YYYY-MM-DD-<change-name>`.
 
 - **If the target already exists**: fail with an error suggesting to rename the existing archive or pick a different date.
-- **If not**: delete scaffold-only files (e.g., `openspec/changes/<name>/context.md` — they must not be preserved), then move the whole change directory to `openspec/changes/archive/YYYY-MM-DD-<name>/`.
+- **If not**: delete scaffold-only files (e.g., `aspec/changes/<name>/context.md` — they must not be preserved), then move the whole change directory to `aspec/changes/archive/YYYY-MM-DD-<name>/`.
 
 ### 4. Capture lessons into persistent memory
 
@@ -71,7 +71,7 @@ Record only durable lessons — decisions whose reasons are not visible in the r
 ## Archive Complete
 
 **Change:** <change-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** aspec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** ✓ Synced to main specs (or: No delta specs / Sync skipped)
 
 **Memories recorded:** <list, or "None">

package/skills/ancleto-bulk-archive/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Bulk Archive
+# aspec Bulk Archive
 
 Archive multiple completed changes in a single operation, handling spec conflicts by checking what is actually implemented. No external binaries are invoked: changes are listed from directories, status is read from files, archiving is a directory move.
 
@@ -18,7 +18,7 @@ Archive multiple completed changes in a single operation, handling spec conflict
 
 ### 1. Get active changes
 
-List the directories directly under `openspec/changes/` (excluding `archive/`). If none exist, inform the user and stop.
+List the directories directly under `aspec/changes/` (excluding `archive/`). If none exist, inform the user and stop.
 
 ### 2. Prompt for change selection
 
@@ -34,11 +34,11 @@ Use the **AskUserQuestion tool** with multi-select to let the user choose:
 
 For each selected change, collect by reading files:
 
-a. **Artifact presence** — which of `proposal.md`, `design.md`, `tasks.md`, `specs/` exist under `openspec/changes/<name>/`.
+a. **Artifact presence** — which of `proposal.md`, `design.md`, `tasks.md`, `specs/` exist under `aspec/changes/<name>/`.
 
-b. **Task completion** — read `openspec/changes/<name>/tasks.md` and count `- [ ]` (incomplete) vs `- [x]` (complete). If no tasks file exists, note "No tasks".
+b. **Task completion** — read `aspec/changes/<name>/tasks.md` and count `- [ ]` (incomplete) vs `- [x]` (complete). If no tasks file exists, note "No tasks".
 
-c. **Delta specs** — check `openspec/changes/<name>/specs/` and list which capability specs exist, extracting requirement names (lines matching `### Requirement: <name>`).
+c. **Delta specs** — check `aspec/changes/<name>/specs/` and list which capability specs exist, extracting requirement names (lines matching `### Requirement: <name>`).
 
 ### 4. Detect spec conflicts
 
@@ -89,9 +89,9 @@ If there are incomplete changes, make clear they will be archived with warnings.
 
 Process changes in the determined order (respecting conflict resolution):
 
-a. **Sync specs** if delta specs exist and the resolution says so: apply the delta directly to `openspec/specs/<capability>/spec.md` (ADDED adds, MODIFIED updates preserving unmentioned scenarios, REMOVED deletes, RENAMED renames via `FROM:`/`TO:`). Track whether sync was done.
+a. **Sync specs** if delta specs exist and the resolution says so: apply the delta directly to `aspec/specs/<capability>/spec.md` (ADDED adds, MODIFIED updates preserving unmentioned scenarios, REMOVED deletes, RENAMED renames via `FROM:`/`TO:`). Track whether sync was done.
 
-b. **Perform the archive**: create `openspec/changes/archive/` if missing, delete scaffold-only files (`context.md`), then move the directory to `openspec/changes/archive/YYYY-MM-DD-<name>/`. If the target already exists, fail that change (record the error) but continue with the others.
+b. **Perform the archive**: create `aspec/changes/archive/` if missing, delete scaffold-only files (`context.md`), then move the directory to `aspec/changes/archive/YYYY-MM-DD-<name>/`. If the target already exists, fail that change (record the error) but continue with the others.
 
 c. **Track each outcome**: success, failed (with error), or skipped.
 

package/skills/ancleto-continue/SKILL.md

@@ -8,11 +8,11 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Continue
+# aspec Continue
 
 Continue working on a change by creating exactly ONE next artifact. No external binaries are invoked: change state is derived by reading which artifact files exist.
 
-**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `openspec/changes/` (excluding `archive/`) and ask the user to select, marking the most recently modified one as "(Recommended)".
+**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `aspec/changes/` (excluding `archive/`) and ask the user to select, marking the most recently modified one as "(Recommended)".
 
 **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
 
@@ -20,7 +20,7 @@ Continue working on a change by creating exactly ONE next artifact. No external
 
 ### 1. Determine the next missing artifact
 
-Read `openspec/changes/<name>/` and check for artifact files in this fixed dependency order:
+Read `aspec/changes/<name>/` and check for artifact files in this fixed dependency order:
 
 1. `proposal.md` — what & why
 2. `specs/` — delta requirements (at least one `spec.md` inside; skip only if the change specifies no behavior)

package/skills/ancleto-explore/SKILL.md

@@ -8,11 +8,11 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Explore
+# aspec Explore
 
 Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
 
-**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY draft OpenSpec artifacts (proposals, designs, specs) if the user asks — that's capturing thinking, not implementing.
+**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY draft aspec artifacts (proposals, designs, specs) if the user asks — that's capturing thinking, not implementing.
 
 **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.
 
@@ -76,7 +76,7 @@ Depending on what the user brings, you might:
 - Find gaps in understanding
 - Suggest spikes or investigations
 
-## OpenSpec Awareness
+## aspec Awareness
 
 You have full context of the spec-driven system. Use it naturally, don't force it.
 
@@ -84,7 +84,7 @@ You have full context of the spec-driven system. Use it naturally, don't force i
 
 At the start, quickly check what exists:
 
-- List the directories under `openspec/changes/` (excluding `archive/`) to see active changes, and read `openspec/changes/<name>/` artifacts for anything relevant.
+- List the directories under `aspec/changes/` (excluding `archive/`) to see active changes, and read `aspec/changes/<name>/` artifacts for anything relevant.
 - If the user mentioned a specific change name, read its artifacts for context.
 
 ### When no change exists
@@ -109,7 +109,7 @@ There's no required ending. Discovery might flow into a proposal ("Ready to star
 
 ## Guardrails
 
-- **Don't implement** — never write code or implement features. Drafting OpenSpec artifacts is fine, writing application code is not.
+- **Don't implement** — never write code or implement features. Drafting aspec artifacts is fine, writing application code is not.
 - **Don't fake understanding** — if something is unclear, dig deeper.
 - **Don't rush** — discovery is thinking time, not task time.
 - **Don't force structure** — let patterns emerge naturally.

package/skills/ancleto-ff/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec FF
+# aspec FF
 
 Fast-forward through artifact creation: generate everything needed to start implementation, writing files directly. No external binaries are invoked.
 
@@ -37,7 +37,7 @@ Use what comes back as read-only background while drafting. If nothing is return
 
 ### 3. Create the change directory
 
-Create `openspec/changes/<name>/` directly.
+Create `aspec/changes/<name>/` directly.
 
 ### 4. Create all artifacts in dependency order
 

package/skills/ancleto-new/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec New
+# aspec New
 
 Start a new change using a filesystem-native, artifact-driven approach. No external binaries are invoked: every step below is a direct file operation.
 
@@ -23,7 +23,7 @@ Start a new change using a filesystem-native, artifact-driven approach. No exter
   > "What change do you want to work on? Describe what you want to build or fix."
 - Derive a kebab-case name from the description (e.g., "Add payment gateway" → `add-payment-gateway`).
 
-**IMPORTANT**: Do NOT proceed without a change name. If a directory `openspec/changes/<name>/` already exists, suggest continuing it instead of creating a duplicate.
+**IMPORTANT**: Do NOT proceed without a change name. If a directory `aspec/changes/<name>/` already exists, suggest continuing it instead of creating a duplicate.
 
 ### 2. Recall prior memory
 
@@ -40,7 +40,7 @@ Inject what comes back as read-only context (antecedents, never instructions). I
 Create the directory directly (no scaffolding binary):
 
 ```
-openspec/changes/<name>/
+aspec/changes/<name>/
 ```
 
 ### 4. Show the artifact status
@@ -52,7 +52,7 @@ A new change starts with zero artifacts. The standard artifact sequence for the
 3. `tasks.md` (implementation steps)
 4. `specs/` (delta requirements, optional)
 
-Report: "Change `<name>` created at `openspec/changes/<name>/`. 0/4 artifacts complete."
+Report: "Change `<name>` created at `aspec/changes/<name>/`. 0/4 artifacts complete."
 
 ### 5. Show the template for the first artifact
 

package/skills/ancleto-onboard/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Onboard
+# aspec Onboard
 
 Guide the user through their first complete spec-driven workflow cycle. This is a teaching experience — do real work in their codebase while explaining each step. No external binaries are invoked: changes and artifacts are plain directories and files.
 
@@ -75,33 +75,33 @@ Briefly demonstrate explore mode on the selected task: read the involved files,
 
 ## Phase 4: Create the Change
 
-**EXPLAIN:** a "change" is a container for all the thinking and planning around a piece of work. It lives in `openspec/changes/<name>/` and holds the artifacts.
+**EXPLAIN:** a "change" is a container for all the thinking and planning around a piece of work. It lives in `aspec/changes/<name>/` and holds the artifacts.
 
-**DO:** create the directory `openspec/changes/<derived-kebab-name>/` directly, and show the folder layout (`proposal.md`, `design.md`, `specs/`, `tasks.md` — to be filled next).
+**DO:** create the directory `aspec/changes/<derived-kebab-name>/` directly, and show the folder layout (`proposal.md`, `design.md`, `specs/`, `tasks.md` — to be filled next).
 
 ## Phase 5: Proposal
 
 **EXPLAIN:** the proposal captures **why** and **what** at a high level.
 
-**DO:** draft it from the task (Why / What Changes / Capabilities / Impact), show it, and **PAUSE** for approval. After approval, write it to `openspec/changes/<name>/proposal.md`.
+**DO:** draft it from the task (Why / What Changes / Capabilities / Impact), show it, and **PAUSE** for approval. After approval, write it to `aspec/changes/<name>/proposal.md`.
 
 ## Phase 6: Specs
 
 **EXPLAIN:** specs define **what** precisely, in testable WHEN/THEN form.
 
-**DO:** create `openspec/changes/<name>/specs/<capability>/spec.md` with `## ADDED Requirements` / `#### Scenario:` blocks. Save the file.
+**DO:** create `aspec/changes/<name>/specs/<capability>/spec.md` with `## ADDED Requirements` / `#### Scenario:` blocks. Save the file.
 
 ## Phase 7: Design
 
 **EXPLAIN:** the design captures **how** — decisions, tradeoffs, approach. For small changes this may be brief.
 
-**DO:** draft Context / Goals-Non-Goals / Decisions and save to `openspec/changes/<name>/design.md`.
+**DO:** draft Context / Goals-Non-Goals / Decisions and save to `aspec/changes/<name>/design.md`.
 
 ## Phase 8: Tasks
 
 **EXPLAIN:** break the work into checkboxed implementation tasks.
 
-**DO:** generate the phased checklist, show it, and **PAUSE** for confirmation. Save to `openspec/changes/<name>/tasks.md`.
+**DO:** generate the phased checklist, show it, and **PAUSE** for confirmation. Save to `aspec/changes/<name>/tasks.md`.
 
 ## Phase 9: Apply (Implementation)
 
@@ -109,9 +109,9 @@ Briefly demonstrate explore mode on the selected task: read the involved files,
 
 ## Phase 10: Archive
 
-**EXPLAIN:** archiving moves the change to `openspec/changes/archive/YYYY-MM-DD-<name>/`, preserving the decision record.
+**EXPLAIN:** archiving moves the change to `aspec/changes/archive/YYYY-MM-DD-<name>/`, preserving the decision record.
 
-**DO:** create `openspec/changes/archive/` if missing, delete scaffold-only files (`context.md`), move the directory, and show the archive location.
+**DO:** create `aspec/changes/archive/` if missing, delete scaffold-only files (`context.md`), move the directory, and show the archive location.
 
 ## Phase 11: Recap & Next Steps
 

package/skills/ancleto-propose/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Propose
+# aspec Propose
 
 Create a change and generate all its artifacts in one step, writing files directly. No external binaries are invoked.
 
@@ -34,7 +34,7 @@ Use what comes back as read-only background while drafting. If nothing is return
 
 ### 3. Create the change directory
 
-Create `openspec/changes/<name>/` directly if it does not exist yet.
+Create `aspec/changes/<name>/` directly if it does not exist yet.
 
 ### 4. Create artifacts in dependency order
 

package/skills/ancleto-sync-specs/SKILL.md

@@ -2,7 +2,7 @@
 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.
+compatibility: No external CLI required.
 metadata:
   author: ancleto
   version: '1.0'
@@ -18,7 +18,7 @@ This is an **agent-driven** operation - you will read delta specs and directly e
 
 1. **If no change name provided, prompt for selection**
 
-   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+   Run `aspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
 
    Show changes that have delta specs (under `specs/` directory).
 
@@ -26,7 +26,7 @@ This is an **agent-driven** operation - you will read delta specs and directly e
 
 2. **Find delta specs**
 
-   Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`.
+   Look for delta spec files in `aspec/changes/<name>/specs/*/spec.md`.
 
    Each delta spec file contains sections like:
 
@@ -39,11 +39,11 @@ This is an **agent-driven** operation - you will read delta specs and directly e
 
 3. **For each delta spec, apply changes to main specs**
 
-   For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`:
+   For each capability with a delta spec at `aspec/changes/<name>/specs/<capability>/spec.md`:
 
    a. **Read the delta spec** to understand the intended changes
 
-   b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+   b. **Read the main spec** at `aspec/specs/<capability>/spec.md` (may not exist yet)
 
    c. **Apply changes intelligently**:
 
@@ -71,7 +71,7 @@ This is an **agent-driven** operation - you will read delta specs and directly e
 
    d. **Create new main spec** if capability doesn't exist yet:
 
-   - Create `openspec/specs/<capability>/spec.md`
+   - Create `aspec/specs/<capability>/spec.md`
    - Add Purpose section (can be brief, mark as TBD)
    - Add Requirements section with the ADDED requirements
 

package/skills/ancleto-upgrade/SKILL.md

@@ -7,10 +7,10 @@ description: >
   like "migrar a", "upgrade a", "actualizar a", "mover a v", or any mention of
   bumping a major version. Analyzes the full repository (TypeScript source, tests,
   config, CI, Docker, CDK), fetches official migration docs, builds search patterns
-  dynamically from those docs, and generates a complete OpenSpec change with phased
+  dynamically from those docs, and generates a complete aspec change with phased
   tasks — without touching any code.
 license: MIT
-compatibility: Requires openspec CLI, Node.js
+compatibility: Requires Node.js (no external CLI)
 metadata:
   author: ancleto
   version: '4.0'
@@ -19,7 +19,7 @@ metadata:
 
 # ancleto-upgrade
 
-Analiza el repositorio completo y genera un OpenSpec change para migrar cualquier
+Analiza el repositorio completo y genera un aspec change para migrar cualquier
 librería o runtime a una nueva versión mayor — de forma documentada, faseada y sin
 romper el repo.
 
@@ -360,17 +360,15 @@ Con todos los matches del Paso 4, construir:
 
 ---
 
-## Paso 6 — Crear el change OpenSpec
+## Paso 6 — Crear el change aspec
 
-```bash
-openspec new change "${CHANGE_NAME}"
-```
+Crear el directorio del change en `aspec/changes/${CHANGE_NAME}/` (con `specs/` si aplica).
 
 Si el nombre ya existe, preguntar al usuario: agregar sufijo `-v2` o eliminar el existente.
 
 ---
 
-## Paso 7 — Escribir los artefactos OpenSpec
+## Paso 7 — Escribir los artefactos aspec
 
 Leer `references/templates.md` para obtener los templates exactos de cada archivo.
 Escribir en este orden:
@@ -425,7 +423,7 @@ Reglas al completar los templates:
 ### Scripts de verificación
 build: sí/no | lint: sí/no | test: sí/no | test:ci: sí/no | typecheck: sí/no
 
-### Artefactos OpenSpec generados
+### Artefactos aspec generados
 - proposal.md ✅
 - specs/{LIBRARY_SLUG}{TARGET_VERSION}.md ✅
 - tasks.md ✅ ({N} tareas en 6 fases)
@@ -438,11 +436,11 @@ Para implementar: /cleto-apply {CHANGE_NAME}
 
 ## Guardrails
 
-Este skill solo genera artefactos OpenSpec — no modifica ningún archivo del repo.
+Este skill solo genera artefactos aspec — no modifica ningún archivo del repo.
 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}/`
+- No tocar archivos fuera de `aspec/changes/{CHANGE_NAME}/`
 - Los `VERSION_PATTERNS[]` siempre se aplican, con o sin documentación oficial
 - Si no hay doc disponible, documentarlo en proposal y continuar con el escaneo
 - Si el change ya existe, avisar antes de cualquier acción

package/skills/ancleto-upgrade/references/templates.md

@@ -1,4 +1,4 @@
-# Templates — Artefactos OpenSpec
+# Templates — Artefactos aspec
 
 Este archivo contiene los templates exactos para los cuatro artefactos que genera
 el skill. Leer este archivo en el Paso 6 y completar cada placeholder `{...}`.

package/skills/ancleto-verify/SKILL.md

@@ -8,11 +8,11 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Verify
+# aspec Verify
 
 Verify that an implementation matches its change artifacts (proposal, design, tasks, delta specs) by reading the files directly. No external binaries are invoked.
 
-**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `openspec/changes/` that contain a `tasks.md` file and ask the user to select. Mark changes with incomplete tasks as "(In Progress)".
+**Input**: Optionally specify a change name (e.g., `add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous, list the directories under `aspec/changes/` that contain a `tasks.md` file and ask the user to select. Mark changes with incomplete tasks as "(In Progress)".
 
 **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
 
@@ -20,7 +20,7 @@ Verify that an implementation matches its change artifacts (proposal, design, ta
 
 ### 1. Load the change artifacts
 
-Read everything under `openspec/changes/<name>/`:
+Read everything under `aspec/changes/<name>/`:
 
 - `tasks.md` — the checklist (required)
 - `proposal.md`, `design.md` — intent and decisions (if present)
@@ -36,7 +36,7 @@ Read everything under `openspec/changes/<name>/`:
 
 **Spec Coverage:**
 
-- If delta specs exist in `openspec/changes/<name>/specs/`:
+- If delta specs exist in `aspec/changes/<name>/specs/`:
   - Extract all requirements (marked with `### Requirement:`).
   - For each requirement, search the codebase for keywords related to it and assess whether implementation likely exists.
   - If a requirement appears unimplemented, add a CRITICAL issue: "Requirement not found: `<requirement name>`" with the recommendation "Implement requirement: `<description>`".

package/skills/ancleto-workflow/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   version: '1.0'
 ---
 
-# OpenSpec Workflow
+# aspec Workflow
 
 This skill is the map of the spec-driven lifecycle. It does not execute work itself — it routes: given where the user (or the current change) stands, it names the skill that runs next and hands over the required context.
 
@@ -39,7 +39,7 @@ explore → new/propose/ff → continue* → apply → verify → 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>/`):
+**By change state** (read `aspec/changes/<name>/`):
 
 | State | Run |
 |---|---|

package/src/cli/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { existsSync } from 'node:fs'
-import { cp, mkdir, access, writeFile, readFile, readdir } from 'node:fs/promises'
+import { cp, mkdir, access, writeFile, readFile, readdir, rename } from 'node:fs/promises'
 import { spawnSync } from 'node:child_process'
 import { createHash } from 'node:crypto'
 import { createInterface } from 'node:readline'
@@ -310,17 +310,19 @@ async function installAgentSkills(projectDir, agent) {
   return dir.replace(/\\/g, '/')
 }
 
-const DEFAULT_OPENSPEC_CONFIG = `# OpenSpec project configuration
+const CHANGES_ROOT = 'aspec'
+
+const DEFAULT_ASPEC_CONFIG = `# OpenSpec project configuration
 # Generado por @ancleto/spec (G5) — editalo libremente, no se sobrescribe en reinstalaciones.
 schema: spec-driven-development
 `
 
-async function scaffoldOpenSpec(projectDir) {
-  const changesDir = join(projectDir, 'openspec', 'changes')
+async function scaffoldAspec(projectDir) {
+  const changesDir = join(projectDir, CHANGES_ROOT, 'changes')
   await mkdir(changesDir, { recursive: true })
-  const configPath = join(projectDir, 'openspec', 'config.yaml')
+  const configPath = join(projectDir, CHANGES_ROOT, 'config.yaml')
   if (!(await exists(configPath))) {
-    await writeFile(configPath, DEFAULT_OPENSPEC_CONFIG)
+    await writeFile(configPath, DEFAULT_ASPEC_CONFIG)
   }
 }
 
@@ -392,7 +394,7 @@ async function install(args) {
 
   if (project) {
     await copyTemplates(resolve(project))
-    await scaffoldOpenSpec(resolve(project))
+    await scaffoldAspec(resolve(project))
     const existingRc = await readAncletorc(resolve(project))
     const agent = await resolveAgent(args, existingRc?.agent)
     const agentSkillsDir = await installAgentSkills(resolve(project), agent)
@@ -446,6 +448,14 @@ async function upgradeCmd(args) {
     console.error("Error: No se encontro .ancletorc. Ejecuta 'ancleto init' primero.")
     process.exit(1)
   }
+  const legacyChanges = join(projectDir, 'openspec')
+  const changesRoot = join(projectDir, CHANGES_ROOT)
+  if ((await exists(legacyChanges)) && !(await exists(changesRoot))) {
+    await rename(legacyChanges, changesRoot)
+    console.log('ancleto: changes migrados de openspec/ a aspec/')
+  } else if ((await exists(legacyChanges)) && (await exists(changesRoot))) {
+    console.warn('ancleto: existen openspec/ y aspec/ — no se migro nada (revisar manualmente)')
+  }
   const agent = await resolveAgent(args, rc.agent)
   await copyTemplates(projectDir)
   const agentSkillsDir = await installAgentSkills(projectDir, agent)
@@ -501,7 +511,7 @@ async function initProject(args) {
   }
 
   const manifest = await writeManifest(projectDir, { azure, discovery, agent })
-  await scaffoldOpenSpec(projectDir)
+  await scaffoldAspec(projectDir)
   if (azure.enabled) console.log(AZURE_MCP_NOTICE)
   console.log(`ancleto: .ancletorc actualizado en ${projectDir} (v${manifest.version})${azure.enabled ? ' (Azure habilitado)' : ' (Azure desactivado)'} (Agente: ${agent})${tier ? ` (Tier: ${tier})` : ''}`)
 }