@devtrack-solution/codesdd 1.2.2 → 1.2.3

package/dist/core/sdd/write-manifest.js

@@ -2,7 +2,7 @@ import { promises as fs } from 'node:fs';
 import path from 'node:path';
 import { RootResolver } from './root-resolver.js';
 import { loadProjectSddConfig, resolveSddPaths } from './state.js';
-import { parseWorkspaceYamlDocument, workspaceSchemaForFile } from './workspace-schemas.js';
+import { parsePromptAssetYamlDocument, parseWorkspaceYamlDocument, workspaceSchemaForFile } from './workspace-schemas.js';
 export class SddWritePolicyError extends Error {
     constructor(message) {
         super(message);
@@ -276,10 +276,13 @@ function validateTemplatesPath(operation, policyPath, segments, label) {
             return;
         throw policyError(label, operation, policyPath, 'templates root may only be created as a directory');
     }
-    if (segments.length === 2 && /\.(md|ya?ml)$/.test(segments[1]) && operation.type !== 'mkdir') {
+    if (segments.length === 2 && operation.type === 'delete' && segments[1].endsWith('.md')) {
         return;
     }
-    throw policyError(label, operation, policyPath, 'templates accepts .md/.yaml files directly under root');
+    if (segments.length === 2 && /\.ya?ml$/.test(segments[1]) && operation.type !== 'mkdir') {
+        return;
+    }
+    throw policyError(label, operation, policyPath, 'templates accepts YAML files directly under root; Markdown templates may only be deleted during cleanup');
 }
 function validateSkillsPath(operation, policyPath, segments, label) {
     if (segments.length === 1) {
@@ -315,10 +318,16 @@ function validatePromptsPath(operation, policyPath, segments, label) {
             return;
         throw policyError(label, operation, policyPath, 'prompts root may only be created as a directory');
     }
+    if (segments.length === 3 && segments[1] === 'assets' && segments[2].endsWith('.yaml') && operation.type !== 'mkdir') {
+        if (operation.type === 'write') {
+            validatePromptAssetYamlContent(operation.content, label, operation, policyPath);
+        }
+        return;
+    }
     if (segments.length === 2 && segments[1].endsWith('.md') && operation.type !== 'mkdir') {
         return;
     }
-    throw policyError(label, operation, policyPath, 'prompts accepts markdown files directly under root');
+    throw policyError(label, operation, policyPath, 'prompts accepts markdown files directly under root and YAML assets under prompts/assets/');
 }
 function validateSourcesPath(operation, policyPath, segments, label) {
     if (segments.length === 1) {
@@ -350,4 +359,13 @@ function validateWorkspaceYamlContent(content, fileName, label, operation, polic
         throw policyError(label, operation, policyPath, `workspace YAML schema validation failed: ${message}`);
     }
 }
+function validatePromptAssetYamlContent(content, label, operation, policyPath) {
+    try {
+        parsePromptAssetYamlDocument(content);
+    }
+    catch (err) {
+        const message = err instanceof Error ? err.message : String(err);
+        throw policyError(label, operation, policyPath, `prompt asset YAML schema validation failed: ${message}`);
+    }
+}
 //# sourceMappingURL=write-manifest.js.map

package/dist/core/shared/skill-generation.d.ts

@@ -42,7 +42,7 @@ export declare function getCommandContents(workflowFilter?: readonly string[]):
  * Generates skill file content with YAML frontmatter.
  *
  * @param template - The skill template
- * @param generatedByVersion - The OpenSpec version to embed in the file
+ * @param generatedByVersion - The CodeSDD version to embed in the file
  * @param transformInstructions - Optional callback to transform the instructions content
  */
 export declare function generateSkillContent(template: SkillTemplate, generatedByVersion: string, transformInstructions?: (instructions: string) => string): string;

package/dist/core/shared/skill-generation.js

@@ -18,18 +18,18 @@ function ensurePtBrGuardrail(content) {
  */
 export function getSkillTemplates(workflowFilter) {
     const all = [
-        { template: getExploreSkillTemplate(), dirName: 'openspec-explore', workflowId: 'explore' },
-        { template: getNewChangeSkillTemplate(), dirName: 'openspec-new-change', workflowId: 'new' },
-        { template: getContinueChangeSkillTemplate(), dirName: 'openspec-continue-change', workflowId: 'continue' },
-        { template: getApplyChangeSkillTemplate(), dirName: 'openspec-apply-change', workflowId: 'apply' },
-        { template: getFfChangeSkillTemplate(), dirName: 'openspec-ff-change', workflowId: 'ff' },
-        { template: getSyncSpecsSkillTemplate(), dirName: 'openspec-sync-specs', workflowId: 'sync' },
-        { template: getArchiveChangeSkillTemplate(), dirName: 'openspec-archive-change', workflowId: 'archive' },
-        { template: getBulkArchiveChangeSkillTemplate(), dirName: 'openspec-bulk-archive-change', workflowId: 'bulk-archive' },
-        { template: getVerifyChangeSkillTemplate(), dirName: 'openspec-verify-change', workflowId: 'verify' },
-        { template: getOnboardSkillTemplate(), dirName: 'openspec-onboard', workflowId: 'onboard' },
-        { template: getOpsxProposeSkillTemplate(), dirName: 'openspec-propose', workflowId: 'propose' },
-        { template: getSddSkillTemplate(), dirName: 'openspec-sdd', workflowId: 'sdd' },
+        { template: getExploreSkillTemplate(), dirName: 'codesdd-explore', workflowId: 'explore' },
+        { template: getNewChangeSkillTemplate(), dirName: 'codesdd-new-change', workflowId: 'new' },
+        { template: getContinueChangeSkillTemplate(), dirName: 'codesdd-continue-change', workflowId: 'continue' },
+        { template: getApplyChangeSkillTemplate(), dirName: 'codesdd-apply-change', workflowId: 'apply' },
+        { template: getFfChangeSkillTemplate(), dirName: 'codesdd-ff-change', workflowId: 'ff' },
+        { template: getSyncSpecsSkillTemplate(), dirName: 'codesdd-sync-specs', workflowId: 'sync' },
+        { template: getArchiveChangeSkillTemplate(), dirName: 'codesdd-archive-change', workflowId: 'archive' },
+        { template: getBulkArchiveChangeSkillTemplate(), dirName: 'codesdd-bulk-archive-change', workflowId: 'bulk-archive' },
+        { template: getVerifyChangeSkillTemplate(), dirName: 'codesdd-verify-change', workflowId: 'verify' },
+        { template: getOnboardSkillTemplate(), dirName: 'codesdd-onboard', workflowId: 'onboard' },
+        { template: getOpsxProposeSkillTemplate(), dirName: 'codesdd-propose', workflowId: 'propose' },
+        { template: getSddSkillTemplate(), dirName: 'codesdd-sdd', workflowId: 'sdd' },
     ];
     if (!workflowFilter)
         return all;
@@ -81,7 +81,7 @@ export function getCommandContents(workflowFilter) {
  * Generates skill file content with YAML frontmatter.
  *
  * @param template - The skill template
- * @param generatedByVersion - The OpenSpec version to embed in the file
+ * @param generatedByVersion - The CodeSDD version to embed in the file
  * @param transformInstructions - Optional callback to transform the instructions content
  */
 export function generateSkillContent(template, generatedByVersion, transformInstructions) {
@@ -93,9 +93,9 @@ export function generateSkillContent(template, generatedByVersion, transformInst
 name: ${template.name}
 description: ${template.description}
 license: ${template.license || 'MIT'}
-compatibility: ${template.compatibility || 'Requires opensdd CLI.'}
+compatibility: ${template.compatibility || 'Requires codesdd CLI.'}
 metadata:
-  author: ${template.metadata?.author || 'openspec'}
+  author: ${template.metadata?.author || 'codesdd'}
   version: "${template.metadata?.version || '1.0'}"
   generatedBy: "${generatedByVersion}"
 ---

package/dist/core/shared/tool-detection.d.ts

@@ -4,12 +4,12 @@
  * Shared utilities for detecting tool configurations and version status.
  */
 /**
- * Names of skill directories created by openspec init.
+ * Names of skill directories created by codesdd init.
  */
-export declare const SKILL_NAMES: readonly ["openspec-explore", "openspec-new-change", "openspec-continue-change", "openspec-apply-change", "openspec-ff-change", "openspec-sync-specs", "openspec-archive-change", "openspec-bulk-archive-change", "openspec-verify-change", "openspec-onboard", "openspec-propose"];
+export declare const SKILL_NAMES: readonly ["codesdd-explore", "codesdd-new-change", "codesdd-continue-change", "codesdd-apply-change", "codesdd-ff-change", "codesdd-sync-specs", "codesdd-archive-change", "codesdd-bulk-archive-change", "codesdd-verify-change", "codesdd-onboard", "codesdd-propose"];
 export type SkillName = (typeof SKILL_NAMES)[number];
 /**
- * IDs of command templates created by openspec init.
+ * IDs of command templates created by codesdd init.
  */
 export declare const COMMAND_IDS: readonly ["explore", "new", "continue", "apply", "ff", "sync", "archive", "bulk-archive", "verify", "onboard", "propose"];
 export type CommandId = (typeof COMMAND_IDS)[number];

package/dist/core/shared/tool-detection.js

@@ -7,23 +7,23 @@ import path from 'path';
 import * as fs from 'fs';
 import { AI_TOOLS } from '../config.js';
 /**
- * Names of skill directories created by openspec init.
+ * Names of skill directories created by codesdd init.
  */
 export const SKILL_NAMES = [
-    'openspec-explore',
-    'openspec-new-change',
-    'openspec-continue-change',
-    'openspec-apply-change',
-    'openspec-ff-change',
-    'openspec-sync-specs',
-    'openspec-archive-change',
-    'openspec-bulk-archive-change',
-    'openspec-verify-change',
-    'openspec-onboard',
-    'openspec-propose',
+    'codesdd-explore',
+    'codesdd-new-change',
+    'codesdd-continue-change',
+    'codesdd-apply-change',
+    'codesdd-ff-change',
+    'codesdd-sync-specs',
+    'codesdd-archive-change',
+    'codesdd-bulk-archive-change',
+    'codesdd-verify-change',
+    'codesdd-onboard',
+    'codesdd-propose',
 ];
 /**
- * IDs of command templates created by openspec init.
+ * IDs of command templates created by codesdd init.
  */
 export const COMMAND_IDS = [
     'explore',
@@ -92,7 +92,7 @@ export function extractGeneratedByVersion(skillFilePath) {
         // ---
         // ...
         // metadata:
-        //   author: openspec
+        //   author: codesdd
         //   version: "1.0"
         //   generatedBy: "0.23.0"
         // ---

package/dist/core/specs-apply.js

@@ -9,7 +9,7 @@ import path from 'path';
 import chalk from 'chalk';
 import { extractRequirementsSection, parseDeltaSpec, normalizeRequirementName, } from './parsers/requirement-blocks.js';
 import { Validator } from './validation/validator.js';
-import { resolveOpenSpecLiveSubpath } from './sdd/services/legacy-capability.service.js';
+import { resolveLegacySpecLiveSubpath } from './sdd/services/legacy-capability.service.js';
 // -----------------------------------------------------------------------------
 // Public API
 // -----------------------------------------------------------------------------
@@ -264,7 +264,7 @@ export async function writeUpdatedSpec(update, rebuilt, counts) {
     await fs.mkdir(targetDir, { recursive: true });
     await fs.writeFile(update.target, rebuilt);
     const specName = path.basename(path.dirname(update.target));
-    console.log(`Applying changes to openspec/specs/${specName}/spec.md:`);
+    console.log(`Applying changes to legacy-spec/specs/${specName}/spec.md:`);
     if (counts.added)
         console.log(`  + ${counts.added} added`);
     if (counts.modified)
@@ -290,8 +290,8 @@ export function buildSpecSkeleton(specFolderName, changeName) {
  * @returns Result of the operation with counts
  */
 export async function applySpecs(projectRoot, changeName, options = {}) {
-    const changeDir = resolveOpenSpecLiveSubpath(projectRoot, 'changes', changeName);
-    const mainSpecsDir = resolveOpenSpecLiveSubpath(projectRoot, 'specs');
+    const changeDir = resolveLegacySpecLiveSubpath(projectRoot, 'changes', changeName);
+    const mainSpecsDir = resolveLegacySpecLiveSubpath(projectRoot, 'specs');
     // Verify change exists
     try {
         const stat = await fs.stat(changeDir);
@@ -344,7 +344,7 @@ export async function applySpecs(projectRoot, changeName, options = {}) {
             await fs.mkdir(targetDir, { recursive: true });
             await fs.writeFile(p.update.target, p.rebuilt);
             if (!options.silent) {
-                console.log(`Applying changes to openspec/specs/${capability}/spec.md:`);
+                console.log(`Applying changes to legacy-spec/specs/${capability}/spec.md:`);
                 if (p.counts.added)
                     console.log(`  + ${p.counts.added} added`);
                 if (p.counts.modified)
@@ -356,7 +356,7 @@ export async function applySpecs(projectRoot, changeName, options = {}) {
             }
         }
         else if (!options.silent) {
-            console.log(`Would apply changes to openspec/specs/${capability}/spec.md:`);
+            console.log(`Would apply changes to legacy-spec/specs/${capability}/spec.md:`);
             if (p.counts.added)
                 console.log(`  + ${p.counts.added} added`);
             if (p.counts.modified)

package/dist/core/templates/index.d.ts

@@ -1,5 +1,5 @@
 /**
- * Template exports for OpenSpec.
+ * Template exports for CodeSDD.
  *
  * The old config file templates (AGENTS.md, project.md, claude-template, etc.)
  * have been removed. The skill-based workflow uses skill-templates.ts directly.

package/dist/core/templates/index.js

@@ -1,5 +1,5 @@
 /**
- * Template exports for OpenSpec.
+ * Template exports for CodeSDD.
  *
  * The old config file templates (AGENTS.md, project.md, claude-template, etc.)
  * have been removed. The skill-based workflow uses skill-templates.ts directly.

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`
     };
 }