Merge pull request #78 from jwm4/refactor/bugfix-commands-to-skills

refactor(bugfix): migrate commands to skills-only architecture

Author: jwm4

WORKFLOW_DEVELOPMENT_GUIDE.md

@@ -339,11 +339,8 @@ git checkout -b feature/bugfix-improvements
 # Edit the workflow configuration
 vim workflows/bugfix/.ambient/ambient.json
 
-# Add or modify a command
-vim workflows/bugfix/.claude/commands/diagnose.md
-
 # Add or modify a skill
-vim workflows/bugfix/.claude/skills/root-cause-analysis/SKILL.md
+vim workflows/bugfix/.claude/skills/diagnose/SKILL.md
 
 # Edit persistent context
 vim workflows/bugfix/CLAUDE.md
@@ -492,8 +489,8 @@ Claude can sometimes mix these up, especially when:
 **1. Use explicit paths:**
 
 ```text
-❌ "Create a new command for the diagnose phase"
-✅ "Create a new command at workflows/bugfix/.claude/commands/diagnose.md"
+❌ "Create a new skill for the diagnose phase"
+✅ "Create a new skill at workflows/bugfix/.claude/skills/diagnose/SKILL.md"
 ```
 
 **2. Be explicit about context:**

workflows/bugfix/.ambient/ambient.json

@@ -1,7 +1,6 @@
 {
   "name": "Fix a bug",
   "description": "Systematic workflow for analyzing, fixing, and verifying software bugs with comprehensive testing and documentation. Guides you through reproduction, root cause diagnosis, fix implementation, testing, and documentation.",
-  "systemPrompt": "You are Amber, the Ambient Code Platform's expert colleague for systematic bug resolution.\n\nYou are controlled by a workflow controller at:\n  .claude/skills/controller/SKILL.md\n\nRead it at the start of the session. It defines how to execute phases, recommend next steps, and handle transitions.\n\nWorkspace layout:\n- Controller: .claude/skills/controller/SKILL.md\n- Phase skills: .claude/skills/{name}/SKILL.md\n- Commands: .claude/commands/*.md\n- Artifacts: artifacts/bugfix/",
-  "startupPrompt": "Greet the user as Amber, their bug fix assistant. Explain that you'll guide them through systematic bug resolution: assess the report, reproduce the bug, diagnose root cause, implement the fix, test it, and document everything. Ask them to describe the bug or paste a bug report or issue URL to get started.",
-  "greeting": "Welcome to the Bug Fix workflow! I'm Amber, and I'll guide you through systematic bug resolution.\n\nPhases:\n1. Assess — Understand the bug report and propose a plan\n2. Reproduce — Confirm the bug is reproducible\n3. Diagnose — Identify the root cause\n4. Fix — Implement the solution\n5. Test — Verify the fix and add regression tests\n6. Document — Create documentation and optionally a PR\n\nTo get started, describe the bug or paste a bug report or issue URL."
+  "systemPrompt": "You are Amber, an expert colleague for systematic bug resolution.\n\nAt the start of the session, read .claude/skills/controller/SKILL.md — it defines the workflow phases, how to execute them, and how to recommend next steps.",
+  "startupPrompt": "Greet the user as Amber, their bug fix assistant. Explain that you'll guide them through systematic bug resolution: assess the report, reproduce the bug, diagnose root cause, implement the fix, test it, and document everything. Ask them to describe the bug or paste a bug report or issue URL to get started."
 }