@devtrack-solution/codesdd 1.2.2 → 1.2.4-rc3

package/dist/core/templates/workflows/apply-change.js

@@ -1,8 +1,8 @@
 export function getApplyChangeSkillTemplate() {
     return {
-        name: 'openspec-apply-change',
-        description: 'Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.',
-        instructions: `Implement tasks from an OpenSpec change.
+        name: 'codesdd-apply-change',
+        description: 'Implement tasks from an CodeSDD change. Use when the user wants to start implementing, continue implementation, or work through tasks.',
+        instructions: `Implement tasks from an CodeSDD change.
 
 **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
@@ -13,13 +13,13 @@ export function getApplyChangeSkillTemplate() {
    If a name is provided, use it. Otherwise:
    - Infer from conversation context if the user mentioned a change
    - Auto-select if only one active change exists
-   - If ambiguous, run \`openspec list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
+   - If ambiguous, run \`codesdd list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
 
    Always announce: "Using change: <name>" and how to override (e.g., \`/opsx:apply <other>\`).
 
 2. **Check status to understand the schema**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to understand:
    - \`schemaName\`: The workflow being used (e.g., "spec-driven")
@@ -28,7 +28,7 @@ export function getApplyChangeSkillTemplate() {
 3. **Get apply instructions**
 
    \`\`\`bash
-   opensdd instructions apply --change "<name>" --json
+   codesdd instructions apply --change "<name>" --json
    \`\`\`
 
    This returns:
@@ -38,7 +38,7 @@ export function getApplyChangeSkillTemplate() {
    - Dynamic instruction based on current state
 
    **Handle states:**
-   - If \`state: "blocked"\` (missing artifacts): show message, suggest using openspec-continue-change
+   - If \`state: "blocked"\` (missing artifacts): show message, suggest using codesdd-continue-change
    - If \`state: "all_done"\`: congratulate, suggest archive
    - Otherwise: proceed to implementation
 
@@ -148,17 +148,17 @@ This skill supports the "actions on a change" model:
 - **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
 - **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxApplyCommandTemplate() {
     return {
         name: 'OPSX: Apply',
-        description: 'Implement tasks from an OpenSpec change (Experimental)',
+        description: 'Implement tasks from an CodeSDD change (Experimental)',
         category: 'Workflow',
         tags: ['workflow', 'artifacts', 'experimental'],
-        content: `Implement tasks from an OpenSpec change.
+        content: `Implement tasks from an CodeSDD change.
 
 **Input**: Optionally specify a change name (e.g., \`/opsx:apply add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
@@ -169,13 +169,13 @@ export function getOpsxApplyCommandTemplate() {
    If a name is provided, use it. Otherwise:
    - Infer from conversation context if the user mentioned a change
    - Auto-select if only one active change exists
-   - If ambiguous, run \`openspec list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
+   - If ambiguous, run \`codesdd list --json\` to get available changes and use the **AskUserQuestion tool** to let the user select
 
    Always announce: "Using change: <name>" and how to override (e.g., \`/opsx:apply <other>\`).
 
 2. **Check status to understand the schema**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to understand:
    - \`schemaName\`: The workflow being used (e.g., "spec-driven")
@@ -184,7 +184,7 @@ export function getOpsxApplyCommandTemplate() {
 3. **Get apply instructions**
 
    \`\`\`bash
-   opensdd instructions apply --change "<name>" --json
+   codesdd instructions apply --change "<name>" --json
    \`\`\`
 
    This returns:

package/dist/core/templates/workflows/archive-change.js

@@ -1,14 +1,14 @@
 export function getArchiveChangeSkillTemplate() {
     return {
-        name: 'openspec-archive-change',
+        name: 'codesdd-archive-change',
         description: 'Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.',
         instructions: `Archive a completed change in the experimental workflow.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, prefer \`opensdd sdd finalize --ref <FEAT-ID>\`.
-Do not create, move, or recreate \`openspec/changes\` in OpenSDD-native projects.
-Use the archive flow below only for explicitly legacy OpenSpec compatibility artifacts.
+If this repository has a \`.sdd/\` directory, prefer \`codesdd sdd finalize --ref <FEAT-ID>\`.
+Do not create, move, or recreate \`legacy-spec/changes\` in CodeSDD-native projects.
+Use the archive flow below only for explicitly legacy CodeSDD compatibility artifacts.
 
 **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
@@ -16,7 +16,7 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
 
 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 \`codesdd 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.
@@ -25,7 +25,7 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
 
 2. **Check artifact completion status**
 
-   Run \`opensdd status --change "<name>" --json\` to check artifact completion.
+   Run \`codesdd status --change "<name>" --json\` to check artifact completion.
 
    Parse the JSON to understand:
    - \`schemaName\`: The workflow being used
@@ -51,10 +51,10 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
 
 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 \`legacy-spec/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 \`legacy-spec/specs/<capability>/spec.md\`
    - Determine what changes would be applied (adds, modifications, removals, renames)
    - Show a combined summary before prompting
 
@@ -62,13 +62,13 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
    - If changes needed: "Sync now (recommended)", "Archive without syncing"
    - If already synced: "Archive now", "Sync anyway", "Cancel"
 
-   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke codesdd-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
 
 5. **Perform the archive**
 
    Create the archive directory if it doesn't exist:
    \`\`\`bash
-   mkdir -p openspec/changes/archive
+   mkdir -p legacy-spec/changes/archive
    \`\`\`
 
    Generate target name using current date: \`YYYY-MM-DD-<change-name>\`
@@ -78,7 +78,7 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
    - If no: Move the change directory to archive
 
    \`\`\`bash
-   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   mv legacy-spec/changes/<name> legacy-spec/changes/archive/YYYY-MM-DD-<name>
    \`\`\`
 
 6. **Display summary**
@@ -97,7 +97,7 @@ Use the archive flow below only for explicitly legacy OpenSpec compatibility art
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** legacy-spec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")
 
 All artifacts complete. All tasks complete.
@@ -105,15 +105,15 @@ All artifacts complete. All tasks complete.
 
 **Guardrails**
 - Always prompt for change selection if not provided
-- Use artifact graph (opensdd status --json) for completion checking
+- Use artifact graph (codesdd 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 .sdd.yaml when moving to archive (it moves with the directory)
 - Show clear summary of what happened
-- If sync is requested, use openspec-sync-specs approach (agent-driven)
+- If sync is requested, use codesdd-sync-specs approach (agent-driven)
 - If delta specs exist, always run the sync assessment and show the combined summary before prompting`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxArchiveCommandTemplate() {
@@ -130,7 +130,7 @@ export function getOpsxArchiveCommandTemplate() {
 
 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 \`codesdd 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.
@@ -139,7 +139,7 @@ export function getOpsxArchiveCommandTemplate() {
 
 2. **Check artifact completion status**
 
-   Run \`opensdd status --change "<name>" --json\` to check artifact completion.
+   Run \`codesdd status --change "<name>" --json\` to check artifact completion.
 
    Parse the JSON to understand:
    - \`schemaName\`: The workflow being used
@@ -165,10 +165,10 @@ export function getOpsxArchiveCommandTemplate() {
 
 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 \`legacy-spec/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 \`legacy-spec/specs/<capability>/spec.md\`
    - Determine what changes would be applied (adds, modifications, removals, renames)
    - Show a combined summary before prompting
 
@@ -176,13 +176,13 @@ export function getOpsxArchiveCommandTemplate() {
    - If changes needed: "Sync now (recommended)", "Archive without syncing"
    - If already synced: "Archive now", "Sync anyway", "Cancel"
 
-   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke codesdd-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
 
 5. **Perform the archive**
 
    Create the archive directory if it doesn't exist:
    \`\`\`bash
-   mkdir -p openspec/changes/archive
+   mkdir -p legacy-spec/changes/archive
    \`\`\`
 
    Generate target name using current date: \`YYYY-MM-DD-<change-name>\`
@@ -192,7 +192,7 @@ export function getOpsxArchiveCommandTemplate() {
    - If no: Move the change directory to archive
 
    \`\`\`bash
-   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   mv legacy-spec/changes/<name> legacy-spec/changes/archive/YYYY-MM-DD-<name>
    \`\`\`
 
 6. **Display summary**
@@ -211,7 +211,7 @@ export function getOpsxArchiveCommandTemplate() {
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** legacy-spec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** ✓ Synced to main specs
 
 All artifacts complete. All tasks complete.
@@ -224,7 +224,7 @@ All artifacts complete. All tasks complete.
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** legacy-spec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** No delta specs
 
 All artifacts complete. All tasks complete.
@@ -237,7 +237,7 @@ All artifacts complete. All tasks complete.
 
 **Change:** <change-name>
 **Schema:** <schema-name>
-**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Archived to:** legacy-spec/changes/archive/YYYY-MM-DD-<name>/
 **Specs:** Sync skipped (user chose to skip)
 
 **Warnings:**
@@ -254,7 +254,7 @@ Review the archive if this was not intentional.
 ## Archive Failed
 
 **Change:** <change-name>
-**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Target:** legacy-spec/changes/archive/YYYY-MM-DD-<name>/
 
 Target archive directory already exists.
 
@@ -266,11 +266,11 @@ Target archive directory already exists.
 
 **Guardrails**
 - Always prompt for change selection if not provided
-- Use artifact graph (opensdd status --json) for completion checking
+- Use artifact graph (codesdd 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 .sdd.yaml when moving to archive (it moves with the directory)
 - Show clear summary of what happened
-- If sync is requested, use the Skill tool to invoke \`openspec-sync-specs\` (agent-driven)
+- If sync is requested, use the Skill tool to invoke \`codesdd-sync-specs\` (agent-driven)
 - If delta specs exist, always run the sync assessment and show the combined summary before prompting`
     };
 }

package/dist/core/templates/workflows/bulk-archive-change.js

@@ -1,14 +1,14 @@
 export function getBulkArchiveChangeSkillTemplate() {
     return {
-        name: 'openspec-bulk-archive-change',
+        name: 'codesdd-bulk-archive-change',
         description: 'Archive multiple completed changes at once. Use when archiving several parallel changes.',
         instructions: `Archive multiple completed changes in a single operation.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
 If this repository has a \`.sdd/\` directory, do not create, move, archive, or recreate
-\`openspec/changes\`. Use \`opensdd sdd finalize --ref <FEAT-ID>\` for canonical
-feature archival. Use this bulk archive flow only for explicitly legacy OpenSpec
+\`legacy-spec/changes\`. Use \`codesdd sdd finalize --ref <FEAT-ID>\` for canonical
+feature archival. Use this bulk archive flow only for explicitly legacy CodeSDD
 compatibility artifacts.
 
 This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
@@ -19,7 +19,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 \`codesdd list --json\` to get all active changes.
 
    If no active changes exist, inform user and stop.
 
@@ -36,15 +36,15 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
 
    For each selected change, collect:
 
-   a. **Artifact status** - Run \`opensdd status --change "<name>" --json\`
+   a. **Artifact status** - Run \`codesdd 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 \`legacy-spec/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 \`legacy-spec/changes/<name>/specs/\` directory
       - List which capability specs exist
       - For each, extract requirement names (lines matching \`### Requirement: <name>\`)
 
@@ -121,14 +121,14 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
    Process changes in the determined order (respecting conflict resolution):
 
    a. **Sync specs** if delta specs exist:
-      - Use the openspec-sync-specs approach (agent-driven intelligent merge)
+      - Use the codesdd-sync-specs approach (agent-driven intelligent merge)
       - For conflicts, apply in resolved order
       - Track if sync was done
 
    b. **Perform the archive**:
       \`\`\`bash
-      mkdir -p openspec/changes/archive
-      mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+      mkdir -p legacy-spec/changes/archive
+      mv legacy-spec/changes/<name> legacy-spec/changes/archive/YYYY-MM-DD-<name>
       \`\`\`
 
    c. **Track outcome** for each change:
@@ -241,12 +241,12 @@ 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 .sdd.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`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxBulkArchiveCommandTemplate() {
@@ -257,11 +257,11 @@ export function getOpsxBulkArchiveCommandTemplate() {
         tags: ['workflow', 'archive', 'experimental', 'bulk'],
         content: `Archive multiple completed changes in a single operation.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
 If this repository has a \`.sdd/\` directory, do not create, move, archive, or recreate
-\`openspec/changes\`. Use \`opensdd sdd finalize --ref <FEAT-ID>\` for canonical
-feature archival. Use this bulk archive flow only for explicitly legacy OpenSpec
+\`legacy-spec/changes\`. Use \`codesdd sdd finalize --ref <FEAT-ID>\` for canonical
+feature archival. Use this bulk archive flow only for explicitly legacy CodeSDD
 compatibility artifacts.
 
 This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
@@ -272,7 +272,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 \`codesdd list --json\` to get all active changes.
 
    If no active changes exist, inform user and stop.
 
@@ -289,15 +289,15 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
 
    For each selected change, collect:
 
-   a. **Artifact status** - Run \`opensdd status --change "<name>" --json\`
+   a. **Artifact status** - Run \`codesdd 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 \`legacy-spec/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 \`legacy-spec/changes/<name>/specs/\` directory
       - List which capability specs exist
       - For each, extract requirement names (lines matching \`### Requirement: <name>\`)
 
@@ -374,14 +374,14 @@ This skill allows you to batch-archive changes, handling spec conflicts intellig
    Process changes in the determined order (respecting conflict resolution):
 
    a. **Sync specs** if delta specs exist:
-      - Use the openspec-sync-specs approach (agent-driven intelligent merge)
+      - Use the codesdd-sync-specs approach (agent-driven intelligent merge)
       - For conflicts, apply in resolved order
       - Track if sync was done
 
    b. **Perform the archive**:
       \`\`\`bash
-      mkdir -p openspec/changes/archive
-      mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+      mkdir -p legacy-spec/changes/archive
+      mv legacy-spec/changes/<name> legacy-spec/changes/archive/YYYY-MM-DD-<name>
       \`\`\`
 
    c. **Track outcome** for each change:
@@ -494,7 +494,7 @@ 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 .sdd.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/dist/core/templates/workflows/continue-change.js

@@ -1,7 +1,7 @@
 export function getContinueChangeSkillTemplate() {
     return {
-        name: 'openspec-continue-change',
-        description: 'Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.',
+        name: 'codesdd-continue-change',
+        description: 'Continue working on an CodeSDD change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.',
         instructions: `Continue working on a change by creating the next artifact.
 
 **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
@@ -10,7 +10,7 @@ export function getContinueChangeSkillTemplate() {
 
 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 \`codesdd 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:
    - Change name
@@ -24,7 +24,7 @@ export function getContinueChangeSkillTemplate() {
 
 2. **Check current status**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to understand current state. The response includes:
    - \`schemaName\`: The workflow schema being used (e.g., "spec-driven")
@@ -47,7 +47,7 @@ export function getContinueChangeSkillTemplate() {
    - Pick the FIRST artifact with \`status: "ready"\` from the status output
    - Get its instructions:
      \`\`\`bash
-     opensdd instructions <artifact-id> --change "<name>" --json
+     codesdd instructions <artifact-id> --change "<name>" --json
      \`\`\`
    - Parse the JSON. The key fields are:
      - \`context\`: Project background (constraints for you - do NOT include in output)
@@ -72,7 +72,7 @@ export function getContinueChangeSkillTemplate() {
 
 4. **After creating an artifact, show progress**
    \`\`\`bash
-   opensdd status --change "<name>"
+   codesdd status --change "<name>"
    \`\`\`
 
 **Output**
@@ -110,8 +110,8 @@ For other schemas, follow the \`instruction\` field from the CLI output.
   - Do NOT copy \`<context>\`, \`<rules>\`, \`<project_context>\` blocks into the artifact
   - These guide what you write, but should never appear in the output`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxContinueCommandTemplate() {
@@ -128,7 +128,7 @@ export function getOpsxContinueCommandTemplate() {
 
 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 \`codesdd 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:
    - Change name
@@ -142,7 +142,7 @@ export function getOpsxContinueCommandTemplate() {
 
 2. **Check current status**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to understand current state. The response includes:
    - \`schemaName\`: The workflow schema being used (e.g., "spec-driven")
@@ -165,7 +165,7 @@ export function getOpsxContinueCommandTemplate() {
    - Pick the FIRST artifact with \`status: "ready"\` from the status output
    - Get its instructions:
      \`\`\`bash
-     opensdd instructions <artifact-id> --change "<name>" --json
+     codesdd instructions <artifact-id> --change "<name>" --json
      \`\`\`
    - Parse the JSON. The key fields are:
      - \`context\`: Project background (constraints for you - do NOT include in output)
@@ -190,7 +190,7 @@ export function getOpsxContinueCommandTemplate() {
 
 4. **After creating an artifact, show progress**
    \`\`\`bash
-   opensdd status --change "<name>"
+   codesdd status --change "<name>"
    \`\`\`
 
 **Output**