synarcx 0.1.0

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

@@ -0,0 +1,216 @@
+export function getSynProposeSkillTemplate() {
+    return {
+        name: 'syn-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.
+
+I'll create a change with artifacts:
+- proposal.md (what & why)
+- design.md (how)
+- tasks.md (implementation steps)
+
+When ready to refine, run /syn:clarify — or skip to implementation with /syn:apply
+
+---
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+   > "What change do you want to work on? Describe what you want to build or fix."
+
+   From their description, derive a kebab-case name (e.g., "add user authentication" → \`add-user-auth\`).
+
+   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+   \`\`\`bash
+   synarcx new change "<name>"
+   \`\`\`
+   This creates a scaffolded change at \`synspec/changes/<name>/\` with \`.synspec.yaml\`.
+
+3. **Get the artifact build order**
+   \`\`\`bash
+   synarcx status --change "<name>" --json
+   \`\`\`
+   Parse the JSON to get:
+   - \`applyRequires\`: array of artifact IDs needed before implementation (e.g., \`["tasks"]\`)
+   - \`artifacts\`: list of all artifacts with their status and dependencies
+
+4. **Create artifacts in sequence until apply-ready**
+
+   Use the **TodoWrite tool** to track progress through the artifacts.
+
+   Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+   a. **For each artifact that is \`ready\` (dependencies satisfied)**:
+      - Get instructions:
+        \`\`\`bash
+        synarcx instructions <artifact-id> --change "<name>" --json
+        \`\`\`
+      - The instructions JSON includes:
+        - \`context\`: Project background (constraints for you - do NOT include in output)
+        - \`rules\`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - \`template\`: The structure to use for your output file
+        - \`instruction\`: Schema-specific guidance for this artifact type
+        - \`outputPath\`: Where to write the artifact
+        - \`dependencies\`: Completed artifacts to read for context
+      - Read any completed dependency files for context
+      - Create the artifact file using \`template\` as the structure
+      - Apply \`context\` and \`rules\` as constraints - but do NOT copy them into the file
+      - Show brief progress: "Created <artifact-id>"
+
+   b. **Continue until all \`applyRequires\` artifacts are complete**
+      - After creating each artifact, re-run \`synarcx 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
+
+   c. **If an artifact requires user input** (unclear context):
+      - Use **AskUserQuestion tool** to clarify
+      - Then continue with creation
+
+5. **Show final status**
+   \`\`\`bash
+   synarcx status --change "<name>"
+   \`\`\`
+
+**Output**
+
+After completing all artifacts, summarize:
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for refinement."
+- Prompt: "Run \`/syn:clarify\` to refine the artifacts, or \`/syn:apply\` to start implementation."
+
+**Artifact Creation Guidelines**
+
+- Follow the \`instruction\` field from \`synarcx 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
+- **IMPORTANT**: \`context\` and \`rules\` are constraints for YOU, not content for the file
+  - Do NOT copy \`<context>\`, \`<rules>\`, \`<project_context>\` blocks into the artifact
+  - These guide what you write, but should never appear in the output
+
+**Guardrails**
+- Create ALL artifacts needed for implementation (as defined by schema's \`apply.requires\`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- 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 synarcx CLI.',
+        metadata: { author: 'synarcx', version: '1.0' },
+    };
+}
+export function getSynProposeCommandTemplate() {
+    return {
+        name: 'syn:propose',
+        description: 'Propose a new change - create it and generate all artifacts in one step',
+        category: 'Workflow',
+        tags: ['workflow', 'artifacts', 'experimental'],
+        content: `Propose a new change - create the change and generate all artifacts in one step.
+
+I'll create a change with artifacts:
+- proposal.md (what & why)
+- design.md (how)
+- tasks.md (implementation steps)
+
+When ready to refine, run /syn:clarify — or skip to implementation with /syn:apply
+
+---
+
+**Input**: The argument after \`/syn:propose\` is the change name (kebab-case), OR a description of what the user wants to build.
+
+**Steps**
+
+1. **If no input provided, ask what they want to build**
+
+   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+   > "What change do you want to work on? Describe what you want to build or fix."
+
+   From their description, derive a kebab-case name (e.g., "add user authentication" → \`add-user-auth\`).
+
+   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+   \`\`\`bash
+   synarcx new change "<name>"
+   \`\`\`
+   This creates a scaffolded change at \`synspec/changes/<name>/\` with \`.synspec.yaml\`.
+
+3. **Get the artifact build order**
+   \`\`\`bash
+   synarcx status --change "<name>" --json
+   \`\`\`
+   Parse the JSON to get:
+   - \`applyRequires\`: array of artifact IDs needed before implementation (e.g., \`["tasks"]\`)
+   - \`artifacts\`: list of all artifacts with their status and dependencies
+
+4. **Create artifacts in sequence until apply-ready**
+
+   Use the **TodoWrite tool** to track progress through the artifacts.
+
+   Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+   a. **For each artifact that is \`ready\` (dependencies satisfied)**:
+      - Get instructions:
+        \`\`\`bash
+        synarcx instructions <artifact-id> --change "<name>" --json
+        \`\`\`
+      - The instructions JSON includes:
+        - \`context\`: Project background (constraints for you - do NOT include in output)
+        - \`rules\`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - \`template\`: The structure to use for your output file
+        - \`instruction\`: Schema-specific guidance for this artifact type
+        - \`outputPath\`: Where to write the artifact
+        - \`dependencies\`: Completed artifacts to read for context
+      - Read any completed dependency files for context
+      - Create the artifact file using \`template\` as the structure
+      - Apply \`context\` and \`rules\` as constraints - but do NOT copy them into the file
+      - Show brief progress: "Created <artifact-id>"
+
+   b. **Continue until all \`applyRequires\` artifacts are complete**
+      - After creating each artifact, re-run \`synarcx 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
+
+   c. **If an artifact requires user input** (unclear context):
+      - Use **AskUserQuestion tool** to clarify
+      - Then continue with creation
+
+5. **Show final status**
+   \`\`\`bash
+   synarcx status --change "<name>"
+   \`\`\`
+
+**Output**
+
+After completing all artifacts, summarize:
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for refinement."
+- Prompt: "Run \`/syn:clarify\` to refine the artifacts, or \`/syn:apply\` to start implementation."
+
+**Artifact Creation Guidelines**
+
+- Follow the \`instruction\` field from \`synarcx 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
+- **IMPORTANT**: \`context\` and \`rules\` are constraints for YOU, not content for the file
+  - Do NOT copy \`<context>\`, \`<rules>\`, \`<project_context>\` blocks into the artifact
+  - These guide what you write, but should never appear in the output
+
+**Guardrails**
+- Create ALL artifacts needed for implementation (as defined by schema's \`apply.requires\`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- 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`
+    };
+}
+//# sourceMappingURL=propose.js.map

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

@@ -0,0 +1,4 @@
+import type { SkillTemplate, CommandTemplate } from '../types.js';
+export declare function getSynSyncSkillTemplate(): SkillTemplate;
+export declare function getSynSyncCommandTemplate(): CommandTemplate;
+//# sourceMappingURL=sync.d.ts.map

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

@@ -0,0 +1,108 @@
+export function getSynSyncSkillTemplate() {
+    return {
+        name: 'syn-sync',
+        description: 'Auto-generate or update synspec/constitution.md from project files (README, AGENTS.md, package.json, src structure) with semver versioning and Sync Impact Report.',
+        instructions: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures the project's purpose, principles, tech stack, conventions, architecture, and decision log.
+
+**Input**: The user can specify a description of what to focus on, or just run the command to regenerate from sources.
+
+---
+
+## First Run
+
+1. **Read project sources**
+   - \`README.md\` — project description, features, purpose
+   - \`AGENTS.md\` — AI agent conventions
+   - \`package.json\` — dependencies, scripts, metadata
+   - \`src/\` structure — code organization (top-level directories)
+
+2. **Generate \`synspec/constitution.md\`** with these sections:
+   - \`# Constitution: <project-name>\` — derived from package.json name
+   - \`Version: 0.1.0\`
+   - \`## Purpose\` — 2-3 sentences from README
+   - \`## Principles\` — key design principles inferred from codebase
+   - \`## Tech Stack\` — languages, frameworks, key dependencies
+   - \`## Conventions\` — code style, naming, patterns observed
+   - \`## Architecture\` — high-level structure overview
+   - \`## Decision Log\` — table with Date, Decision, Rationale
+
+3. **Verify** the file was created at \`synspec/constitution.md\`
+
+---
+
+## Re-run (Update)
+
+When re-run, 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, and note the version.`,
+        license: 'MIT',
+        compatibility: 'Requires synarcx CLI.',
+        metadata: { author: 'synarcx', version: '0.1' },
+    };
+}
+export function getSynSyncCommandTemplate() {
+    return {
+        name: 'syn:sync',
+        description: 'Auto-generate or update synspec/constitution.md from project files',
+        category: 'Workflow',
+        tags: ['workflow', 'sync', 'project'],
+        content: `Generate or update the project constitution — a living document in \`synspec/constitution.md\` that captures the project's purpose, principles, tech stack, conventions, architecture, and decision log.
+
+**Input**: The user can specify a description of what to focus on, or just run the command to regenerate from sources.
+
+---
+
+## First Run
+
+1. **Read project sources**
+   - \`README.md\` — project description, features, purpose
+   - \`AGENTS.md\` — AI agent conventions
+   - \`package.json\` — dependencies, scripts, metadata
+   - \`src/\` structure — code organization (top-level directories)
+
+2. **Generate \`synspec/constitution.md\`** with these sections:
+   - \`# Constitution: <project-name>\` — derived from package.json name
+   - \`Version: 0.1.0\`
+   - \`## Purpose\` — 2-3 sentences from README
+   - \`## Principles\` — key design principles inferred from codebase
+   - \`## Tech Stack\` — languages, frameworks, key dependencies
+   - \`## Conventions\` — code style, naming, patterns observed
+   - \`## Architecture\` — high-level structure overview
+   - \`## Decision Log\` — table with Date, Decision, Rationale
+
+3. **Verify** the file was created at \`synspec/constitution.md\`
+
+---
+
+## Re-run (Update)
+
+When re-run, 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, and note the version.`
+    };
+}
+//# sourceMappingURL=sync.js.map

package/dist/core/update.d.ts

@@ -0,0 +1,82 @@
+/**
+ * Update Command
+ *
+ * Refreshes synarcx skills and commands for configured tools.
+ * Supports profile-aware updates, delivery changes, migration, and smart update detection.
+ */
+/**
+ * Options for the update command.
+ */
+export interface UpdateCommandOptions {
+    /** Force update even when tools are up to date */
+    force?: boolean;
+}
+/**
+ * Scans installed workflow artifacts (skills and managed commands) across all configured tools.
+ * Returns the union of detected workflow IDs that match ALL_WORKFLOWS.
+ *
+ * Wrapper around the shared migration module's scanInstalledWorkflows that accepts tool IDs.
+ */
+export declare function scanInstalledWorkflows(projectPath: string, toolIds: string[]): string[];
+export declare class UpdateCommand {
+    private readonly force;
+    constructor(options?: UpdateCommandOptions);
+    execute(projectPath: string): Promise<void>;
+    /**
+     * Display message when all tools are up to date.
+     */
+    private displayUpToDateMessage;
+    /**
+     * Display the update plan showing which tools need updating.
+     */
+    private displayUpdatePlan;
+    /**
+     * Detects new tool directories that aren't currently configured and displays a hint.
+     */
+    private detectNewTools;
+    /**
+     * Displays a note about extra workflows installed that aren't in the current profile.
+     */
+    private displayExtraWorkflowsNote;
+    /**
+     * Suggest opting back into core when a custom profile still matches the old
+     * pre-sync core set. Keep custom profiles user-owned; do not mutate them.
+     */
+    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.
+     * 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.
+     */
+    private handleLegacyCleanup;
+    /**
+     * Perform cleanup of legacy artifacts.
+     */
+    private performLegacyCleanup;
+    /**
+     * Upgrade legacy tools to new skills system.
+     * Returns array of tool IDs that were newly configured.
+     */
+    private upgradeLegacyTools;
+}
+//# sourceMappingURL=update.d.ts.map