speedrun

Automate sequential execution of remaining bugfix workflow phases.

Updated May 5, 2026

Search Tags:#debugging #workflow automation #bugfix #artifact tracking #phase execution #escalation handling

Ready to run

npx skills add https://github.com/swghosh/ambient-workflows --skill speedrun-swghosh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speedrun
Source: https://github.com/swghosh/ambient-workflows/tree/main/workflows/bugfix/.claude/skills/speedrun
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill speedrun-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents slow, stop-and-start bugfix sessions by automatically selecting and running the next incomplete phase until the workflow completes (or an escalation requires you).

Core Features & Use Cases

Guided phase progression: Detects which bugfix phases are already completed and immediately runs the next one in order to keep momentum.
Artifact-aware completion: Uses existing artifact paths and conversation context to determine what to skip and what to execute next.
Escalation-respecting execution: Stops for user input when the workflow reaches low-confidence, ambiguous-root-cause, trade-off-heavy, or compliance/security decision points.

Quick Start

Start a speed-run from your current point by running /speedrun and let it execute the next incomplete bugfix phases in sequence.

Frequently Asked Questions about speedrun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate multi-step bugfix workflow phases without pausing?▼

Automating bugfix workflow phases requires sequential phase execution that skips completed steps using artifact-driven detection. The workflow runs continuously without pausing until reaching an escalation gate or terminal summary.

What is artifact-driven phase detection in a bugfix workflow?▼

Artifact-driven phase detection is a mechanism that uses existing artifact paths and conversation context to determine which bugfix phases are already completed. It identifies what to skip and what to execute next to maintain workflow momentum.

When do bugfix escalation gates stop automated phase execution?▼

Automated bugfix phase execution stops at escalation gates when the workflow encounters low-confidence, ambiguous-root-cause, trade-off-heavy, or compliance and security decision points. Execution pauses for user input before resuming.

Can I resume a partially completed bugfix workflow from existing artifacts?▼

Yes, you can resume a partially completed bugfix workflow from existing artifacts. The system uses artifact paths and conversation context to detect completed phases and immediately runs the next incomplete phase in sequential order.

What's the best way to speed up stop-and-start bugfix sessions?▼

The best way to speed up stop-and-start bugfix sessions is automated sequential phase execution that skips completed steps. This approach detects existing artifacts and runs remaining phases continuously until an escalation requires user input.

Do I need to manually track which bugfix phases are completed?▼

No, you do not need to manually track completed bugfix phases. The workflow automatically detects completion using artifact paths and conversation context, skipping finished phases and executing the next incomplete one in sequence.