@ancleto/spec 0.6.4 → 0.6.5

package/commands/cleto-archive.md

@@ -10,7 +10,7 @@ Archive a completed change in the experimental workflow.
 
 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 only active changes (not already archived).
    Include the schema used for each change if available.
@@ -19,7 +19,7 @@ Archive a completed change in the experimental workflow.
 
 2. **Check artifact completion status**
 
-   Run `openspec status --change "<name>" --json` to check artifact completion.
+   Run `aspec status --change "<name>" --json` to check artifact completion.
 
    Parse the JSON to understand:
 
@@ -48,11 +48,11 @@ Archive a completed change in the experimental workflow.
 
 4. **Assess delta spec sync state**
 
-   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+   Check for delta specs at `aspec/changes/<name>/specs/`. If none exist, proceed without 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 changes would be applied (adds, modifications, removals, renames)
    - Show a combined summary before prompting
 
@@ -68,7 +68,7 @@ Archive a completed change in the experimental workflow.
    Create the archive directory if it doesn't exist:
 
    ```bash
-   mkdir -p openspec/changes/archive
+   mkdir -p aspec/changes/archive
    ```
 
    Generate target name using current date: `YYYY-MM-DD-<change-name>`
@@ -81,13 +81,13 @@ Archive a completed change in the experimental workflow.
    **Before moving**, delete scaffold-only files if present — they must not be preserved in the archive:
 
    ```bash
-   rm -f openspec/changes/<name>/context.md
+   rm -f aspec/changes/<name>/context.md
    ```
 
    Then move:
 
    ```bash
-   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   mv aspec/changes/<name> aspec/changes/archive/YYYY-MM-DD-<name>
    ```
 
 6. **Display summary**
@@ -107,7 +107,7 @@ Archive a completed change in the experimental workflow.
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** aspec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** ✓ Synced to main specs
 
 All artifacts complete. All tasks complete.
@@ -120,7 +120,7 @@ All artifacts complete. All tasks complete.
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** aspec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** No delta specs
 
 All artifacts complete. All tasks complete.
@@ -133,7 +133,7 @@ All artifacts complete. All tasks complete.
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** aspec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** Sync skipped (user chose to skip)
 
 **Warnings:**
@@ -150,7 +150,7 @@ Review the archive if this was not intentional.
 ## Archive Failed
 
 **Change:** <change-name>
-**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Target:** aspec/changes/archive/YYYY-MM-DD-<name>/
 
 Target archive directory already exists.
 
@@ -163,9 +163,9 @@ Target archive directory already exists.
 **Guardrails**
 
 - Always prompt for change selection if not provided
-- Use artifact graph (openspec status --json) for completion checking
+- Use artifact graph (aspec status --json) for completion checking
 - Don't block archive on warnings - just inform and confirm
-- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Preserve .aspec.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 `ancleto-sync-specs` (agent-driven)
 - If delta specs exist, always run the sync assessment and show the combined summary before prompting

package/commands/cleto-bulk-archive.md

@@ -12,7 +12,7 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
 
 1. **Get active changes**
 
-   Run `openspec list --json` to get all active changes.
+   Run `aspec list --json` to get all active changes.
 
    If no active changes exist, inform user and stop.
 
@@ -30,17 +30,17 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
 
    For each selected change, collect:
 
-   a. **Artifact status** - Run `openspec status --change "<name>" --json`
+   a. **Artifact status** - Run `aspec status --change "<name>" --json`
 
    - Parse `schemaName` and `artifacts` list
    - Note which artifacts are `done` vs other states
 
-   b. **Task completion** - Read `openspec/changes/<name>/tasks.md`
+   b. **Task completion** - Read `aspec/changes/<name>/tasks.md`
 
    - Count `- [ ]` (incomplete) vs `- [x]` (complete)
    - If no tasks file exists, note as "No tasks"
 
-   c. **Delta specs** - Check `openspec/changes/<name>/specs/` directory
+   c. **Delta specs** - Check `aspec/changes/<name>/specs/` directory
 
    - List which capability specs exist
    - For each, extract requirement names (lines matching `### Requirement: <name>`)
@@ -131,8 +131,8 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
    b. **Perform the archive**:
 
    ```bash
-   mkdir -p openspec/changes/archive
-   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   mkdir -p aspec/changes/archive
+   mv aspec/changes/<name> aspec/changes/archive/YYYY-MM-DD-<name>
    ```
 
    c. **Track outcome** for each change:
