synarcx 0.2.0 → 0.2.1

package/dist/core/templates/types.js

@@ -1,5 +1,13 @@
 /**
  * Core template types for skills and slash commands.
  */
-export {};
+export function commandFromSkill(skill, overrides) {
+    return {
+        name: overrides.name ?? skill.name,
+        description: overrides.description ?? skill.description,
+        category: overrides.category ?? 'Workflow',
+        tags: overrides.tags ?? ['synarcx', skill.name.replace('syn-', '')],
+        content: overrides.content,
+    };
+}
 //# sourceMappingURL=types.js.map

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

@@ -1,48 +1,49 @@
+import { commandFromSkill } from '../types.js';
 export function getSynAnalyzeSkillTemplate() {
     return {
         name: 'syn-analyze',
         description: 'Cross-artifact consistency check across proposal, specs, design, and tasks. Edits in place to fix inconsistencies.',
-        instructions: `Run a cross-artifact consistency check for a change. Edits artifacts in place to fix issues found.
-
----
-
-## Steps
-
-1. **Identify the change**
-   - If the user specified a change name, use it
-   - Otherwise, run \`synarcx list --json\` to find active changes
-   - If multiple, ask which one to analyze
-
-2. **Read all artifacts**
-   - \`synspec/changes/<name>/proposal.md\`
-   - \`synspec/changes/<name>/specs/**/*.md\`
-   - \`synspec/changes/<name>/design.md\`
-   - \`synspec/changes/<name>/tasks.md\`
-
-3. **Run consistency checks**
-
-   a. **Terminology consistency** — same terms used across all artifacts
-   b. **Scope alignment** — proposal scope matches design and tasks
-   c. **Completeness** — no missing sections or dangling references
-   d. **Conflict detection** — contradictory statements between artifacts
-   e. **Traceability** — every task maps to a spec requirement
-
-4. **Fix inconsistencies in place**
-   - Edit artifacts directly to resolve issues
-   - Maximum 5 edits per session
-   - Show what was changed and why
-
-5. **Generate summary** of changes made
-
----
-
-## Output
-
-After completing, summarize:
-- What was checked
-- What inconsistencies were found and fixed
-- What artifacts were modified
-- Any remaining concerns
+        instructions: `Run a cross-artifact consistency check for a change. Edits artifacts in place to fix issues found.
+
+---
+
+## Steps
+
+1. **Identify the change**
+   - If the user specified a change name, use it
+   - Otherwise, run \`synarcx list --json\` to find active changes
+   - If multiple, ask which one to analyze
+
+2. **Read all artifacts**
+   - \`synspec/changes/<name>/proposal.md\`
+   - \`synspec/changes/<name>/specs/**/*.md\`
+   - \`synspec/changes/<name>/design.md\`
+   - \`synspec/changes/<name>/tasks.md\`
+
+3. **Run consistency checks**
+
+   a. **Terminology consistency** — same terms used across all artifacts
+   b. **Scope alignment** — proposal scope matches design and tasks
+   c. **Completeness** — no missing sections or dangling references
+   d. **Conflict detection** — contradictory statements between artifacts
+   e. **Traceability** — every task maps to a spec requirement
+
+4. **Fix inconsistencies in place**
+   - Edit artifacts directly to resolve issues
+   - Maximum 5 edits per session
+   - Show what was changed and why
+
+5. **Generate summary** of changes made
+
+---
+
+## Output
+
+After completing, summarize:
+- What was checked
+- What inconsistencies were found and fixed
+- What artifacts were modified
+- Any remaining concerns
 - Next step: Run \`/syn:apply\` to start implementation`,
         license: 'MIT',
         compatibility: 'Requires synarcx CLI.',
@@ -50,52 +51,51 @@ After completing, summarize:
     };
 }
 export function getSynAnalyzeCommandTemplate() {
-    return {
+    return commandFromSkill(getSynAnalyzeSkillTemplate(), {
         name: 'syn:analyze',
         description: 'Cross-artifact consistency check for proposal, specs, design, and tasks',
-        category: 'Workflow',
         tags: ['workflow', 'analyze'],
-        content: `Run a cross-artifact consistency check for a change. Edits artifacts in place to fix issues found.
-
----
-
-## Steps
-
-1. **Identify the change**
-   - If the user specified a change name, use it
-   - Otherwise, run \`synarcx list --json\` to find active changes
-   - If multiple, ask which one to analyze
-
-2. **Read all artifacts**
-   - \`synspec/changes/<name>/proposal.md\`
-   - \`synspec/changes/<name>/specs/**/*.md\`
-   - \`synspec/changes/<name>/design.md\`
-   - \`synspec/changes/<name>/tasks.md\`
-
-3. **Run consistency checks**
-   - **Terminology consistency** — same terms across all artifacts
-   - **Scope alignment** — proposal scope matches design and tasks
-   - **Completeness** — no missing sections or dangling references
-   - **Conflict detection** — contradictory statements between artifacts
-   - **Traceability** — every task maps to a spec requirement
-
-4. **Fix inconsistencies in place**
-   - Edit artifacts directly to resolve issues
-   - Maximum 5 edits per session
-   - Show what was changed and why
-
-5. **Generate summary** of changes made
-
----
-
-## Output
-
-After completing, summarize:
-- What was checked
-- What inconsistencies were found and fixed
-- What artifacts were modified
-- Any remaining concerns
+        content: `Run a cross-artifact consistency check for a change. Edits artifacts in place to fix issues found.
+
+---
+
+## Steps
+
+1. **Identify the change**
+   - If the user specified a change name, use it
+   - Otherwise, run \`synarcx list --json\` to find active changes
+   - If multiple, ask which one to analyze
+
+2. **Read all artifacts**
+   - \`synspec/changes/<name>/proposal.md\`
+   - \`synspec/changes/<name>/specs/**/*.md\`
+   - \`synspec/changes/<name>/design.md\`
+   - \`synspec/changes/<name>/tasks.md\`
+
+3. **Run consistency checks**
+   - **Terminology consistency** — same terms across all artifacts
+   - **Scope alignment** — proposal scope matches design and tasks
+   - **Completeness** — no missing sections or dangling references
+   - **Conflict detection** — contradictory statements between artifacts
+   - **Traceability** — every task maps to a spec requirement
+
+4. **Fix inconsistencies in place**
+   - Edit artifacts directly to resolve issues
+   - Maximum 5 edits per session
+   - Show what was changed and why
+
+5. **Generate summary** of changes made
+
+---
+
+## Output
+
+After completing, summarize:
+- What was checked
+- What inconsistencies were found and fixed
+- What artifacts were modified
+- Any remaining concerns
 - Next step: Run \`/syn:apply\` to start implementation`
-    };
+    });
 }
 //# sourceMappingURL=analyze.js.map