synarcx 0.2.0 → 0.2.1

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

@@ -1,90 +1,91 @@
+import { commandFromSkill } from '../types.js';
 export function getSynRefactorSkillTemplate() {
     return {
         name: 'syn-refactor',
         description: 'Investigate structural changes that must not alter behavior. Entry point for refactoring — explores, then hands off to /syn:propose.',
-        instructions: `Investigate a structural refactoring opportunity. Focuses on improving code structure without changing observable behavior. When thinking is clear, explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts.
-
-**Input**: The user can describe what they want to restructure, or just run the command to start exploring.
-
----
-
-## Initial Context
-
-Check for existing context:
-\`\`\`bash
-synarcx list --json
-\`\`\`
-
-If a relevant change exists, read its artifacts. Otherwise, start fresh.
-
----
-
-## Reframing the Problem
-
-This is a structural-change investigation. The goal is to improve code organization, reduce duplication, increase cohesion, or decrease coupling — without changing what the system does.
-
-### Opening Question
-
-Start by asking (use AskUserQuestion tool, open-ended):
-> "What part of the codebase feels like it needs restructuring?"
-
-Let the user describe the pain point before diving in.
-
----
-
-## Investigation
-
-Explore the codebase to understand the current structure:
-
-1. **Map the current shape** — read relevant source files, identify:
-   - Module boundaries and responsibilities
-   - Dependency direction
-   - Code duplication or overlapping concerns
-   - Testing patterns
-
-2. **Identify the target shape** — work with the user to define:
-   - What the ideal structure would look like
-   - Which modules or files move where
-   - How dependencies should flow
-
-3. **Surface risks** — flag areas of concern:
-   - Implicit dependencies that aren't visible in imports
-   - Areas where refactoring could make things worse
-   - Testing hazards (brittle tests, high coupling to internals)
-
-4. **Visualize** — use ASCII diagrams to show:
-   - Current vs. target module structure
-   - Dependency direction changes
-   - File/move relationships
-
----
-
-## Analyze-Gate Note (for the /syn:analyze phase)
-
-When a proposal is created from this investigation, the analyze phase MUST check:
-- Does the proposed change alter any public API signature?
-- Does it change output format, error messages, or user-facing behavior?
-- Does it add new functionality beyond what existed?
-
-If any of these is true → flag as a **behavior contract violation** and suggest reclassifying as a feature (not a refactor).
-
----
-
-## Hand-Off
-
-When the investigation reaches a clear conclusion, present findings and explicitly prompt:
-
-\`\`\`
-### Refactoring Plan
-
-**Current Shape**: <summary of current structure>
-**Target Shape**: <proposed structure>
-**Key Changes**: <list of structural moves>
-**Risks**: <potential issues>
-
-**Ready to formalize?** Run \`/syn:propose\` to create a change with these findings.
-\`\`\`
-
+        instructions: `Investigate a structural refactoring opportunity. Focuses on improving code structure without changing observable behavior. When thinking is clear, explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts.
+
+**Input**: The user can describe what they want to restructure, or just run the command to start exploring.
+
+---
+
+## Initial Context
+
+Check for existing context:
+\`\`\`bash
+synarcx list --json
+\`\`\`
+
+If a relevant change exists, read its artifacts. Otherwise, start fresh.
+
+---
+
+## Reframing the Problem
+
+This is a structural-change investigation. The goal is to improve code organization, reduce duplication, increase cohesion, or decrease coupling — without changing what the system does.
+
+### Opening Question
+
+Start by asking (use AskUserQuestion tool, open-ended):
+> "What part of the codebase feels like it needs restructuring?"
+
+Let the user describe the pain point before diving in.
+
+---
+
+## Investigation
+
+Explore the codebase to understand the current structure:
+
+1. **Map the current shape** — read relevant source files, identify:
+   - Module boundaries and responsibilities
+   - Dependency direction
+   - Code duplication or overlapping concerns
+   - Testing patterns
+
+2. **Identify the target shape** — work with the user to define:
+   - What the ideal structure would look like
+   - Which modules or files move where
+   - How dependencies should flow
+
+3. **Surface risks** — flag areas of concern:
+   - Implicit dependencies that aren't visible in imports
+   - Areas where refactoring could make things worse
+   - Testing hazards (brittle tests, high coupling to internals)
+
+4. **Visualize** — use ASCII diagrams to show:
+   - Current vs. target module structure
+   - Dependency direction changes
+   - File/move relationships
+
+---
+
+## Analyze-Gate Note (for the /syn:analyze phase)
+
+When a proposal is created from this investigation, the analyze phase MUST check:
+- Does the proposed change alter any public API signature?
+- Does it change output format, error messages, or user-facing behavior?
+- Does it add new functionality beyond what existed?
+
+If any of these is true → flag as a **behavior contract violation** and suggest reclassifying as a feature (not a refactor).
+
+---
+
+## Hand-Off
+
+When the investigation reaches a clear conclusion, present findings and explicitly prompt:
+
+\`\`\`
+### Refactoring Plan
+
+**Current Shape**: <summary of current structure>
+**Target Shape**: <proposed structure>
+**Key Changes**: <list of structural moves>
+**Risks**: <potential issues>
+
+**Ready to formalize?** Run \`/syn:propose\` to create a change with these findings.
+\`\`\`
+
 Do NOT create any artifacts or start the pipeline. The user must explicitly run \`/syn:propose\`.`,
         license: 'MIT',
         compatibility: 'Requires synarcx CLI.',
@@ -92,35 +93,34 @@ Do NOT create any artifacts or start the pipeline. The user must explicitly run
     };
 }
 export function getSynRefactorCommandTemplate() {
-    return {
+    return commandFromSkill(getSynRefactorSkillTemplate(), {
         name: 'syn:refactor',
         description: 'Investigate structural refactoring — map current vs. target shape, then hands off to /syn:propose',
-        category: 'Workflow',
         tags: ['workflow', 'refactor', 'restructure'],
-        content: `Investigate a structural refactoring opportunity. Focuses on improving code structure without changing observable behavior. When thinking is clear, explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts.
-
-**Input**: The argument after \`/syn:refactor\` describes what the user wants to restructure.
-
----
-
-## Investigation
-
-1. **Map the current shape** — read relevant source files, identify module boundaries, dependencies, duplication.
-2. **Identify the target shape** — define what the ideal structure looks like.
-3. **Surface risks** — flag implicit dependencies, testing hazards, areas that could get worse.
-4. **Visualize** — use ASCII diagrams to show current vs. target structure.
-
----
-
-## Analyze-Gate Note
-
-When artifacts are created, the analyze phase MUST check for behavior contract violations — no public API changes, no output format changes, no new functionality. If violated, flag and suggest reclassifying as a feature.
-
----
-
-## Hand-Off
-
+        content: `Investigate a structural refactoring opportunity. Focuses on improving code structure without changing observable behavior. When thinking is clear, explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts.
+
+**Input**: The argument after \`/syn:refactor\` describes what the user wants to restructure.
+
+---
+
+## Investigation
+
+1. **Map the current shape** — read relevant source files, identify module boundaries, dependencies, duplication.
+2. **Identify the target shape** — define what the ideal structure looks like.
+3. **Surface risks** — flag implicit dependencies, testing hazards, areas that could get worse.
+4. **Visualize** — use ASCII diagrams to show current vs. target structure.
+
+---
+
+## Analyze-Gate Note
+
+When artifacts are created, the analyze phase MUST check for behavior contract violations — no public API changes, no output format changes, no new functionality. If violated, flag and suggest reclassifying as a feature.
+
+---
+
+## Hand-Off
+
 Present a summary with Current Shape, Target Shape, Key Changes, and Risks. Then explicitly prompt: "Ready to formalize? Run \`/syn:propose\` to create a change with these findings."`
-    };
+    });
 }
 //# sourceMappingURL=refactor.js.map

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