@@ -250,6 +250,6 @@ No active changes found. Create a new change to get started.
 - Show clear per-change status before confirming
 - Use single confirmation for entire batch
 - Track and report all outcomes (success/skip/fail)
-- Preserve .openspec.yaml when moving to archive
+- Preserve .aspec.yaml when moving to archive
 - Archive directory target uses current date: YYYY-MM-DD-<name>
 - If archive target exists, fail that change but continue with others

package/commands/cleto-continue.md

@@ -10,7 +10,7 @@ Continue working on a change by creating the next artifact.
 
 1. **If no change name provided, prompt for selection**
 
-   Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+   Run `aspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
 
    Present the top 3-4 most recently modified changes as options, showing:
 
@@ -26,7 +26,7 @@ Continue working on a change by creating the next artifact.
 2. **Check current status**
 
    ```bash
-   openspec status --change "<name>" --json
+   aspec status --change "<name>" --json
    ```
 
    Parse the JSON to understand current state. The response includes:
@@ -41,7 +41,7 @@ Continue working on a change by creating the next artifact.
 
    Otherwise, read it as background context — it is NOT an artifact and must NOT be included in output files, but its contents inform what you write:
 
-   - `openspec/changes/<name>/context.md` — Work Item context (title, description, acceptance criteria)
+   - `aspec/changes/<name>/context.md` — Work Item context (title, description, acceptance criteria)
 
    If either file is missing, skip silently.
 
@@ -63,7 +63,7 @@ Continue working on a change by creating the next artifact.
    - Pick the FIRST artifact with `status: "ready"` from the status output
    - Get its instructions:
      ```bash
-     openspec instructions <artifact-id> --change "<name>" --json
+     aspec instructions <artifact-id> --change "<name>" --json
      ```
    - Parse the JSON. The key fields are:
      - `context`: Project background (constraints for you - do NOT include in output)
@@ -91,7 +91,7 @@ Continue working on a change by creating the next artifact.
 
 5. **After creating an artifact, show progress**
    ```bash
-   openspec status --change "<name>"
+   aspec status --change "<name>"
    ```
 
 **Output**

package/commands/cleto-explore.md

@@ -4,7 +4,7 @@ description: Enter explore mode - think through ideas, investigate problems, cla
 
 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 create 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 create 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.
 
@@ -81,16 +81,16 @@ Depending on what the user brings, you might:
 
 ---
 
-## OpenSpec Awareness
+## aspec Awareness
 
-You have full context of the OpenSpec system. Use it naturally, don't force it.
+You have full context of the aspec system. Use it naturally, don't force it.
 
 ### Check for context
 
 At the start, quickly check what exists:
 
 ```bash
-openspec list --json
+aspec list --json
 ```
 
 This tells you:
@@ -114,9 +114,9 @@ If the user mentions a change or you detect one is relevant:
 
 1. **Read existing artifacts for context**
 
-   - `openspec/changes/<name>/proposal.md`
-   - `openspec/changes/<name>/design.md`
-   - `openspec/changes/<name>/tasks.md`
+   - `aspec/changes/<name>/proposal.md`
+   - `aspec/changes/<name>/design.md`
+   - `aspec/changes/<name>/tasks.md`
    - etc.
 
 2. **Reference them naturally in conversation**
@@ -171,7 +171,7 @@ When things crystallize, you might offer a summary - but it's optional. Sometime
 
 ## Guardrails
 
-- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't implement** - Never write code or implement features. Creating 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/commands/cleto-ff.md

@@ -13,7 +13,7 @@ Fast-forward through artifact creation - generate everything needed to start imp
    Resolve Work Item context in this order — stop at the first source that yields data:
 
    a. **In-session context** — If WI data was already fetched in this session, use it. Proceed to name derivation below.
-   b. **`context.md`** — If a change name was provided as argument and `openspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
+   b. **`context.md`** — If a change name was provided as argument and `aspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
    c. **Ask the user** — Use the **AskUserQuestion tool** to ask for the Work Item reference. Two accepted formats:
 
    - **ID + Project** — e.g., ID `12345` and project `MyProject`
@@ -42,16 +42,14 @@ Fast-forward through artifact creation - generate everything needed to start imp
 
 2. **Create the change directory**
 
-   ```bash
-   openspec new change "<name>"
-   ```
+   Create the directory `aspec/changes/<name>/` in the repository.
 
-   This creates a scaffolded change at `openspec/changes/<name>/`.
+   This scaffolds the change at `aspec/changes/<name>/`.
 
 3. **Get the artifact build order**
 
    ```bash
