@devtrack-solution/codesdd 1.2.2 → 1.2.4-rc3

package/dist/core/templates/workflows/propose.js

@@ -1,16 +1,16 @@
 export function getOpsxProposeSkillTemplate() {
     return {
-        name: 'openspec-propose',
+        name: 'codesdd-propose',
         description: 'Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.',
         instructions: `Propose a new change - create the change and generate all artifacts in one step.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, do not create or recreate \`openspec/changes\`.
-Use the OpenSDD lifecycle instead: \`opensdd sdd insight\`, \`opensdd sdd debate\`,
-\`opensdd sdd decide\`, \`opensdd sdd breakdown\`, and \`opensdd sdd start\`.
-Use the OPSX/OpenSpec change flow below only for explicitly legacy projects or when
-the user explicitly asks for legacy OpenSpec compatibility artifacts.
+If this repository has a \`.sdd/\` directory, do not create or recreate \`legacy-spec/changes\`.
+Use the CodeSDD lifecycle instead: \`codesdd sdd insight\`, \`codesdd sdd debate\`,
+\`codesdd sdd decide\`, \`codesdd sdd breakdown\`, and \`codesdd sdd start\`.
+Use the OPSX/CodeSDD change flow below only for explicitly legacy projects or when
+the user explicitly asks for legacy CodeSDD compatibility artifacts.
 
 I'll create a change with artifacts:
 - proposal.md (what & why)
@@ -36,13 +36,13 @@ When ready to implement, run /opsx:apply
 
 2. **Create the change directory**
    \`\`\`bash
-   opensdd new change "<name>"
+   codesdd new change "<name>"
    \`\`\`
-   This creates a scaffolded change at \`openspec/changes/<name>/\` with \`.openspec.yaml\`.
+   This creates a scaffolded change at \`legacy-spec/changes/<name>/\` with \`.sdd.yaml\`.
 
 3. **Get the artifact build order**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to get:
    - \`applyRequires\`: array of artifact IDs needed before implementation (e.g., \`["tasks"]\`)
@@ -57,7 +57,7 @@ When ready to implement, run /opsx:apply
    a. **For each artifact that is \`ready\` (dependencies satisfied)**:
       - Get instructions:
         \`\`\`bash
-        opensdd instructions <artifact-id> --change "<name>" --json
+        codesdd instructions <artifact-id> --change "<name>" --json
         \`\`\`
       - The instructions JSON includes:
         - \`context\`: Project background (constraints for you - do NOT include in output)
@@ -72,7 +72,7 @@ When ready to implement, run /opsx:apply
       - Show brief progress: "Created <artifact-id>"
 
    b. **Continue until all \`applyRequires\` artifacts are complete**
-      - After creating each artifact, re-run \`opensdd status --change "<name>" --json\`
+      - After creating each artifact, re-run \`codesdd 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
 
@@ -82,7 +82,7 @@ When ready to implement, run /opsx:apply
 
 5. **Show final status**
    \`\`\`bash
-   opensdd status --change "<name>"
+   codesdd status --change "<name>"
    \`\`\`
 
 **Output**
@@ -95,7 +95,7 @@ After completing all artifacts, summarize:
 
 **Artifact Creation Guidelines**
 
-- Follow the \`instruction\` field from \`opensdd instructions\` for each artifact type
+- Follow the \`instruction\` field from \`codesdd 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
@@ -110,8 +110,8 @@ After completing all artifacts, summarize:
 - If a change with that name already exists, ask if user wants to continue it or create a new one
 - Verify each artifact file exists after writing before proceeding to next`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxProposeCommandTemplate() {
@@ -146,13 +146,13 @@ When ready to implement, run /opsx:apply
 
 2. **Create the change directory**
    \`\`\`bash
-   opensdd new change "<name>"
+   codesdd new change "<name>"
    \`\`\`
-   This creates a scaffolded change at \`openspec/changes/<name>/\` with \`.openspec.yaml\`.
+   This creates a scaffolded change at \`legacy-spec/changes/<name>/\` with \`.sdd.yaml\`.
 
 3. **Get the artifact build order**
    \`\`\`bash
-   opensdd status --change "<name>" --json
+   codesdd status --change "<name>" --json
    \`\`\`
    Parse the JSON to get:
    - \`applyRequires\`: array of artifact IDs needed before implementation (e.g., \`["tasks"]\`)
@@ -167,7 +167,7 @@ When ready to implement, run /opsx:apply
    a. **For each artifact that is \`ready\` (dependencies satisfied)**:
       - Get instructions:
         \`\`\`bash
-        opensdd instructions <artifact-id> --change "<name>" --json
+        codesdd instructions <artifact-id> --change "<name>" --json
         \`\`\`
       - The instructions JSON includes:
         - \`context\`: Project background (constraints for you - do NOT include in output)
@@ -182,7 +182,7 @@ When ready to implement, run /opsx:apply
       - Show brief progress: "Created <artifact-id>"
 
    b. **Continue until all \`applyRequires\` artifacts are complete**
-      - After creating each artifact, re-run \`opensdd status --change "<name>" --json\`
+      - After creating each artifact, re-run \`codesdd 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
 
@@ -192,7 +192,7 @@ When ready to implement, run /opsx:apply
 
 5. **Show final status**
    \`\`\`bash
-   opensdd status --change "<name>"
+   codesdd status --change "<name>"
    \`\`\`
 
 **Output**
@@ -205,7 +205,7 @@ After completing all artifacts, summarize:
 
 **Artifact Creation Guidelines**
 
-- Follow the \`instruction\` field from \`opensdd instructions\` for each artifact type
+- Follow the \`instruction\` field from \`codesdd 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/dist/core/templates/workflows/sdd.js

@@ -1,6 +1,6 @@
 export function getSddSkillTemplate() {
     return {
-        name: 'openspec-sdd',
+        name: 'codesdd-sdd',
         description: 'Atue como Arquiteto Principal para manter o Software Design Document (SDD) continuo.',
         instructions: `Voce e o Arquiteto Principal de Software responsavel por manter o Software Design Document (SDD) continuo do sistema.
 Seu foco principal e design de alto nivel, arquitetura, estrutura do projeto e consistencia documental, e NAO escrever codigo de aplicacao.
@@ -28,22 +28,22 @@ Voce pode ler arquivos, escrever Markdown e organizar estruturas de diretorios.
 - Escrever novas especificacoes quando solicitado.
 - Se o usuario pedir implementacao direta de codigo, orientar primeiro o planejamento e a documentacao da mudanca.
 
-## Consciencia OpenSDD
+## Consciencia CodeSDD
 
-Voce tem contexto do sistema OpenSDD. O estado operacional canonico vive em
+Voce tem contexto do sistema CodeSDD. O estado operacional canonico vive em
 \`.sdd/state/*.yaml\`; arquivos Markdown sao visoes, guias ou documentacao
-curada. Material OpenSpec importado em \`.sdd/sources/legacy/spec-corpus\` e
+curada. Material Legacy spec importado em \`.sdd/sources/legacy/spec-corpus\` e
 somente contexto legado, nao fonte operacional de verdade.
 
 ### Checagem de contexto
 
-No inicio, consulte \`opensdd sdd next\`, \`opensdd sdd check --render\` e leia
+No inicio, consulte \`codesdd sdd next\`, \`codesdd sdd check --render\` e leia
 \`README.md\`, \`.sdd/core/\`, \`.sdd/state/*.yaml\` e artefatos SDD relevantes.
 
 ### Atualizacao documental
 
 Se houver divergencia entre codigo e documentacao, proponha ajuste nos documentos
-e no estado OpenSDD canonico quando aplicavel. Se o usuario anunciar uma decisao,
+e no estado CodeSDD canonico quando aplicavel. Se o usuario anunciar uma decisao,
 registre-a no artefato correto.
 
 ## Guardrails
@@ -53,8 +53,8 @@ registre-a no artefato correto.
 - **Evitar suposicoes:** validar com o usuario quando houver incerteza de direcao arquitetural.
     `,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxSddCommandTemplate() {

package/dist/core/templates/workflows/sync-specs.js

@@ -1,13 +1,13 @@
 export function getSyncSpecsSkillTemplate() {
     return {
-        name: 'openspec-sync-specs',
+        name: 'codesdd-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.',
         instructions: `Sync delta specs from a change to main specs.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, do not create or recreate \`openspec/specs\`
-or \`openspec/changes\`. Treat imported OpenSpec files under
+If this repository has a \`.sdd/\` directory, do not create or recreate \`legacy-spec/specs\`
+or \`legacy-spec/changes\`. Treat imported CodeSDD files under
 \`.sdd/sources/legacy/spec-corpus\` as read-only legacy context unless the user explicitly
 asks for legacy compatibility maintenance.
 
@@ -19,7 +19,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 \`codesdd list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
 
    Show changes that have delta specs (under \`specs/\` directory).
 
@@ -27,7 +27,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 \`legacy-spec/changes/<name>/specs/*/spec.md\`.
 
    Each delta spec file contains sections like:
    - \`## ADDED Requirements\` - New requirements to add
@@ -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 \`legacy-spec/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 \`legacy-spec/specs/<capability>/spec.md\` (may not exist yet)
 
    c. **Apply changes intelligently**:
 
@@ -66,7 +66,7 @@ This is an **agent-driven** operation - you will read delta specs and directly e
       - Find the FROM requirement, rename to TO
 
    d. **Create new main spec** if capability doesn't exist yet:
-      - Create \`openspec/specs/<capability>/spec.md\`
+      - Create \`legacy-spec/specs/<capability>/spec.md\`
       - Add Purpose section (can be brief, mark as TBD)
       - Add Requirements section with the ADDED requirements
 
@@ -137,8 +137,8 @@ Main specs are now updated. The change remains active - archive when implementat
 - Show what you're changing as you go
 - The operation should be idempotent - running twice should give same result`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxSyncCommandTemplate() {
@@ -149,10 +149,10 @@ export function getOpsxSyncCommandTemplate() {
         tags: ['workflow', 'specs', 'experimental'],
         content: `Sync delta specs from a change to main specs.
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, do not create or recreate \`openspec/specs\`
-or \`openspec/changes\`. Treat imported OpenSpec files under
+If this repository has a \`.sdd/\` directory, do not create or recreate \`legacy-spec/specs\`
+or \`legacy-spec/changes\`. Treat imported CodeSDD files under
 \`.sdd/sources/legacy/spec-corpus\` as read-only legacy context unless the user explicitly
 asks for legacy compatibility maintenance.
 
@@ -164,7 +164,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 \`codesdd list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
 
    Show changes that have delta specs (under \`specs/\` directory).
 
@@ -172,7 +172,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 \`legacy-spec/changes/<name>/specs/*/spec.md\`.
 
    Each delta spec file contains sections like:
    - \`## ADDED Requirements\` - New requirements to add
@@ -184,11 +184,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 \`legacy-spec/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 \`legacy-spec/specs/<capability>/spec.md\` (may not exist yet)
 
    c. **Apply changes intelligently**:
 
@@ -211,7 +211,7 @@ This is an **agent-driven** operation - you will read delta specs and directly e
       - Find the FROM requirement, rename to TO
 
    d. **Create new main spec** if capability doesn't exist yet:
-      - Create \`openspec/specs/<capability>/spec.md\`
+      - Create \`legacy-spec/specs/<capability>/spec.md\`
       - Add Purpose section (can be brief, mark as TBD)
       - Add Requirements section with the ADDED requirements
 

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

@@ -1,14 +1,14 @@
 export function getVerifyChangeSkillTemplate() {
     return {
-        name: 'openspec-verify-change',
+        name: 'codesdd-verify-change',
         description: 'Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.',
         instructions: `Verify that an implementation matches the change artifacts (specs, tasks, design).
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, verify against OpenSDD canonical state
+If this repository has a \`.sdd/\` directory, verify against CodeSDD canonical state
 first: \`.sdd/state/*.yaml\`, \`.sdd/active/<FEAT-ID>\`, and \`.sdd/planned/<FEAT-ID>\`.
-Use OpenSpec paths only as imported legacy context or when the user explicitly asks
+Use CodeSDD paths only as imported legacy context or when the user explicitly asks
 for legacy compatibility validation.
 
 **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.
@@ -17,7 +17,7 @@ for legacy compatibility validation.
 
 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 changes that have implementation tasks (tasks artifact exists).
    Include the schema used for each change if available.
@@ -27,7 +27,7 @@ for legacy compatibility validation.
 
 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")
@@ -36,7 +36,7 @@ for legacy compatibility validation.
 3. **Get the change directory and load artifacts**
 
    \`\`\`bash
-   opensdd instructions apply --change "<name>" --json
+   codesdd instructions apply --change "<name>" --json
    \`\`\`
 
    This returns the change directory and context files. Read all available artifacts from \`contextFiles\`.
@@ -61,7 +61,7 @@ for legacy compatibility validation.
      - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
 
    **Spec Coverage**:
-   - If delta specs exist in \`openspec/changes/<name>/specs/\`:
+   - If delta specs exist in \`legacy-spec/changes/<name>/specs/\`:
      - Extract all requirements (marked with "### Requirement:")
      - For each requirement:
        - Search codebase for keywords related to the requirement
@@ -167,8 +167,8 @@ Use clear markdown with:
 - Specific, actionable recommendations
 - No vague suggestions like "consider reviewing"`,
         license: 'MIT',
-        compatibility: 'Requires opensdd CLI.',
-        metadata: { author: 'openspec', version: '1.0' },
+        compatibility: 'Requires codesdd CLI.',
+        metadata: { author: 'codesdd', version: '1.0' },
     };
 }
 export function getOpsxVerifyCommandTemplate() {
@@ -179,11 +179,11 @@ export function getOpsxVerifyCommandTemplate() {
         tags: ['workflow', 'verify', 'experimental'],
         content: `Verify that an implementation matches the change artifacts (specs, tasks, design).
 
-**OpenSDD-native guardrail**
+**CodeSDD-native guardrail**
 
-If this repository has a \`.sdd/\` directory, verify against OpenSDD canonical state
+If this repository has a \`.sdd/\` directory, verify against CodeSDD canonical state
 first: \`.sdd/state/*.yaml\`, \`.sdd/active/<FEAT-ID>\`, and \`.sdd/planned/<FEAT-ID>\`.
-Use OpenSpec paths only as imported legacy context or when the user explicitly asks
+Use CodeSDD paths only as imported legacy context or when the user explicitly asks
 for legacy compatibility validation.
 
 **Input**: Optionally specify a change name after \`/opsx:verify\` (e.g., \`/opsx:verify add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
@@ -192,7 +192,7 @@ for legacy compatibility validation.
 
 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 changes that have implementation tasks (tasks artifact exists).
    Include the schema used for each change if available.
@@ -202,7 +202,7 @@ for legacy compatibility validation.
 
 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")
@@ -211,7 +211,7 @@ for legacy compatibility validation.
 3. **Get the change directory and load artifacts**
 
    \`\`\`bash
-   opensdd instructions apply --change "<name>" --json
+   codesdd instructions apply --change "<name>" --json
    \`\`\`
 
    This returns the change directory and context files. Read all available artifacts from \`contextFiles\`.
@@ -236,7 +236,7 @@ for legacy compatibility validation.
      - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
 
    **Spec Coverage**:
-   - If delta specs exist in \`openspec/changes/<name>/specs/\`:
+   - If delta specs exist in \`legacy-spec/changes/<name>/specs/\`:
      - Extract all requirements (marked with "### Requirement:")
      - For each requirement:
        - Search codebase for keywords related to the requirement

package/dist/core/update.d.ts

@@ -1,7 +1,7 @@
 /**
  * Update Command
  *
- * Refreshes OpenSpec skills and commands for configured tools.
+ * Refreshes CodeSDD skills and commands for configured tools.
  * Supports profile-aware updates, delivery changes, migration, and smart update detection.
  */
 /**
@@ -59,7 +59,7 @@ export declare class UpdateCommand {
      */
     private removeUnselectedCommandFiles;
     /**
-     * Detect and handle legacy OpenSpec artifacts.
+     * Detect and handle legacy CodeSDD artifacts.
      * Unlike init, update warns but continues if legacy files found in non-interactive mode.
      * Returns array of tool IDs that were newly configured during legacy upgrade.
      */

package/dist/core/update.js

@@ -1,7 +1,7 @@
 /**
  * Update Command
  *
- * Refreshes OpenSpec skills and commands for configured tools.
+ * Refreshes CodeSDD skills and commands for configured tools.
  * Supports profile-aware updates, delivery changes, migration, and smart update detection.
  */
 import path from 'path';
@@ -11,7 +11,7 @@ import * as fs from 'fs';
 import { createRequire } from 'module';
 import { FileSystemUtils } from '../utils/file-system.js';
 import { transformToHyphenCommands } from '../utils/command-references.js';
-import { AI_TOOLS, OPENSPEC_DIR_NAME } from './config.js';
+import { AI_TOOLS } from './config.js';
 import { generateCommands, CommandAdapterRegistry, } from './command-generation/index.js';
 import { getToolVersionStatus, getSkillTemplates, getCommandContents, generateSkillContent, getToolsWithSkillsDir, } from './shared/index.js';
 import { detectLegacyArtifacts, cleanupLegacyArtifacts, formatCleanupSummary, formatDetectionSummary, getToolsFromLegacyArtifacts, } from './legacy-cleanup.js';
@@ -22,8 +22,9 @@ import { getAvailableTools } from './available-tools.js';
 import { WORKFLOW_TO_SKILL_DIR, getCommandConfiguredTools, getConfiguredToolsForProfileSync, getToolsNeedingProfileSync, } from './profile-sync-drift.js';
 import { scanInstalledWorkflows as scanInstalledWorkflowsShared, migrateIfNeeded as migrateIfNeededShared, } from './migration.js';
 import { CLI_NAME, CLI_REPOSITORY_URL } from './branding.js';
+import { resolveLegacySpecLiveRoot } from './sdd/services/legacy-capability.service.js';
 const require = createRequire(import.meta.url);
-const { version: OPENSPEC_VERSION } = require('../../package.json');
+const { version: CODESDD_VERSION } = require('../../package.json');
 /**
  * Scans installed workflow artifacts (skills and managed commands) across all configured tools.
  * Returns the union of detected workflow IDs that match ALL_WORKFLOWS.
@@ -43,10 +44,10 @@ export class UpdateCommand {
     }
     async execute(projectPath) {
         const resolvedProjectPath = path.resolve(projectPath);
-        const openspecPath = path.join(resolvedProjectPath, OPENSPEC_DIR_NAME);
-        // 1. Check openspec directory exists
-        if (!await FileSystemUtils.directoryExists(openspecPath)) {
-            throw new Error(`No OpenSpec directory found. Run '${CLI_NAME} init' first.`);
+        const codesddPath = resolveLegacySpecLiveRoot(resolvedProjectPath);
+        // 1. Check codesdd directory exists
+        if (!await FileSystemUtils.directoryExists(codesddPath)) {
+            throw new Error(`No CodeSDD directory found. Run '${CLI_NAME} init' first.`);
         }
         // 2. Perform one-time migration if needed before any legacy upgrade generation.
         // Use detected tool directories to preserve existing opsx skills/commands.
@@ -73,7 +74,7 @@ export class UpdateCommand {
         const commandConfiguredTools = getCommandConfiguredTools(resolvedProjectPath);
         const commandConfiguredSet = new Set(commandConfiguredTools);
         const toolStatuses = configuredTools.map((toolId) => {
-            const status = getToolVersionStatus(resolvedProjectPath, toolId, OPENSPEC_VERSION);
+            const status = getToolVersionStatus(resolvedProjectPath, toolId, CODESDD_VERSION);
             if (!status.configured && commandConfiguredSet.has(toolId)) {
                 return { ...status, configured: true };
             }
@@ -131,7 +132,7 @@ export class UpdateCommand {
                         const skillFile = path.join(skillDir, 'SKILL.md');
                         // Use hyphen-based command references for OpenCode
                         const transformer = tool.value === 'opencode' ? transformToHyphenCommands : undefined;
-                        const skillContent = generateSkillContent(template, OPENSPEC_VERSION, transformer);
+                        const skillContent = generateSkillContent(template, CODESDD_VERSION, transformer);
                         await FileSystemUtils.writeFile(skillFile, skillContent);
                     }
                     removedDeselectedSkillCount += await this.removeUnselectedSkillDirs(skillsDir, desiredWorkflows);
@@ -170,7 +171,7 @@ export class UpdateCommand {
         // 11. Summary
         console.log();
         if (updatedTools.length > 0) {
-            console.log(chalk.green(`✓ Updated: ${updatedTools.join(', ')} (v${OPENSPEC_VERSION})`));
+            console.log(chalk.green(`✓ Updated: ${updatedTools.join(', ')} (v${CODESDD_VERSION})`));
         }
         if (failedTools.length > 0) {
             console.log(chalk.red(`✗ Failed: ${failedTools.map(f => `${f.name} (${f.error})`).join(', ')}`));
@@ -215,7 +216,7 @@ export class UpdateCommand {
      */
     displayUpToDateMessage(toolStatuses) {
         const toolNames = toolStatuses.map((s) => s.toolId);
-        console.log(chalk.green(`✓ All ${toolStatuses.length} tool(s) up to date (v${OPENSPEC_VERSION})`));
+        console.log(chalk.green(`✓ All ${toolStatuses.length} tool(s) up to date (v${CODESDD_VERSION})`));
         console.log(chalk.dim(`  Tools: ${toolNames.join(', ')}`));
         console.log();
         console.log(chalk.dim('Use --force to refresh files anyway.'));
@@ -228,7 +229,7 @@ export class UpdateCommand {
             const status = statusByTool.get(toolId);
             if (status?.needsUpdate) {
                 const fromVersion = status.generatedByVersion ?? 'unknown';
-                return `${status.toolId} (${fromVersion} → ${OPENSPEC_VERSION})`;
+                return `${status.toolId} (${fromVersion} → ${CODESDD_VERSION})`;
             }
             return `${toolId} (config sync)`;
         });
@@ -262,7 +263,7 @@ export class UpdateCommand {
         const profileSet = new Set(profileWorkflows);
         const extraWorkflows = installedWorkflows.filter((w) => !profileSet.has(w));
         if (extraWorkflows.length > 0) {
-            console.log(chalk.dim(`Note: ${extraWorkflows.length} extra workflows not in profile (use \`openspec config profile\` to manage)`));
+            console.log(chalk.dim(`Note: ${extraWorkflows.length} extra workflows not in profile (use \`codesdd config profile\` to manage)`));
         }
     }
     /**
@@ -366,7 +367,7 @@ export class UpdateCommand {
         return removed;
     }
     /**
-     * Detect and handle legacy OpenSpec artifacts.
+     * Detect and handle legacy CodeSDD artifacts.
      * Unlike init, update warns but continues if legacy files found in non-interactive mode.
      * Returns array of tool IDs that were newly configured during legacy upgrade.
      */
@@ -506,7 +507,7 @@ export class UpdateCommand {
                         const skillFile = path.join(skillDir, 'SKILL.md');
                         // Use hyphen-based command references for OpenCode
                         const transformer = tool.value === 'opencode' ? transformToHyphenCommands : undefined;
-                        const skillContent = generateSkillContent(template, OPENSPEC_VERSION, transformer);
+                        const skillContent = generateSkillContent(template, CODESDD_VERSION, transformer);
                         await FileSystemUtils.writeFile(skillFile, skillContent);
                     }
                 }

package/dist/core/validation/constants.d.ts

@@ -26,7 +26,7 @@ export declare const VALIDATION_MESSAGES: {
     readonly REQUIREMENT_TOO_LONG: "Requirement text is very long (>500 characters). Consider breaking it down.";
     readonly DELTA_DESCRIPTION_TOO_BRIEF: "Delta description is too brief";
     readonly DELTA_MISSING_REQUIREMENTS: "Delta should include requirements";
-    readonly GUIDE_NO_DELTAS: "No deltas found. Ensure your change has a specs/ directory with capability folders (e.g. specs/http-server/spec.md) containing .md files that use delta headers (## ADDED/MODIFIED/REMOVED/RENAMED Requirements) and that each requirement includes at least one \"#### Scenario:\" block. Tip: run \"opensdd change show <change-id> --json --deltas-only\" to inspect parsed deltas.";
+    readonly GUIDE_NO_DELTAS: "No deltas found. Ensure your change has a specs/ directory with capability folders (e.g. specs/http-server/spec.md) containing .md files that use delta headers (## ADDED/MODIFIED/REMOVED/RENAMED Requirements) and that each requirement includes at least one \"#### Scenario:\" block. Tip: run \"codesdd change show <change-id> --json --deltas-only\" to inspect parsed deltas.";
     readonly GUIDE_MISSING_SPEC_SECTIONS: "Missing required sections. Expected headers: \"## Purpose\" and \"## Requirements\". Example:\n## Purpose\n[brief purpose]\n\n## Requirements\n### Requirement: Clear requirement statement\nUsers SHALL ...\n\n#### Scenario: Descriptive name\n- **WHEN** ...\n- **THEN** ...";
     readonly GUIDE_MISSING_CHANGE_SECTIONS: "Missing required sections. Expected headers: \"## Why\" and \"## What Changes\". Ensure deltas are documented in specs/ using delta headers.";
     readonly GUIDE_SCENARIO_FORMAT: "Scenarios must use level-4 headers. Convert bullet lists into:\n#### Scenario: Short name\n- **WHEN** ...\n- **THEN** ...\n- **AND** ...";

package/dist/core/validation/constants.js

@@ -32,7 +32,7 @@ export const VALIDATION_MESSAGES = {
     DELTA_DESCRIPTION_TOO_BRIEF: 'Delta description is too brief',
     DELTA_MISSING_REQUIREMENTS: 'Delta should include requirements',
     // Guidance snippets (appended to primary messages for remediation)
-    GUIDE_NO_DELTAS: 'No deltas found. Ensure your change has a specs/ directory with capability folders (e.g. specs/http-server/spec.md) containing .md files that use delta headers (## ADDED/MODIFIED/REMOVED/RENAMED Requirements) and that each requirement includes at least one "#### Scenario:" block. Tip: run "opensdd change show <change-id> --json --deltas-only" to inspect parsed deltas.',
+    GUIDE_NO_DELTAS: 'No deltas found. Ensure your change has a specs/ directory with capability folders (e.g. specs/http-server/spec.md) containing .md files that use delta headers (## ADDED/MODIFIED/REMOVED/RENAMED Requirements) and that each requirement includes at least one "#### Scenario:" block. Tip: run "codesdd change show <change-id> --json --deltas-only" to inspect parsed deltas.',
     GUIDE_MISSING_SPEC_SECTIONS: 'Missing required sections. Expected headers: "## Purpose" and "## Requirements". Example:\n## Purpose\n[brief purpose]\n\n## Requirements\n### Requirement: Clear requirement statement\nUsers SHALL ...\n\n#### Scenario: Descriptive name\n- **WHEN** ...\n- **THEN** ...',
     GUIDE_MISSING_CHANGE_SECTIONS: 'Missing required sections. Expected headers: "## Why" and "## What Changes". Ensure deltas are documented in specs/ using delta headers.',
     GUIDE_SCENARIO_FORMAT: 'Scenarios must use level-4 headers. Convert bullet lists into:\n#### Scenario: Short name\n- **WHEN** ...\n- **THEN** ...\n- **AND** ...',

package/dist/core/view.js

@@ -4,19 +4,19 @@ import chalk from 'chalk';
 import { getTaskProgressForChange } from '../utils/task-progress.js';
 import { MarkdownParser } from './parsers/markdown-parser.js';
 import { CLI_NAME } from './branding.js';
-import { resolveOpenSpecSubpath } from './sdd/services/legacy-capability.service.js';
+import { resolveLegacySpecSubpath } from './sdd/services/legacy-capability.service.js';
 export class ViewCommand {
     async execute(targetPath = '.') {
-        const openspecDir = resolveOpenSpecSubpath(targetPath);
-        if (!fs.existsSync(openspecDir)) {
-            console.error(chalk.red('No openspec directory found'));
+        const codesddDir = resolveLegacySpecSubpath(targetPath);
+        if (!fs.existsSync(codesddDir)) {
+            console.error(chalk.red('No codesdd directory found'));
             process.exit(1);
         }
-        console.log(chalk.bold('\nOpenSpec Dashboard\n'));
+        console.log(chalk.bold('\nCodeSDD Dashboard\n'));
         console.log('═'.repeat(60));
         // Get changes and specs data
-        const changesData = await this.getChangesData(openspecDir);
-        const specsData = await this.getSpecsData(openspecDir);
+        const changesData = await this.getChangesData(codesddDir);
+        const specsData = await this.getSpecsData(codesddDir);
         // Display summary metrics
         this.displaySummary(changesData, specsData);
         // Display draft changes
@@ -61,8 +61,8 @@ export class ViewCommand {
         console.log('\n' + '═'.repeat(60));
         console.log(chalk.dim(`\nUse ${chalk.white(`${CLI_NAME} list --changes`)} or ${chalk.white(`${CLI_NAME} list --specs`)} for detailed views`));
     }
-    async getChangesData(openspecDir) {
-        const changesDir = path.join(openspecDir, 'changes');
+    async getChangesData(codesddDir) {
+        const changesDir = path.join(codesddDir, 'changes');
         if (!fs.existsSync(changesDir)) {
             return { draft: [], active: [], completed: [] };
         }
@@ -102,8 +102,8 @@ export class ViewCommand {
         completed.sort((a, b) => a.name.localeCompare(b.name));
         return { draft, active, completed };
     }
-    async getSpecsData(openspecDir) {
-        const specsDir = path.join(openspecDir, 'specs');
+    async getSpecsData(codesddDir) {
+        const specsDir = path.join(codesddDir, 'specs');
         if (!fs.existsSync(specsDir)) {
             return [];
         }

package/dist/domains/sdd/index.d.ts

@@ -0,0 +1,6 @@
+export { buildFeatureTitle, computeCanonicalTitle, markdownInsightTemplate, slugify, stripFunctionalTitlePrefixes, } from '../../core/sdd/domain/helpers.js';
+export { evaluateFeatureFinalizeGuardrails, evaluateFeatureStartGuardrails, type FeatureFinalizeGuardrails, type FeatureStartGuardrails, type LifecycleDependencyCheck, type LifecycleLockCheck, } from '../../core/sdd/domain/lifecycle-guardrails.js';
+export { clearLifecycleHooks, registerLifecycleHook, runLifecycleHooks, unregisterLifecycleHook, type LifecycleHook, type LifecycleHookContext, type LifecycleHookEvent, } from '../../core/sdd/domain/lifecycle-hooks.js';
+export { TransitionEngine, type EntityStatus } from '../../core/sdd/domain/transition-engine.js';
+export { evaluateWorkspaceTraceability } from '../../core/sdd/domain/traceability.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/domains/sdd/index.js

@@ -0,0 +1,6 @@
+export { buildFeatureTitle, computeCanonicalTitle, markdownInsightTemplate, slugify, stripFunctionalTitlePrefixes, } from '../../core/sdd/domain/helpers.js';
+export { evaluateFeatureFinalizeGuardrails, evaluateFeatureStartGuardrails, } from '../../core/sdd/domain/lifecycle-guardrails.js';
+export { clearLifecycleHooks, registerLifecycleHook, runLifecycleHooks, unregisterLifecycleHook, } from '../../core/sdd/domain/lifecycle-hooks.js';
+export { TransitionEngine } from '../../core/sdd/domain/transition-engine.js';
+export { evaluateWorkspaceTraceability } from '../../core/sdd/domain/traceability.js';
+//# sourceMappingURL=index.js.map