feat: add deterministic slash commands and improved SKILL.md descriptions for Qwen CLI

Since Qwen Code CLI lacks Gemini-style lifecycle hooks (BeforeAgent/
BeforeTool), this uses custom commands as deterministic skill triggers.

Changes:
- Create 8 custom commands (.qwen/commands/): /brainstorm, /debug,
  /plan, /tdd, /review, /verify, /execute, /finish
- Broaden SKILL.md descriptions for brainstorming, writing-plans, and
  using-superpowers with semantic keywords to improve probabilistic
  model-driven activation
- Update install.sh to symlink custom commands into ~/.qwen/commands/
- Add Quick Skill Commands section to injected QWEN.md context block

Author: mhenke

.qwen/commands/brainstorm.md

@@ -0,0 +1,5 @@
+Activate the "brainstorming" skill now. You MUST read and follow the brainstorming skill workflow before doing any creative work, building, designing, or implementing.
+
+Use `/skills activate brainstorming` or read `~/.qwen/skills/brainstorming/SKILL.md` and follow it exactly.
+
+Then apply the brainstorming workflow to whatever follows this command.

.qwen/commands/debug.md

@@ -0,0 +1,5 @@
+Activate the "systematic-debugging" skill now. You MUST read and follow the systematic debugging workflow before proposing any fixes.
+
+Use `/skills activate systematic-debugging` or read `~/.qwen/skills/systematic-debugging/SKILL.md` and follow it exactly.
+
+Then apply the debugging workflow to whatever follows this command.

.qwen/commands/execute.md

@@ -0,0 +1,5 @@
+Activate the "executing-plans" skill now. You MUST read and follow the plan execution workflow with review checkpoints between tasks.
+
+Use `/skills activate executing-plans` or read `~/.qwen/skills/executing-plans/SKILL.md` and follow it exactly.
+
+Then execute the implementation plan following the skill's structured approach.

.qwen/commands/finish.md

@@ -0,0 +1,5 @@
+Activate the "finishing-a-development-branch" skill now. You MUST read and follow the branch completion workflow before merging or creating PRs.
+
+Use `/skills activate finishing-a-development-branch` or read `~/.qwen/skills/finishing-a-development-branch/SKILL.md` and follow it exactly.
+
+Present structured options for merge, PR, or cleanup.

.qwen/commands/plan.md

@@ -0,0 +1,5 @@
+Activate the "writing-plans" skill now. You MUST read and follow the planning workflow before touching any code.
+
+Use `/skills activate writing-plans` or read `~/.qwen/skills/writing-plans/SKILL.md` and follow it exactly.
+
+Then apply the planning workflow to whatever follows this command.

.qwen/commands/review.md

@@ -0,0 +1,5 @@
+Activate the "requesting-code-review" skill now. You MUST read and follow the code review workflow to verify work meets requirements.
+
+Use `/skills activate requesting-code-review` or read `~/.qwen/skills/requesting-code-review/SKILL.md` and follow it exactly.
+
+Then apply the code review workflow to whatever follows this command.

.qwen/commands/tdd.md

@@ -0,0 +1,5 @@
+Activate the "test-driven-development" skill now. You MUST read and follow the TDD workflow: write test first, watch it fail, write minimal code to pass, refactor.
+
+Use `/skills activate test-driven-development` or read `~/.qwen/skills/test-driven-development/SKILL.md` and follow it exactly.
+
+Then apply the TDD workflow to whatever follows this command.

.qwen/commands/verify.md

@@ -0,0 +1,5 @@
+Activate the "verification-before-completion" skill now. You MUST verify your work is complete and correct BEFORE committing, pushing, or claiming success.
+
+Use `/skills activate verification-before-completion` or read `~/.qwen/skills/verification-before-completion/SKILL.md` and follow it exactly.
+
+Run all verification steps and confirm output before making any success claims. Evidence before assertions, always.

.qwen/install.sh

@@ -171,6 +171,50 @@ else
 fi
 
 
+# --- Link custom commands (deterministic skill triggers) ---
+COMMANDS_DIR="$QWEN_DIR/commands"
+REPO_COMMANDS_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/commands"
+
+mkdir -p "$COMMANDS_DIR"
+
+if [ -d "$REPO_COMMANDS_DIR" ]; then
+    echo "Linking custom commands from $REPO_COMMANDS_DIR to $COMMANDS_DIR..."
+    for cmd_path in "$REPO_COMMANDS_DIR"/*.md; do
+        if [ -f "$cmd_path" ]; then
+            cmd_name=$(basename "$cmd_path")
+            target_path="$COMMANDS_DIR/$cmd_name"
+
+            if [ -e "$target_path" ] || [ -L "$target_path" ]; then
+                if [ -L "$target_path" ]; then
+                    link_target="$(realpath "$target_path" 2>/dev/null || readlink "$target_path")"
+                    if [[ "$link_target" == "$REPO_DIR"* ]]; then
+                        rm "$target_path"
+                    else
+                        echo "  ⚠ $cmd_name points to $link_target (not this repo). Skipping."
+                        continue
+                    fi
+                else
+                    echo "  ⚠ $target_path exists and is not a symlink. Skipping."
+                    continue
+                fi
+            fi
+
+            if ln -sr "$cmd_path" "$target_path" 2>/dev/null; then
+                :
+            elif command -v python3 >/dev/null 2>&1; then
+                rel_path="$(python3 -c "import os,sys; print(os.path.relpath(sys.argv[1], sys.argv[2]))" "$cmd_path" "$COMMANDS_DIR")"
+                ln -s "$rel_path" "$target_path"
+            else
+                echo "  ⚠ Warning: Neither GNU ln -sr nor python3 available. Using absolute path (less portable)."
+                ln -s "$cmd_path" "$target_path"
+            fi
+            echo "  ✓ /${cmd_name%.md}"
+        fi
+    done
+else
+    echo "No commands directory found at $REPO_COMMANDS_DIR, skipping command linking."
+fi
+
 # --- Context injection into QWEN.md ---
 CONTEXT_HEADER="<!-- SUPERPOWERS-CONTEXT-START -->"
 CONTEXT_FOOTER="<!-- SUPERPOWERS-CONTEXT-END -->"
@@ -196,6 +240,17 @@ The skills were originally written for Claude Code. Interpret as follows:
 - Search → `search_file_content` or `glob`
 - Shell → `run_shell_command`
 - Web fetch → `web_fetch`
+
+## Quick Skill Commands
+These slash commands deterministically activate specific skills:
+- `/brainstorm` — brainstorming (design before implementation)
+- `/debug` — systematic debugging
+- `/plan` — write implementation plans
+- `/tdd` — test-driven development
+- `/review` — request code review
+- `/verify` — verification before completion
+- `/execute` — execute an implementation plan
+- `/finish` — finish a development branch
 <!-- SUPERPOWERS-CONTEXT-END -->
 EOM
 

skills/brainstorming/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brainstorming
-description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
+description: "Designs, plans, and brainstorms new apps, features, and components. You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
 ---
 
 # Brainstorming Ideas Into Designs