-   openspec status --change "<name>" --json
+   aspec status --change "<name>" --json
    ```
 
    Parse the JSON to get:
@@ -69,7 +67,7 @@ Fast-forward through artifact creation - generate everything needed to start imp
 
    - Get instructions:
      ```bash
-     openspec instructions <artifact-id> --change "<name>" --json
+     aspec instructions <artifact-id> --change "<name>" --json
      ```
    - The instructions JSON includes:
      - `context`: Project background (constraints for you - do NOT include in output)
@@ -87,7 +85,7 @@ Fast-forward through artifact creation - generate everything needed to start imp
 
    b. **Continue until all `applyRequires` artifacts are complete**
 
-   - After creating each artifact, re-run `openspec status --change "<name>" --json`
+   - After creating each artifact, re-run `aspec status --change "<name>" --json`
    - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
    - Stop when all `applyRequires` artifacts are done
 
@@ -98,7 +96,7 @@ Fast-forward through artifact creation - generate everything needed to start imp
 
 5. **Show final status**
    ```bash
-   openspec status --change "<name>"
+   aspec status --change "<name>"
    ```
 
 **Output**
@@ -112,7 +110,7 @@ After completing all artifacts, summarize:
 
 **Artifact Creation Guidelines**
 
-- Follow the `instruction` field from `openspec instructions` for each artifact type
+- Follow the `instruction` field from `aspec instructions` for each artifact type
 - The schema defines what each artifact should contain - follow it
 - Read dependency artifacts for context before creating new ones
 - Use `template` as the structure for your output file - fill in its sections

package/commands/cleto-new.md

@@ -13,7 +13,7 @@ Start a new change using the experimental artifact-driven approach.
    Resolve Work Item context in this order — stop at the first source that yields data:
 
    a. **In-session context** — If WI data was already fetched in this session, use it. Proceed to name derivation below.
-   b. **`context.md`** — If a change name was provided as argument and `openspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
+   b. **`context.md`** — If a change name was provided as argument and `aspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
    c. **Ask the user** — Use the **AskUserQuestion tool** to ask for the Work Item reference. Two accepted formats:
 
    - **ID + Project** — e.g., ID `12345` and project `MyProject`
@@ -45,22 +45,20 @@ Start a new change using the experimental artifact-driven approach.
    **Use a different schema only if the user mentions:**
 
    - A specific schema name → use `--schema <name>`
-   - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose
+   - "show workflows" or "what workflows" → run `aspec schemas --json` and let them choose
 
    **Otherwise**: Omit `--schema` to use the default.
 
 3. **Create the change directory**
 
-   ```bash
-   openspec new change "<name>"
-   ```
+   Create the directory `aspec/changes/<name>/` in the repository.
 
-   Add `--schema <name>` only if the user requested a specific workflow.
-   This creates a scaffolded change at `openspec/changes/<name>/` with the selected schema.
+   Record the schema selection in the change metadata only if the user requested a specific workflow.
+   This scaffolds the change at `aspec/changes/<name>/` with the selected schema.
 
 4. **Persist Work Item context to `context.md`** (only if WI was resolved in step 1)
 
-   Write WI context to `openspec/changes/<name>/context.md`:
+   Write WI context to `aspec/changes/<name>/context.md`:
 
    ```
    # Work Item Context
@@ -82,7 +80,7 @@ Start a new change using the experimental artifact-driven approach.
 5. **Show the artifact status**
 
    ```bash
-   openspec status --change "<name>"
+   aspec status --change "<name>"
    ```
 
    This shows which artifacts need to be created and which are ready (dependencies satisfied).
@@ -91,7 +89,7 @@ Start a new change using the experimental artifact-driven approach.
    The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
 
    ```bash
-   openspec instructions <first-artifact-id> --change "<name>"
+   aspec instructions <first-artifact-id> --change "<name>"
    ```
 
    This outputs the template and context for creating the first artifact.

package/commands/cleto-onboard.md

@@ -1,27 +1,15 @@
 ---
-description: Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
+description: Guided onboarding - walk through a complete aspec workflow cycle with narration
 ---
 
-Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
+Guide the user through their first complete aspec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
 
 ---
 
 ## Preflight
 
