fix: prevent skills from loading twice when invoked via slash commands

Root Cause: Slash commands were outputting text like 'Execute: /skill analyze'
which Claude would parse and execute, but something was causing double execution.

Fix: Changed slash commands to use directive format instead:
- Old: 'Execute: /skill analyze' (text that gets re-parsed)
- New: 'Use the Skill tool with skill="analyze".' (single instruction)

This provides clear instructions for Claude to invoke the skill exactly once.

Updated all 7 slash commands:
- /stackshift.analyze
- /stackshift.reverse-engineer
- /stackshift.create-specs
- /stackshift.gap-analysis
- /stackshift.complete-spec
- /stackshift.implement
- /stackshift.cruise-control

Result: Skills should now load once instead of twice.

Author: jschulte

.claude/commands/stackshift.analyze.md

@@ -2,16 +2,8 @@
 description: Gear 1 - Analyze codebase and detect tech stack
 ---
 
-Run the analyze skill to start reverse engineering.
+Invoke the analyze skill (Gear 1 of StackShift).
 
-This is **Gear 1** of the StackShift process.
+This will detect tech stack, map directory structure, assess completeness, create analysis-report.md, and help you choose Greenfield or Brownfield route.
 
-Execute: `/skill analyze`
-
-This will:
-- Detect programming language and framework
-- Identify application type
-- Map directory structure
-- Assess completeness
-- Create analysis-report.md
-- Ask you to choose route: Greenfield or Brownfield
+Use the Skill tool with skill="analyze".

.claude/commands/stackshift.complete-spec.md

@@ -2,17 +2,10 @@
 description: Gear 5 - Resolve clarifications and complete specifications
 ---
 
-Run the complete-spec skill to resolve ambiguities.
+Invoke the complete-spec skill (Gear 5 of StackShift).
 
-This is **Gear 5** of the StackShift process.
+This resolves ambiguities by finding [NEEDS CLARIFICATION] markers, asking targeted questions, and updating specs.
 
-Execute: `/skill complete-spec`
+Prerequisite: Complete Gear 4 (gap-analysis)
 
-This will:
-- Find [NEEDS CLARIFICATION] markers
-- Ask targeted questions
-- Update specs with answers
-- Remove ambiguities
-- Prepare for implementation
-
-Prerequisites: Complete Gear 4 (gap-analysis)
+Use the Skill tool with skill="complete-spec".

.claude/commands/stackshift.create-specs.md

@@ -2,21 +2,10 @@
 description: Gear 3 - Generate GitHub Spec Kit specifications for ALL features
 ---
 
-Run the create-specs skill to automatically generate comprehensive specifications.
+Invoke the create-specs skill (Gear 3 of StackShift).
 
-This is **Gear 3** of the StackShift process.
+This automatically generates specifications for the ENTIRE application (not just gaps) - creates specs for existing features, partial features, and missing features. Achieves 100% spec coverage.
 
-Execute: `/skill create-specs`
+Prerequisite: Complete Gear 2 (reverse-engineer)
 
-This will:
-- Automatically parse functional-specification.md
-- Extract ALL features (complete, partial, missing)
-- Generate constitution.md
-- Create specs for EVERY feature (not just gaps!)
-- Create implementation plans for incomplete features
-- Set up /speckit.* slash commands
-- Achieve 100% spec coverage
-
-Prerequisites: Complete Gear 2 (reverse-engineer)
-
-**Critical**: Creates specs for existing features too, enabling spec-driven changes to current code!
+Use the Skill tool with skill="create-specs".

.claude/commands/stackshift.cruise-control.md

@@ -2,19 +2,11 @@
 description: Cruise Control - Automatically run all 6 gears in sequence
 ---
 
-Run cruise control mode to shift through all gears automatically.
+Use the Skill tool to invoke the cruise-control skill.
 
-This is **CRUISE CONTROL MODE** - full automation!
+Skill: cruise-control
 
-Execute: `/skill cruise-control`
+This runs CRUISE CONTROL MODE - shifting through all 6 gears automatically:
+1. Analyze → 2. Reverse Engineer → 3. Create Specs → 4. Gap Analysis → 5. Complete Spec → 6. Implement
 
-This will:
-- Run all 6 gears sequentially
-- Gear 1: Analyze → Gear 2: Reverse Engineer → Gear 3: Create Specs
-- Gear 4: Gap Analysis → Gear 5: Complete Spec → Gear 6: Implement
-- Handle clarifications based on configuration (defer/prompt/skip)
-- Create complete, spec-driven codebase
-
-Prerequisites: None (runs entire workflow from start)
-
-**Perfect for**: Hands-off migration of complete applications
+Perfect for hands-off migration of complete applications.

.claude/commands/stackshift.gap-analysis.md

@@ -2,17 +2,10 @@
 description: Gear 4 - Analyze gaps and create prioritized implementation roadmap
 ---
 
-Run the gap-analysis skill to identify incomplete features.
+Invoke the gap-analysis skill (Gear 4 of StackShift).
 
-This is **Gear 4** of the StackShift process.
+This identifies incomplete features, creates prioritized roadmap, estimates implementation effort.
 
-Execute: `/skill gap-analysis`
+Prerequisite: Complete Gear 3 (create-specs)
 
-This will:
-- Run /speckit.analyze for validation
-- Identify COMPLETE, PARTIAL, and MISSING features
-- Create prioritized roadmap
-- Estimate implementation effort
-- Suggest implementation phases
-
-Prerequisites: Complete Gear 3 (create-specs)
+Use the Skill tool with skill="gap-analysis".

.claude/commands/stackshift.implement.md

@@ -2,19 +2,10 @@
 description: Gear 6 - Implement features from specifications
 ---
 
-Run the implement skill to build features from specs.
+Invoke the implement skill (Gear 6 of StackShift).
 
-This is **Gear 6** of the StackShift process.
+This builds features from specs using /speckit.tasks and /speckit.implement. Only implements PARTIAL and MISSING features - existing features are already under spec control.
 
-Execute: `/skill implement`
+Prerequisite: Complete Gear 5 (complete-spec)
 
-This will:
-- Use /speckit.tasks to generate task list
-- Use /speckit.implement to build features
-- Work through prioritized implementation plan
-- Validate against specifications
-- Build PARTIAL and MISSING features
-
-Prerequisites: Complete Gear 5 (complete-spec)
-
-**Note**: Only implements incomplete features. Existing features are already under spec control from Gear 3!
+Use the Skill tool with skill="implement".

.claude/commands/stackshift.reverse-engineer.md

@@ -2,18 +2,10 @@
 description: Gear 2 - Extract comprehensive documentation from codebase
 ---
 
-Run the reverse-engineer skill to create comprehensive documentation.
+Invoke the reverse-engineer skill (Gear 2 of StackShift).
 
-This is **Gear 2** of the StackShift process.
+This creates comprehensive documentation including functional requirements, data architecture, API endpoints, and business logic in docs/reverse-engineering/.
 
-Execute: `/skill reverse-engineer`
+Prerequisite: Complete Gear 1 (analyze)
 
-This will:
-- Extract comprehensive documentation (8-10 files)
-- Document functional requirements
-- Document data architecture
-- Document API endpoints
-- Document business logic
-- Create docs/reverse-engineering/ directory
-
-Prerequisites: Complete Gear 1 (analyze)
+Use the Skill tool with skill="reverse-engineer".