@thiagodiogo/pscode 1.0.1 → 2.0.0

package/dist/cli/index.js

@@ -253,7 +253,6 @@ program
     .command('complete [change-name]')
     .description('Complete a change and update main specs')
     .option('-y, --yes', 'Skip confirmation prompts')
-    .option('--skip-specs', 'Skip spec update operations (useful for infrastructure, tooling, or doc-only changes)')
     .option('--no-validate', 'Skip validation (not recommended, requires confirmation)')
     .action(async (changeName, options) => {
     try {

package/dist/core/complete.d.ts

@@ -1,7 +1,6 @@
 export declare class CompleteCommand {
     execute(changeName?: string, options?: {
         yes?: boolean;
-        skipSpecs?: boolean;
         noValidate?: boolean;
         validate?: boolean;
     }): Promise<void>;

package/dist/core/complete.js

@@ -182,73 +182,49 @@ export class CompleteCommand {
                 console.log(`Warning: ${incompleteTasks} incomplete task(s) found. Continuing due to --yes flag.`);
             }
         }
-        // Handle spec updates unless skipSpecs flag is set
-        if (options.skipSpecs) {
-            console.log('Skipping spec updates (--skip-specs flag provided).');
-        }
-        else {
-            // Find specs to update
-            const specUpdates = await findSpecUpdates(changeDir, mainSpecsDir);
-            if (specUpdates.length > 0) {
-                console.log('\nSpecs to update:');
+        // Sync delta specs to main specs
+        const specUpdates = await findSpecUpdates(changeDir, mainSpecsDir);
+        if (specUpdates.length > 0) {
+            console.log('\nSincronizando specs...');
+            // Prepare all updates first (validation pass, no writes)
+            const prepared = [];
+            try {
                 for (const update of specUpdates) {
-                    const status = update.exists ? 'update' : 'create';
-                    const capability = path.basename(path.dirname(update.target));
-                    console.log(`  ${capability}: ${status}`);
+                    const built = await buildUpdatedSpec(update, changeName);
+                    prepared.push({ update, rebuilt: built.rebuilt, counts: built.counts });
                 }
-                let shouldUpdateSpecs = true;
-                if (!options.yes) {
-                    const { confirm } = await import('@inquirer/prompts');
-                    shouldUpdateSpecs = await confirm({
-                        message: 'Proceed with spec updates?',
-                        default: true
-                    });
-                    if (!shouldUpdateSpecs) {
-                        console.log('Skipping spec updates. Proceeding with archive.');
-                    }
-                }
-                if (shouldUpdateSpecs) {
-                    // Prepare all updates first (validation pass, no writes)
-                    const prepared = [];
-                    try {
-                        for (const update of specUpdates) {
-                            const built = await buildUpdatedSpec(update, changeName);
-                            prepared.push({ update, rebuilt: built.rebuilt, counts: built.counts });
+            }
+            catch (err) {
+                console.log(String(err.message || err));
+                console.log('Aborted. No files were changed.');
+                return;
+            }
+            // All validations passed; pre-validate rebuilt full spec and then write files and display counts
+            let totals = { added: 0, modified: 0, removed: 0, renamed: 0 };
+            for (const p of prepared) {
+                const specName = path.basename(path.dirname(p.update.target));
+                if (!skipValidation) {
+                    const report = await new Validator().validateSpecContent(specName, p.rebuilt);
+                    if (!report.valid) {
+                        console.log(chalk.red(`\nValidation errors in rebuilt spec for ${specName} (will not write changes):`));
+                        for (const issue of report.issues) {
+                            if (issue.level === 'ERROR')
+                                console.log(chalk.red(`  ✗ ${issue.message}`));
+                            else if (issue.level === 'WARNING')
+                                console.log(chalk.yellow(`  ⚠ ${issue.message}`));
                         }
-                    }
-                    catch (err) {
-                        console.log(String(err.message || err));
                         console.log('Aborted. No files were changed.');
                         return;
                     }
-                    // All validations passed; pre-validate rebuilt full spec and then write files and display counts
-                    let totals = { added: 0, modified: 0, removed: 0, renamed: 0 };
-                    for (const p of prepared) {
-                        const specName = path.basename(path.dirname(p.update.target));
-                        if (!skipValidation) {
-                            const report = await new Validator().validateSpecContent(specName, p.rebuilt);
-                            if (!report.valid) {
-                                console.log(chalk.red(`\nValidation errors in rebuilt spec for ${specName} (will not write changes):`));
-                                for (const issue of report.issues) {
-                                    if (issue.level === 'ERROR')
-                                        console.log(chalk.red(`  ✗ ${issue.message}`));
-                                    else if (issue.level === 'WARNING')
-                                        console.log(chalk.yellow(`  ⚠ ${issue.message}`));
-                                }
-                                console.log('Aborted. No files were changed.');
-                                return;
-                            }
-                        }
-                        await writeUpdatedSpec(p.update, p.rebuilt, p.counts);
-                        totals.added += p.counts.added;
-                        totals.modified += p.counts.modified;
-                        totals.removed += p.counts.removed;
-                        totals.renamed += p.counts.renamed;
-                    }
-                    console.log(`Totals: + ${totals.added}, ~ ${totals.modified}, - ${totals.removed}, → ${totals.renamed}`);
-                    console.log('Specs updated successfully.');
                 }
+                await writeUpdatedSpec(p.update, p.rebuilt, p.counts);
+                totals.added += p.counts.added;
+                totals.modified += p.counts.modified;
+                totals.removed += p.counts.removed;
+                totals.renamed += p.counts.renamed;
             }
+            console.log(`Totals: + ${totals.added}, ~ ${totals.modified}, - ${totals.removed}, → ${totals.renamed}`);
+            console.log('Specs updated successfully.');
         }
         // Create archive directory with date prefix
         const archiveName = `${this.getArchiveDate()}-${changeName}`;

package/dist/core/completions/command-registry.js

@@ -139,10 +139,6 @@ export const COMMAND_REGISTRY = [
                 short: 'y',
                 description: 'Skip confirmation prompts',
             },
-            {
-                name: 'skip-specs',
-                description: 'Skip spec update operations',
-            },
             {
                 name: 'no-validate',
                 description: 'Skip validation (not recommended)',

package/dist/core/init.js

@@ -42,7 +42,6 @@ const WORKFLOW_TO_SKILL_DIR = {
     'continue': 'pscode-continue-change',
     'apply': 'pscode-apply-change',
     'ff': 'pscode-ff-change',
-    'sync': 'pscode-sync-specs',
     'complete': 'pscode-archive-change',
     'bulk-archive': 'pscode-bulk-archive-change',
     'verify': 'pscode-verify-change',

package/dist/core/profile-sync-drift.js

@@ -13,7 +13,6 @@ export const WORKFLOW_TO_SKILL_DIR = {
     'continue': 'pscode-continue-change',
     'apply': 'pscode-apply-change',
     'ff': 'pscode-ff-change',
-    'sync': 'pscode-sync-specs',
     'complete': 'pscode-archive-change',
     'bulk-archive': 'pscode-bulk-archive-change',
     'verify': 'pscode-verify-change',

package/dist/core/profiles.d.ts

@@ -5,7 +5,7 @@
  * `pscode init --profile <name>` or `pscode config profile <name>`.
  * The workflow lists are fixed in code — users cannot customise them.
  */
-export declare const ALL_WORKFLOWS: readonly ["propose", "explore", "new", "continue", "apply", "ff", "sync", "complete", "bulk-archive", "verify", "onboard", "trello-setup", "draft", "rfc", "design", "tasks", "arch-check", "adr", "jira-sync", "dod"];
+export declare const ALL_WORKFLOWS: readonly ["propose", "explore", "new", "continue", "apply", "ff", "complete", "bulk-archive", "verify", "onboard", "trello-setup", "draft", "rfc", "design", "tasks", "arch-check", "adr", "jira-sync", "dod"];
 export type WorkflowId = (typeof ALL_WORKFLOWS)[number];
 export interface ProfileDefinition {
     description: string;
@@ -13,8 +13,8 @@ export interface ProfileDefinition {
 }
 export declare const PROFILES: {
     readonly standard: {
-        readonly description: "Padrão — propose, explore, apply, sync, complete";
-        readonly workflows: readonly ["propose", "explore", "apply", "sync", "complete"];
+        readonly description: "Padrão — propose, explore, apply, complete";
+        readonly workflows: readonly ["propose", "explore", "apply", "complete"];
     };
     readonly dixi: {
         readonly description: "Dixi — RFC→Design→Tasks→Apply com guardrails para Java/Spring e React/Next.js";

package/dist/core/profiles.js

@@ -12,7 +12,6 @@ export const ALL_WORKFLOWS = [
     'continue',
     'apply',
     'ff',
-    'sync',
     'complete',
     'bulk-archive',
     'verify',
@@ -29,8 +28,8 @@ export const ALL_WORKFLOWS = [
 ];
 export const PROFILES = {
     standard: {
-        description: 'Padrão — propose, explore, apply, sync, complete',
-        workflows: ['propose', 'explore', 'apply', 'sync', 'complete'],
+        description: 'Padrão — propose, explore, apply, complete',
+        workflows: ['propose', 'explore', 'apply', 'complete'],
     },
     dixi: {
         description: 'Dixi — RFC→Design→Tasks→Apply com guardrails para Java/Spring e React/Next.js',

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

@@ -3,7 +3,7 @@
  *
  * Shared utilities for generating skill and command files.
  */
-import { getExploreSkillTemplate, getNewChangeSkillTemplate, getContinueChangeSkillTemplate, getApplyChangeSkillTemplate, getFfChangeSkillTemplate, getSyncSpecsSkillTemplate, getCompleteChangeSkillTemplate, getBulkArchiveChangeSkillTemplate, getVerifyChangeSkillTemplate, getOnboardSkillTemplate, getProposeSkillTemplate, getTrelloSetupSkillTemplate, getTrelloDraftSkillTemplate, getPsExploreCommandTemplate, getPsNewCommandTemplate, getPsContinueCommandTemplate, getPsApplyCommandTemplate, getPsFfCommandTemplate, getPsSyncCommandTemplate, getPsCompleteCommandTemplate, getPsBulkArchiveCommandTemplate, getPsVerifyCommandTemplate, getPsOnboardCommandTemplate, getPsProposeCommandTemplate, getTrelloSetupCommandTemplate, getTrelloDraftCommandTemplate, } from '../templates/skill-templates.js';
+import { getExploreSkillTemplate, getNewChangeSkillTemplate, getContinueChangeSkillTemplate, getApplyChangeSkillTemplate, getFfChangeSkillTemplate, getCompleteChangeSkillTemplate, getBulkArchiveChangeSkillTemplate, getVerifyChangeSkillTemplate, getOnboardSkillTemplate, getProposeSkillTemplate, getTrelloSetupSkillTemplate, getTrelloDraftSkillTemplate, getPsExploreCommandTemplate, getPsNewCommandTemplate, getPsContinueCommandTemplate, getPsApplyCommandTemplate, getPsFfCommandTemplate, getPsCompleteCommandTemplate, getPsBulkArchiveCommandTemplate, getPsVerifyCommandTemplate, getPsOnboardCommandTemplate, getPsProposeCommandTemplate, getTrelloSetupCommandTemplate, getTrelloDraftCommandTemplate, } from '../templates/skill-templates.js';
 /**
  * Gets skill templates with their directory names, optionally filtered by workflow IDs.
  *
@@ -16,7 +16,6 @@ export function getSkillTemplates(workflowFilter) {
         { template: getContinueChangeSkillTemplate(), dirName: 'pscode-continue-change', workflowId: 'continue' },
         { template: getApplyChangeSkillTemplate(), dirName: 'pscode-apply-change', workflowId: 'apply' },
         { template: getFfChangeSkillTemplate(), dirName: 'pscode-ff-change', workflowId: 'ff' },
-        { template: getSyncSpecsSkillTemplate(), dirName: 'pscode-sync-specs', workflowId: 'sync' },
         { template: getCompleteChangeSkillTemplate(), dirName: 'pscode-archive-change', workflowId: 'complete' },
         { template: getBulkArchiveChangeSkillTemplate(), dirName: 'pscode-bulk-archive-change', workflowId: 'bulk-archive' },
         { template: getVerifyChangeSkillTemplate(), dirName: 'pscode-verify-change', workflowId: 'verify' },
@@ -43,7 +42,6 @@ export function getCommandTemplates(workflowFilter) {
         { template: getPsContinueCommandTemplate(), id: 'continue' },
         { template: getPsApplyCommandTemplate(), id: 'apply' },
         { template: getPsFfCommandTemplate(), id: 'ff' },
-        { template: getPsSyncCommandTemplate(), id: 'sync' },
         { template: getPsCompleteCommandTemplate(), id: 'complete' },
         { template: getPsBulkArchiveCommandTemplate(), id: 'bulk-archive' },
         { template: getPsVerifyCommandTemplate(), id: 'verify' },

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

@@ -6,12 +6,12 @@
 /**
  * Names of skill directories created by pscode init.
  */
-export declare const SKILL_NAMES: readonly ["pscode-explore", "pscode-new-change", "pscode-continue-change", "pscode-apply-change", "pscode-ff-change", "pscode-sync-specs", "pscode-archive-change", "pscode-bulk-archive-change", "pscode-verify-change", "pscode-onboard", "pscode-propose"];
+export declare const SKILL_NAMES: readonly ["pscode-explore", "pscode-new-change", "pscode-continue-change", "pscode-apply-change", "pscode-ff-change", "pscode-archive-change", "pscode-bulk-archive-change", "pscode-verify-change", "pscode-onboard", "pscode-propose"];
 export type SkillName = (typeof SKILL_NAMES)[number];
 /**
  * IDs of command templates created by pscode init.
  */
-export declare const COMMAND_IDS: readonly ["explore", "new", "continue", "apply", "ff", "sync", "complete", "bulk-archive", "verify", "onboard", "propose"];
+export declare const COMMAND_IDS: readonly ["explore", "new", "continue", "apply", "ff", "complete", "bulk-archive", "verify", "onboard", "propose"];
 export type CommandId = (typeof COMMAND_IDS)[number];
 /**
  * Status of skill configuration for a tool.

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

@@ -15,7 +15,6 @@ export const SKILL_NAMES = [
     'pscode-continue-change',
     'pscode-apply-change',
     'pscode-ff-change',
-    'pscode-sync-specs',
     'pscode-archive-change',
     'pscode-bulk-archive-change',
     'pscode-verify-change',
@@ -31,7 +30,6 @@ export const COMMAND_IDS = [
     'continue',
     'apply',
     'ff',
-    'sync',
     'complete',
     'bulk-archive',
     'verify',

package/dist/core/templates/skill-templates.d.ts

@@ -9,7 +9,6 @@ export { getNewChangeSkillTemplate, getPsNewCommandTemplate } from './workflows/
 export { getContinueChangeSkillTemplate, getPsContinueCommandTemplate } from './workflows/continue-change.js';
 export { getApplyChangeSkillTemplate, getPsApplyCommandTemplate } from './workflows/apply-change.js';
 export { getFfChangeSkillTemplate, getPsFfCommandTemplate } from './workflows/ff-change.js';
-export { getSyncSpecsSkillTemplate, getPsSyncCommandTemplate } from './workflows/sync-specs.js';
 export { getCompleteChangeSkillTemplate, getPsCompleteCommandTemplate } from './workflows/archive-change.js';
 export { getBulkArchiveChangeSkillTemplate, getPsBulkArchiveCommandTemplate } from './workflows/bulk-archive-change.js';
 export { getVerifyChangeSkillTemplate, getPsVerifyCommandTemplate } from './workflows/verify-change.js';

package/dist/core/templates/skill-templates.js

@@ -8,7 +8,6 @@ export { getNewChangeSkillTemplate, getPsNewCommandTemplate } from './workflows/
 export { getContinueChangeSkillTemplate, getPsContinueCommandTemplate } from './workflows/continue-change.js';
 export { getApplyChangeSkillTemplate, getPsApplyCommandTemplate } from './workflows/apply-change.js';
 export { getFfChangeSkillTemplate, getPsFfCommandTemplate } from './workflows/ff-change.js';
-export { getSyncSpecsSkillTemplate, getPsSyncCommandTemplate } from './workflows/sync-specs.js';
 export { getCompleteChangeSkillTemplate, getPsCompleteCommandTemplate } from './workflows/archive-change.js';
 export { getBulkArchiveChangeSkillTemplate, getPsBulkArchiveCommandTemplate } from './workflows/bulk-archive-change.js';
 export { getVerifyChangeSkillTemplate, getPsVerifyCommandTemplate } from './workflows/verify-change.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thiagodiogo/pscode",
-  "version": "1.0.1",
+  "version": "2.0.0",
   "description": "AI-native system for spec-driven development",
   "keywords": [
     "pscode",
@@ -39,24 +39,6 @@
     "!dist/**/__tests__",
     "!dist/**/*.map"
   ],
-  "scripts": {
-    "lint": "eslint src/",
-    "build": "node build.js",
-    "dev": "tsc --watch",
-    "dev:cli": "pnpm build && node bin/pscode.js",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "test:ui": "vitest --ui",
-    "test:coverage": "vitest --coverage",
-    "test:postinstall": "node scripts/postinstall.js",
-    "prepare": "pnpm run build",
-    "prepublishOnly": "pnpm run build",
-    "postinstall": "node scripts/postinstall.js",
-    "check:pack-version": "node scripts/pack-version-check.mjs",
-    "release": "pnpm run release:ci",
-    "release:ci": "pnpm run check:pack-version && pnpm exec changeset publish",
-    "changeset": "changeset"
-  },
   "engines": {
     "node": ">=20.19.0"
   },
@@ -81,5 +63,21 @@
     "posthog-node": "^5.20.0",
     "yaml": "^2.8.2",
     "zod": "^4.0.17"
+  },
+  "scripts": {
+    "lint": "eslint src/",
+    "build": "node build.js",
+    "dev": "tsc --watch",
+    "dev:cli": "pnpm build && node bin/pscode.js",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:ui": "vitest --ui",
+    "test:coverage": "vitest --coverage",
+    "test:postinstall": "node scripts/postinstall.js",
+    "postinstall": "node scripts/postinstall.js",
+    "check:pack-version": "node scripts/pack-version-check.mjs",
+    "release": "pnpm run release:ci",
+    "release:ci": "pnpm run check:pack-version && pnpm exec changeset publish",
+    "changeset": "changeset"
   }
-}
+}

package/dist/core/templates/workflows/sync-specs.d.ts

@@ -1,10 +0,0 @@
-/**
- * Skill Template Workflow Modules
- *
- * This file is generated by splitting the legacy monolithic
- * templates file into workflow-focused modules.
- */
-import type { SkillTemplate, CommandTemplate } from '../types.js';
-export declare function getSyncSpecsSkillTemplate(): SkillTemplate;
-export declare function getPsSyncCommandTemplate(): CommandTemplate;
-//# sourceMappingURL=sync-specs.d.ts.map

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

@@ -1,290 +0,0 @@
-export function getSyncSpecsSkillTemplate() {
-    return {
-        name: 'pscode-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.
-
-This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
-
-**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.
-
-**Steps**
-
-1. **If no change name provided, prompt for selection**
-
-   Run \`pscode list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
-
-   Show changes that have delta specs (under \`specs/\` directory).
-
-   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
-
-2. **Resolve change context**
-
-   Run:
-   \`\`\`bash
-   pscode status --change "<name>" --json
-   \`\`\`
-
-   If status reports \`actionContext.mode: "workspace-planning"\`, explain that workspace spec sync is not supported in this slice and STOP. Do not fall back to repo-local paths or edit linked repos.
-
-3. **Find delta specs**
-
-   Use \`artifactPaths.specs.existingOutputPaths\` from the status JSON as the list of delta spec files.
-
-   Each delta spec file contains sections like:
-   - \`## ADDED Requirements\` - New requirements to add
-   - \`## MODIFIED Requirements\` - Changes to existing requirements
-   - \`## REMOVED Requirements\` - Requirements to remove
-   - \`## RENAMED Requirements\` - Requirements to rename (FROM:/TO: format)
-
-   If no delta specs found, inform user and stop.
-
-4. **For each delta spec, apply changes to main specs**
-
-   For each repo-local capability delta spec path returned by the CLI:
-
-   a. **Read the delta spec** to understand the intended changes
-
-   b. **Read the main spec** at \`pscode/specs/<capability>/spec.md\` (may not exist yet)
-
-   c. **Apply changes intelligently**:
-
-      **ADDED Requirements:**
-      - If requirement doesn't exist in main spec → add it
-      - If requirement already exists → update it to match (treat as implicit MODIFIED)
-
-      **MODIFIED Requirements:**
-      - Find the requirement in main spec
-      - Apply the changes - this can be:
-        - Adding new scenarios (don't need to copy existing ones)
-        - Modifying existing scenarios
-        - Changing the requirement description
-      - Preserve scenarios/content not mentioned in the delta
-
-      **REMOVED Requirements:**
-      - Remove the entire requirement block from main spec
-
-      **RENAMED Requirements:**
-      - Find the FROM requirement, rename to TO
-
-   d. **Create new main spec** if capability doesn't exist yet:
-      - Create \`pscode/specs/<capability>/spec.md\`
-      - Add Purpose section (can be brief, mark as TBD)
-      - Add Requirements section with the ADDED requirements
-
-5. **Show summary**
-
-   After applying all changes, summarize:
-   - Which capabilities were updated
-   - What changes were made (requirements added/modified/removed/renamed)
-
-**Delta Spec Format Reference**
-
-\`\`\`markdown
-## ADDED Requirements
-
-### Requirement: New Feature
-The system SHALL do something new.
-
-#### Scenario: Basic case
-- **WHEN** user does X
-- **THEN** system does Y
-
-## MODIFIED Requirements
-
-### Requirement: Existing Feature
-#### Scenario: New scenario to add
-- **WHEN** user does A
-- **THEN** system does B
-
-## REMOVED Requirements
-
-### Requirement: Deprecated Feature
-
-## RENAMED Requirements
-
-- FROM: \`### Requirement: Old Name\`
-- TO: \`### Requirement: New Name\`
-\`\`\`
-
-**Key Principle: Intelligent Merging**
-
-Unlike programmatic merging, you can apply **partial updates**:
-- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
-- The delta represents *intent*, not a wholesale replacement
-- Use your judgment to merge changes sensibly
-
-**Output On Success**
-
-\`\`\`
-## Specs Synced: <change-name>
-
-Updated main specs:
-
-**<capability-1>**:
-- Added requirement: "New Feature"
-- Modified requirement: "Existing Feature" (added 1 scenario)
-
-**<capability-2>**:
-- Created new spec file
-- Added requirement: "Another Feature"
-
-Main specs are now updated. The change remains active - archive when implementation is complete.
-\`\`\`
-
-**Guardrails**
-- Read both delta and main specs before making changes
-- Preserve existing content not mentioned in delta
-- If something is unclear, ask for clarification
-- Show what you're changing as you go
-- The operation should be idempotent - running twice should give same result`,
-        license: 'MIT',
-        compatibility: 'Requires pscode CLI.',
-        metadata: { author: 'pscode', version: '1.0' },
-    };
-}
-export function getPsSyncCommandTemplate() {
-    return {
-        name: 'PS: Sync',
-        description: 'Sync delta specs from a change to main specs',
-        category: 'Workflow',
-        tags: ['workflow', 'specs', 'experimental'],
-        content: `Sync delta specs from a change to main specs.
-
-This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
-
-**Input**: Optionally specify a change name after \`/ps:sync\` (e.g., \`/ps:sync add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
-
-**Steps**
-
-1. **If no change name provided, prompt for selection**
-
-   Run \`pscode list --json\` to get available changes. Use the **AskUserQuestion tool** to let the user select.
-
-   Show changes that have delta specs (under \`specs/\` directory).
-
-   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
-
-2. **Resolve change context**
-
-   Run:
-   \`\`\`bash
-   pscode status --change "<name>" --json
-   \`\`\`
-
-   If status reports \`actionContext.mode: "workspace-planning"\`, explain that workspace spec sync is not supported in this slice and STOP. Do not fall back to repo-local paths or edit linked repos.
-
-3. **Find delta specs**
-
-   Use \`artifactPaths.specs.existingOutputPaths\` from the status JSON as the list of delta spec files.
-
-   Each delta spec file contains sections like:
-   - \`## ADDED Requirements\` - New requirements to add
-   - \`## MODIFIED Requirements\` - Changes to existing requirements
-   - \`## REMOVED Requirements\` - Requirements to remove
-   - \`## RENAMED Requirements\` - Requirements to rename (FROM:/TO: format)
-
-   If no delta specs found, inform user and stop.
-
-4. **For each delta spec, apply changes to main specs**
-
-   For each repo-local capability delta spec path returned by the CLI:
-
-   a. **Read the delta spec** to understand the intended changes
-
-   b. **Read the main spec** at \`pscode/specs/<capability>/spec.md\` (may not exist yet)
-
-   c. **Apply changes intelligently**:
-
-      **ADDED Requirements:**
-      - If requirement doesn't exist in main spec → add it
-      - If requirement already exists → update it to match (treat as implicit MODIFIED)
-
-      **MODIFIED Requirements:**
-      - Find the requirement in main spec
-      - Apply the changes - this can be:
-        - Adding new scenarios (don't need to copy existing ones)
-        - Modifying existing scenarios
-        - Changing the requirement description
-      - Preserve scenarios/content not mentioned in the delta
-
-      **REMOVED Requirements:**
-      - Remove the entire requirement block from main spec
-
-      **RENAMED Requirements:**
-      - Find the FROM requirement, rename to TO
-
-   d. **Create new main spec** if capability doesn't exist yet:
-      - Create \`pscode/specs/<capability>/spec.md\`
-      - Add Purpose section (can be brief, mark as TBD)
-      - Add Requirements section with the ADDED requirements
-
-5. **Show summary**
-
-   After applying all changes, summarize:
-   - Which capabilities were updated
-   - What changes were made (requirements added/modified/removed/renamed)
-
-**Delta Spec Format Reference**
-
-\`\`\`markdown
-## ADDED Requirements
-
-### Requirement: New Feature
-The system SHALL do something new.
-
-#### Scenario: Basic case
-- **WHEN** user does X
-- **THEN** system does Y
-
-## MODIFIED Requirements
-
-### Requirement: Existing Feature
-#### Scenario: New scenario to add
-- **WHEN** user does A
-- **THEN** system does B
-
-## REMOVED Requirements
-
-### Requirement: Deprecated Feature
-
-## RENAMED Requirements
-
-- FROM: \`### Requirement: Old Name\`
-- TO: \`### Requirement: New Name\`
-\`\`\`
-
-**Key Principle: Intelligent Merging**
-
-Unlike programmatic merging, you can apply **partial updates**:
-- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
-- The delta represents *intent*, not a wholesale replacement
-- Use your judgment to merge changes sensibly
-
-**Output On Success**
-
-\`\`\`
-## Specs Synced: <change-name>
-
-Updated main specs:
-
-**<capability-1>**:
-- Added requirement: "New Feature"
-- Modified requirement: "Existing Feature" (added 1 scenario)
-
-**<capability-2>**:
-- Created new spec file
-- Added requirement: "Another Feature"
-
-Main specs are now updated. The change remains active - archive when implementation is complete.
-\`\`\`
-
-**Guardrails**
-- Read both delta and main specs before making changes
-- Preserve existing content not mentioned in delta
-- If something is unclear, ask for clarification
-- Show what you're changing as you go
-- The operation should be idempotent - running twice should give same result`
-    };
-}
-//# sourceMappingURL=sync-specs.js.map