-Before starting, check if the OpenSpec CLI is installed:
-
-```bash
-# Unix/macOS
-openspec --version 2>&1 || echo "CLI_NOT_INSTALLED"
-# Windows (PowerShell)
-# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" }
-```
-
-**If CLI not installed:**
-
-> OpenSpec CLI is not installed. Install it first, then come back to `/cleto-onboard`.
-
-Stop here if not installed.
+No external binaries are required: the change cycle runs on the aspec skills bundled
+with your agent (`/cleto-*`). Proceed directly.
 
 ---
 
@@ -30,7 +18,7 @@ Stop here if not installed.
 Display:
 
 ```
-## Welcome to OpenSpec!
+## Welcome to aspec!
 
 I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.
 
@@ -110,7 +98,7 @@ Which task interests you? (Pick a number or describe your own)
 If the user picks or describes something too large (major feature, multi-day work):
 
 ```
-That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
+That's a valuable task, but it's probably larger than ideal for your first aspec run-through.
 
 For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
 
@@ -165,26 +153,26 @@ Now let's create a change to hold our work.
 ```
 ## Creating a Change
 
-A "change" in OpenSpec is a container for all the thinking and planning around a piece of work. It lives in `openspec/changes/<name>/` and holds your artifacts—proposal, specs, design, tasks.
+A "change" in aspec is a container for all the thinking and planning around a piece of work. It lives in `aspec/changes/<name>/` and holds your artifacts—proposal, specs, design, tasks.
 
 Let me create one for our task.
 ```
 
-**DO:** Create the change with a derived kebab-case name:
+**DO:** Create the change directory with a derived kebab-case name:
 
 ```bash
-openspec new change "<derived-name>"
+mkdir -p aspec/changes/<derived-name>
 ```
 
 **SHOW:**
 
 ```
-Created: `openspec/changes/<name>/`
+Created: `aspec/changes/<name>/`
 
 The folder structure:
 ```
 
-openspec/changes/<name>/
+aspec/changes/<name>/
 ├── proposal.md ← Why we're doing this (empty, we'll fill it)
 ├── design.md ← How we'll build it (empty)
 ├── specs/ ← Detailed requirements (empty)
@@ -247,10 +235,10 @@ Does this capture the intent? I can adjust before we save it.
 After approval, save the proposal:
 
 ```bash
-openspec instructions proposal --change "<name>" --json
+aspec instructions proposal --change "<name>" --json
 ```
 
-Then write the content to `openspec/changes/<name>/proposal.md`.
+Then write the content to `aspec/changes/<name>/proposal.md`.
 
 ```
 Proposal saved. This is your "why" document—you can always come back and refine it as understanding evolves.
@@ -276,9 +264,9 @@ For a small task like this, we might only need one spec file.
 
 ```bash
 # Unix/macOS
-mkdir -p openspec/changes/<name>/specs/<capability-name>
+mkdir -p aspec/changes/<name>/specs/<capability-name>
 # Windows (PowerShell)
-# New-Item -ItemType Directory -Force -Path "openspec/changes/<name>/specs/<capability-name>"
+# New-Item -ItemType Directory -Force -Path "aspec/changes/<name>/specs/<capability-name>"
 ```
 
 Draft the spec content:
@@ -305,7 +293,7 @@ Here's the spec:
 This format—WHEN/THEN/AND—makes requirements testable. You can literally read them as test cases.
 ```
 
-Save to `openspec/changes/<name>/specs/<capability>/spec.md`.
+Save to `aspec/changes/<name>/specs/<capability>/spec.md`.
 
 ---
 
@@ -351,7 +339,7 @@ Here's the design:
 For a small task, this captures the key decisions without over-engineering.
 ```
 
-Save to `openspec/changes/<name>/design.md`.
+Save to `aspec/changes/<name>/design.md`.
 
 ---
 
@@ -390,7 +378,7 @@ Each checkbox becomes a unit of work in the apply phase. Ready to implement?
 
 **PAUSE** - Wait for user to confirm they're ready to implement.
 
-Save to `openspec/changes/<name>/tasks.md`.
+Save to `aspec/changes/<name>/tasks.md`.
 
 ---
 
@@ -436,7 +424,7 @@ The change is implemented! One more step—let's archive it.
 ```
 ## Archiving
 
-When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/changes/archive/YYYY-MM-DD-<name>/`.
+When a change is complete, we archive it. This moves it from `aspec/changes/` to `aspec/changes/archive/YYYY-MM-DD-<name>/`.
 
 Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way.
 ```
