Automatic mode - shift through all 6 gears sequentially without stopping. Like cruise control or automatic transmission, this runs the entire StackShift workflow from analysis to implementation in one go. Perfect for unattended execution or when you want to let StackShift handle everything automatically.
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Automatic transmission for StackShift - Shift through all 6 gears sequentially without manual intervention.
Use cruise control when:
Trigger Phrases:
Runs 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
Without stopping between gears!
At the start, you'll be asked:
Route Selection:
Choose your route:
A) Greenfield - Shift to new tech stack
B) Brownfield - Manage existing code
Implementation Framework:
Choose implementation framework:
A) GitHub Spec Kit - Feature specs in .specify/, /speckit.* commands
B) BMAD Method - PRD + Architecture in docs/, agent-driven workflow
Clarifications Handling: (Spec Kit only)
How to handle [NEEDS CLARIFICATION] markers?
A) Defer - Mark them, implement around them, clarify later
B) Prompt - Stop and ask questions interactively
C) Skip - Only implement fully-specified features
Implementation Scope: (Spec Kit only)
What to implement in Gear 6?
A) P0 only - Critical features only
B) P0 + P1 - Critical and high-value
C) All - Everything (may take hours/days)
D) None - Stop after specs are ready
Then cruise control takes over!
Note: For BMAD Method, questions 3-4 are skipped. BMAD agents handle clarifications and implementation through their interactive workflow.
auto_mode: truestackshift:code-analyzer agent/speckit.* slash commands/speckit.analyze/speckit.tasks and /speckit.implement for each featureauto_mode: truestackshift:code-analyzer agentdocs/ formatdocs/index.md, docs/architecture/, docs/architecture.md, docs/prd.md*workflow-init command to start BMAD workflowWhile cruise control is running, you can check progress:
# See current gear
node plugin/scripts/state-manager.js status
# Detailed progress
node plugin/scripts/state-manager.js progress
# Watch progress in real-time
watch -n 5 'node plugin/scripts/state-manager.js progress'
Or via MCP resource:
Read stackshift://progress
You can stop cruise control at any time:
"Stop cruise control"
"Pause StackShift"
"Switch to manual mode"
This will:
auto_mode: falseYou can resume cruise control later:
"Resume cruise control from current gear"
User: "Run StackShift in cruise control mode"
StackShift:
Setting up cruise control...
Choose your route:
A) Greenfield - Shift to new tech stack
B) Brownfield - Manage existing code
User: "B - Brownfield"
StackShift:
How to handle clarifications?
A) Defer - Clarify later
B) Prompt - Ask me now
C) Skip - Only implement clear features
User: "A - Defer"
StackShift:
Implementation scope?
A) P0 only
B) P0 + P1
C) All features
D) None (stop after specs)
User: "B - P0 + P1"
StackShift:
ā
Cruise control engaged! Shifting through all gears automatically...
š Gear 1: Analyzing... ā
Complete (2 min)
š Gear 2: Reverse engineering... ā
Complete (8 min)
š Gear 3: Creating specifications... ā
Complete (5 min)
š Gear 4: Gap analysis... ā
Complete (3 min)
⨠Gear 5: Completing specs (deferred clarifications)... ā
Complete (1 min)
š Gear 6: Implementing P0 + P1 features... š In Progress (est. 45 min)
Feature 1/8: user-authentication... ā
Feature 2/8: fish-management... ā
Feature 3/8: photo-upload... š In progress...
[... continues automatically ...]
š All gears complete! Application at 85% implementation.
Deferred clarifications (3) saved in: .specify/memory/clarifications.md
You can resolve these later with: /speckit.clarify
Cruise control can be configured via state:
{
"auto_mode": true,
"auto_config": {
"route": "brownfield",
"clarifications_strategy": "defer",
"implementation_scope": "p0_p1",
"pause_between_gears": false,
"notify_on_completion": true
}
}
Run cruise control in background:
# Start in background
nohup stackshift cruise-control --route brownfield --scope p0 &
# Check progress
tail -f stackshift-cruise.log
# Or via state
watch stackshift://progress
5pm: "Run cruise control, brownfield, P0+P1, defer clarifications"
9am: Check results, review generated specs, answer deferred questions
# .github/workflows/stackshift.yml
- name: Run StackShift Analysis
run: stackshift cruise-control --route brownfield --scope none
# Generates specs, doesn't implement (safe for CI)
Run cruise control on multiple projects:
- project-a: greenfield
- project-b: brownfield
- project-c: brownfield
"Show me what StackShift does - run full demo"
ā Runs cruise control with sample project
Cruise control creates checkpoints at each gear:
Before proceeding:
Pauses automatically if:
/speckit.analyze shows major inconsistenciesAt any point, you can:
"Pause after current gear"
"Stop cruise control"
"Switch to manual mode"
"Take control"
State saved, you can continue manually from that point.
After cruise control completes:
.stackshift-state.json shows 6/6 gears.specify/ directory)After cruise control completes:
.stackshift-state.json shows framework: "bmad"docs/ structure generated with all required files*workflow-init to take overRemember: Cruise control is like automatic transmission - convenient and hands-off. Manual mode (using individual skills) gives you more control. Choose based on your needs!
š Manual = Control each gear yourself š¤ Cruise Control = Let StackShift handle it
Both get you to the same destination!