synarcx 0.3.1 → 0.3.2

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

@@ -71,7 +71,7 @@ export function getSynDebugCommandTemplate() {
         name: 'syn:debug',
         description: 'Investigate a known error — root cause analysis through hypothesis, explicitly prompts /syn:propose',
         tags: ['workflow', 'debug', 'fix'],
-        content: `Investigate a known error or failure systematically in 3 phases. Produces a diagnosis and suggests \`/syn:propose\` for creating the fix change.
+        content: `Investigate a known error or failure systematically in 3 phases. Produces a diagnosis and explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts or auto-hand off.
 
 **Input**: Error message, symptom, or failure description. The argument after \`/syn:debug\` is what went wrong.
 
@@ -79,7 +79,12 @@ export function getSynDebugCommandTemplate() {
 
 ## Initial Context
 
-If a change is active, read its artifacts first to understand what was intended vs. what went wrong.
+If a change is active, read its artifacts first:
+- \`synspec/changes/<name>/proposal.md\`
+- \`synspec/changes/<name>/design.md\`
+- \`synspec/changes/<name>/tasks.md\`
+
+Use that context to understand what was intended vs. what went wrong.
 
 ---
 
@@ -111,7 +116,19 @@ If a change is active, read its artifacts first to understand what was intended
 
 ## Output
 
-After completing, present the diagnosis and explicitly prompt the user to run \`/syn:propose\` to formalize the fix. Do NOT auto-create artifacts.`
+After completing the 3-phase investigation, present findings and prompt explicitly:
+
+\`\`\`
+### Diagnosis
+
+**Root Cause**: <what was found>
+**Pattern**: <similar issues or novel>
+**Hypothesis**: <proposed fix approach>
+
+**Ready to formalize?** Run \`/syn:propose\` to create a change with these findings.
+\`\`\`
+
+Do NOT create any artifacts, do NOT start the pipeline automatically. The user must explicitly run \`/syn:propose\` to formalize.`
     });
 }
 //# sourceMappingURL=debug.js.map

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

@@ -103,12 +103,52 @@ export function getSynRefactorCommandTemplate() {
 
 ---
 
+## 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
 
-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.
+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
 
 ---
 
@@ -120,7 +160,20 @@ When artifacts are created, the analyze phase MUST check for behavior contract v
 
 ## 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."`
+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\`.`
     });
 }
 //# sourceMappingURL=refactor.js.map