@@ -444,13 +432,13 @@ Archived changes become your project's decision history—you can always find th
 **DO:**
 
 ```bash
-openspec archive "<name>"
+aspec archive "<name>"
 ```
 
 **SHOW:**
 
 ```
-Archived to: `openspec/changes/archive/YYYY-MM-DD-<name>/`
+Archived to: `aspec/changes/archive/YYYY-MM-DD-<name>/`
 
 The change is now part of your project's history. The code is in your codebase, the decision record is preserved.
 ```
@@ -462,7 +450,7 @@ The change is now part of your project's history. The code is in your codebase,
 ```
 ## Congratulations!
 
-You just completed a full OpenSpec cycle:
+You just completed a full aspec cycle:
 
 1. **Explore** - Thought through the problem
 2. **New** - Created a change container
@@ -513,7 +501,7 @@ Try `/cleto-propose` on something you actually want to build. You've got the rhy
 If the user says they need to stop, want to pause, or seem disengaged:
 
 ```
-No problem! Your change is saved at `openspec/changes/<name>/`.
+No problem! Your change is saved at `aspec/changes/<name>/`.
 
 To pick up where we left off later:
 - `/cleto-continue <name>` - Resume artifact creation
@@ -529,7 +517,7 @@ Exit gracefully without pressure.
 If the user says they just want to see the commands or skip the tutorial:
 
 ```
-## OpenSpec Quick Reference
+## aspec Quick Reference
 
 **Core workflow:**
 

package/commands/cleto-propose.md

@@ -23,7 +23,7 @@ When ready to implement, run /cleto-apply
    Resolve Work Item context in this order — stop at the first source that yields data:
 
    a. **In-session context** — If WI data was already fetched in this session, use it. Proceed to name derivation below.
-   b. **`context.md`** — If a change name was provided as argument and `openspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
+   b. **`context.md`** — If a change name was provided as argument and `aspec/changes/<name>/context.md` exists, read it and use its content. Proceed to name derivation.
    c. **Ask the user** — Use the **AskUserQuestion tool** to ask for the Work Item reference. Two accepted formats:
 
    - **ID + Project** — e.g., ID `12345` and project `MyProject`
@@ -52,16 +52,14 @@ When ready to implement, run /cleto-apply
 
 2. **Create the change directory**
 
-   ```bash
-   openspec new change "<name>"
-   ```
+   Create the directory `aspec/changes/<name>/` in the repository.
 
-   This creates a scaffolded change at `openspec/changes/<name>/` with `.openspec.yaml`.
+   This scaffolds the change at `aspec/changes/<name>/` with `.aspec.yaml`.
 
 3. **Get the artifact build order**
 
    ```bash
-   openspec status --change "<name>" --json
+   aspec status --change "<name>" --json
    ```
 
    Parse the JSON to get:
@@ -79,7 +77,7 @@ When ready to implement, run /cleto-apply
 
    - Get instructions:
      ```bash
-     openspec instructions <artifact-id> --change "<name>" --json
+     aspec instructions <artifact-id> --change "<name>" --json
      ```
    - The instructions JSON includes:
      - `context`: Project background (constraints for you - do NOT include in output)
@@ -97,7 +95,7 @@ When ready to implement, run /cleto-apply
 
    b. **Continue until all `applyRequires` artifacts are complete**
 
-   - After creating each artifact, re-run `openspec status --change "<name>" --json`
+   - After creating each artifact, re-run `aspec status --change "<name>" --json`
    - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
    - Stop when all `applyRequires` artifacts are done
 
@@ -108,7 +106,7 @@ When ready to implement, run /cleto-apply
 
 5. **Show final status**
    ```bash
-   openspec status --change "<name>"
+   aspec status --change "<name>"
    ```
 
 **Output**
@@ -122,7 +120,7 @@ After completing all artifacts, summarize:
 
 **Artifact Creation Guidelines**
 
-- Follow the `instruction` field from `openspec instructions` for each artifact type
+- Follow the `instruction` field from `aspec instructions` for each artifact type
 - The schema defines what each artifact should contain - follow it
 - Read dependency artifacts for context before creating new ones
 - Use `template` as the structure for your output file - fill in its sections

package/commands/cleto-sync.md

@@ -12,7 +12,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).
 
@@ -20,7 +20,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:
 
@@ -33,11 +33,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**:
 
@@ -65,7 +65,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