@ancleto/spec 0.6.2 → 0.6.5

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.
@@ -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)
@@ -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.
@@ -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/{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.
@@ -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/{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.
@@ -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)
@@ -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.
@@ -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/{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.
@@ -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
 
@@ -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.
@@ -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
 
@@ -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.
@@ -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
 
@@ -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:
@@ -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.
 
@@ -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.
 
@@ -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
 
@@ -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,8 +1,8 @@
 ---
-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.
+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,24 +423,24 @@ 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)
 - design.md ✅
 
-Para implementar: /opsx-apply {CHANGE_NAME}
+Para implementar: /cleto-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
+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