@@ -1,101 +1,102 @@
+import { commandFromSkill } from '../types.js';
 export function getSynSyncSkillTemplate() {
     return {
         name: 'syn-sync',
         description: 'Generate or update synspec/constitution.md with README validation, supporting file scan, guardrail Q&A, and structured constitution generation.',
-        instructions: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures validated project context.
-
-**Input**: The user can specify a focus area, or just run the command to proceed through the validation flow.
-
----
-
-## README Gate (Required)
-
-Before any generation, the README MUST pass quality validation.
-
-1. **Check that README.md exists and is not empty.**
-   - If missing or blank → stop, output: "SYNC BLOCKED: README.md is missing or empty. Please write a README that describes what this project does and what problem it solves, then re-run \`/syn:sync\`."
-   - Do NOT write any files. Do NOT proceed.
-
-2. **Check that README meaningfully describes the project.**
-   - A passing README must have both:
-     - At least one sentence describing what the project does
-     - At least one sentence describing the problem it solves or who it is for
-   - AI judges quality at runtime. Examples of THIN content that should fail:
-     - Only a title and install instructions
-     - Auto-generated placeholder text ("# My Project", "## Getting Started")
-     - Single-line descriptions with no substance
-   - If README is too thin → stop, output: "SYNC BLOCKED: README is too thin. A passing README must describe (1) what the project does and (2) what problem it solves, in at least one sentence each. Please update README.md and re-run \`/syn:sync\`."
-
-3. **If README passes**, proceed to the next phase.
-
----
-
-## Supporting File Scan
-
-After README passes, read supporting project files for context:
-- \`AGENTS.md\` — AI agent conventions
-- \`package.json\` — dependencies, scripts, metadata
-- \`src/\` structure — code organization (top-level directories)
-- Any other notable config files (\`tsconfig.json\`, \`.eslintrc.*\`, etc.)
-
-Note what information is already well-covered by the README so guardrail questions avoid repeating it.
-
----
-
-## Guardrail Q&A
-
-Generate up to 5 targeted questions. Each question should probe areas that CANNOT be reliably inferred from code or README alone:
-
-| Topic Area | Example Question |
-|------------|-----------------|
-| Off-limits areas | "Are there any parts of the codebase AI should never modify?" |
-| Hard constraints | "Are there compliance, security, or infrastructure constraints?" |
-| Coding rules | "Are there coding conventions not obvious from the code?" |
-| Out-of-scope | "What is explicitly out of scope for this project right now?" |
-| Dependencies | "Are there any planned or pending dependency changes?" |
-
-**Rules:**
-- Adapt questions to the project's stack, structure, and domain — don't ask generic questions that don't apply
-- Skip questions already answered by the README, AGENTS.md, or other supporting files
-- Maximum 5 questions per session
-- Ask one at a time using the AskUserQuestion tool, wait for each answer
-
----
-
-## Constitution Generation
-
-With README validated, supporting files scanned, and Q&A answers collected, generate \`synspec/constitution.md\` with these sections:
-
-1. **\`# Constitution: <project-name>\`** — derived from package.json name, with Version field
-2. **\`## Purpose\`** — 2-3 sentences synthesized from README
-3. **\`## Principles\`** — key design principles inferred from codebase and Q&A
-4. **\`## Tech Stack\`** — languages, frameworks, key dependencies from package.json
-5. **\`## Constraints\`** — from Q&A answers: hard constraints, compliance, infra limits
-6. **\`## Off-Limits\`** — from Q&A answers: areas AI must not touch, out-of-scope items
-7. **\`## Conventions\`** — code style, naming, patterns observed from code and AGENTS.md
-8. **\`## Architecture\`** — high-level structure overview from src/ scan
-9. **\`## Decision Log\`** — table with Date, Decision, Rationale (append-only)
-
-**The Constraints and Off-Limits sections MUST be written from Q&A answers, not inferred from docs.**
-
----
-
-## Re-run (Update)
-
-When re-run and \`synspec/constitution.md\` already exists, still run the README gate — README may have degraded since last sync. Offer a semver bump choice:
-- **MAJOR** — constitution structure changed or reorganized
-- **MINOR** — new section added
-- **PATCH** — content update, typo fixes
-
-Append a Sync Impact Report as an HTML comment at the top:
-\`\`\`
-<!-- Sync Impact: MAJOR — constitution structure reorganized -->
-\`\`\`
-
----
-
-## Output
-
+        instructions: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures validated project context.
+
+**Input**: The user can specify a focus area, or just run the command to proceed through the validation flow.
+
+---
+
+## README Gate (Required)
+
+Before any generation, the README MUST pass quality validation.
+
+1. **Check that README.md exists and is not empty.**
+   - If missing or blank → stop, output: "SYNC BLOCKED: README.md is missing or empty. Please write a README that describes what this project does and what problem it solves, then re-run \`/syn:sync\`."
+   - Do NOT write any files. Do NOT proceed.
+
+2. **Check that README meaningfully describes the project.**
+   - A passing README must have both:
+     - At least one sentence describing what the project does
+     - At least one sentence describing the problem it solves or who it is for
+   - AI judges quality at runtime. Examples of THIN content that should fail:
+     - Only a title and install instructions
+     - Auto-generated placeholder text ("# My Project", "## Getting Started")
+     - Single-line descriptions with no substance
+   - If README is too thin → stop, output: "SYNC BLOCKED: README is too thin. A passing README must describe (1) what the project does and (2) what problem it solves, in at least one sentence each. Please update README.md and re-run \`/syn:sync\`."
+
+3. **If README passes**, proceed to the next phase.
+
+---
+
+## Supporting File Scan
+
+After README passes, read supporting project files for context:
+- \`AGENTS.md\` — AI agent conventions
+- \`package.json\` — dependencies, scripts, metadata
+- \`src/\` structure — code organization (top-level directories)
+- Any other notable config files (\`tsconfig.json\`, \`.eslintrc.*\`, etc.)
+
+Note what information is already well-covered by the README so guardrail questions avoid repeating it.
+
+---
+
+## Guardrail Q&A
+
+Generate up to 5 targeted questions. Each question should probe areas that CANNOT be reliably inferred from code or README alone:
+
+| Topic Area | Example Question |
+|------------|-----------------|
+| Off-limits areas | "Are there any parts of the codebase AI should never modify?" |
+| Hard constraints | "Are there compliance, security, or infrastructure constraints?" |
+| Coding rules | "Are there coding conventions not obvious from the code?" |
+| Out-of-scope | "What is explicitly out of scope for this project right now?" |
+| Dependencies | "Are there any planned or pending dependency changes?" |
+
+**Rules:**
+- Adapt questions to the project's stack, structure, and domain — don't ask generic questions that don't apply
+- Skip questions already answered by the README, AGENTS.md, or other supporting files
+- Maximum 5 questions per session
+- Ask one at a time using the AskUserQuestion tool, wait for each answer
+
+---
+
+## Constitution Generation
+
+With README validated, supporting files scanned, and Q&A answers collected, generate \`synspec/constitution.md\` with these sections:
+
+1. **\`# Constitution: <project-name>\`** — derived from package.json name, with Version field
+2. **\`## Purpose\`** — 2-3 sentences synthesized from README
+3. **\`## Principles\`** — key design principles inferred from codebase and Q&A
+4. **\`## Tech Stack\`** — languages, frameworks, key dependencies from package.json
+5. **\`## Constraints\`** — from Q&A answers: hard constraints, compliance, infra limits
+6. **\`## Off-Limits\`** — from Q&A answers: areas AI must not touch, out-of-scope items
+7. **\`## Conventions\`** — code style, naming, patterns observed from code and AGENTS.md
+8. **\`## Architecture\`** — high-level structure overview from src/ scan
+9. **\`## Decision Log\`** — table with Date, Decision, Rationale (append-only)
+
+**The Constraints and Off-Limits sections MUST be written from Q&A answers, not inferred from docs.**
+
+---
+
+## Re-run (Update)
+
+When re-run and \`synspec/constitution.md\` already exists, still run the README gate — README may have degraded since last sync. Offer a semver bump choice:
+- **MAJOR** — constitution structure changed or reorganized
+- **MINOR** — new section added
+- **PATCH** — content update, typo fixes
+
+Append a Sync Impact Report as an HTML comment at the top:
+\`\`\`
+<!-- Sync Impact: MAJOR — constitution structure reorganized -->
+\`\`\`
+
+---
+
+## Output
+
 After completion, summarize what was created or updated, note the version, and list how many Q&A questions were answered.`,
         license: 'MIT',
         compatibility: 'Requires synarcx CLI.',
@@ -103,63 +104,62 @@ After completion, summarize what was created or updated, note the version, and l
     };
 }
 export function getSynSyncCommandTemplate() {
-    return {
+    return commandFromSkill(getSynSyncSkillTemplate(), {
         name: 'syn:sync',
         description: 'Generate/update project constitution with README validation, guardrail Q&A, and constraint capture',
-        category: 'Workflow',
         tags: ['workflow', 'sync', 'project'],
-        content: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures validated project context.
-
-**Input**: The user can specify a focus area, or just run the command to proceed through the validation flow.
-
----
-
-## README Gate (Required)
-
-Before any generation, the README MUST pass quality validation.
-
-1. **Check that README.md exists and is not empty.**
-   - If missing or blank → stop with message explaining README must exist and describe the project.
-   - Do NOT write any files.
-
-2. **Check that README meaningfully describes the project.**
-   - A passing README must have both: (1) what the project does, (2) what problem it solves.
-   - AI judges quality at runtime.
-   - If too thin → stop with message explaining what's needed.
-
-3. **If README passes**, proceed.
-
----
-
-## Supporting File Scan
-
-Read AGENTS.md, package.json, src/ structure, and other notable config files. Note what's already covered by README to avoid redundant questions.
-
----
-
-## Guardrail Q&A
-
-Generate up to 5 targeted questions about off-limits areas, hard constraints, coding rules, out-of-scope items, and dependency plans. Adapt to the project's stack and domain. Skip questions already answered by README or supporting files.
-
----
-
-## Constitution Generation
-
-Generate \`synspec/constitution.md\` with sections: Purpose, Principles, Tech Stack, Constraints (from Q&A), Off-Limits (from Q&A), Conventions, Architecture, Decision Log.
-
-**Constraints and Off-Limits MUST come from Q&A answers, not inferred.**
-
----
-
-## Re-run (Update)
-
-Still run the README gate even when constitution exists — README may have degraded. Offer semver bump. Append Sync Impact Report HTML comment.
-
----
-
-## Output
-
+        content: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures validated project context.
+
+**Input**: The user can specify a focus area, or just run the command to proceed through the validation flow.
+
+---
+
+## README Gate (Required)
+
+Before any generation, the README MUST pass quality validation.
+
+1. **Check that README.md exists and is not empty.**
+   - If missing or blank → stop with message explaining README must exist and describe the project.
+   - Do NOT write any files.
+
+2. **Check that README meaningfully describes the project.**
+   - A passing README must have both: (1) what the project does, (2) what problem it solves.
+   - AI judges quality at runtime.
+   - If too thin → stop with message explaining what's needed.
+
+3. **If README passes**, proceed.
+
+---
+
+## Supporting File Scan
+
+Read AGENTS.md, package.json, src/ structure, and other notable config files. Note what's already covered by README to avoid redundant questions.
+
+---
+
+## Guardrail Q&A
+
+Generate up to 5 targeted questions about off-limits areas, hard constraints, coding rules, out-of-scope items, and dependency plans. Adapt to the project's stack and domain. Skip questions already answered by README or supporting files.
+
+---
+
+## Constitution Generation
+
+Generate \`synspec/constitution.md\` with sections: Purpose, Principles, Tech Stack, Constraints (from Q&A), Off-Limits (from Q&A), Conventions, Architecture, Decision Log.
+
+**Constraints and Off-Limits MUST come from Q&A answers, not inferred.**
+
+---
+
+## Re-run (Update)
+
+Still run the README gate even when constitution exists — README may have degraded. Offer semver bump. Append Sync Impact Report HTML comment.
+
+---
+
+## Output
+
 Summarize what was created/updated, note the version, and show how many Q&A questions were answered.`
-    };
+    });
 }
 //# sourceMappingURL=sync.js.map

package/dist/core/update.d.ts

@@ -44,27 +44,7 @@ export declare class UpdateCommand {
      */
     private displayOldCoreCustomProfileNote;
     /**
-     * Removes skill directories for workflows when delivery changed to commands-only.
-     * Returns the number of directories removed.
-     */
-    private removeSkillDirs;
-    /**
-     * Removes skill directories for workflows that are no longer selected in the active profile.
-     * Returns the number of directories removed.
-     */
-    private removeUnselectedSkillDirs;
-    /**
-     * Removes command files for workflows when delivery changed to skills-only.
-     * Returns the number of files removed.
-     */
-    private removeCommandFiles;
-    /**
-     * Removes command files for workflows that are no longer selected in the active profile.
-     * Returns the number of files removed.
-     */
-    private removeUnselectedCommandFiles;
-    /**
-     * Detect and handle legacy OpenSpec artifacts.
+     * Detect and handle legacy 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.
      */