turbo-implement

Detect git state and route implementation to Manual, Ralph, Autopilot, Guided, or Codex modes.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/devseunggwan/praxis --skill turbo-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turbo-implement
Source: https://github.com/devseunggwan/praxis/tree/main/skills/turbo-implement
Command: npx skills add https://github.com/devseunggwan/praxis --skill turbo-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between workspace setup and actual implementation by coordinating mode selection, context gathering, and handoff to delivery.

Core Features & Use Cases

  • Auto-detects git state (branch, worktree) to infer context
  • Chooses an execution mode (Manual, Ralph, Autopilot, Guided, Codex) based on issue/spec/plan presence
  • Chains to turbo-completion after successful implementation to deliver
  • Handles errors gracefully and offers fallbacks to keep the workflow moving

Quick Start

Identify the issue from the current git state, select an implementation mode, perform changes, and then run turbo-completion to finalize delivery.

Frequently Asked Questions about turbo-implement

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

FAQPage Schema
How do I automate git workflow implementation and delivery based on my current branch state?

Automating git workflow implementation involves auto-detecting your branch and worktree state to infer context, then routing execution to Manual, Ralph, Autopilot, Guided, or Codex mode. It seamlessly chains to turbo-completion to finalize the delivery pipeline after successful implementation.

What is the best way to route software implementation tasks to different execution modes automatically?

Routing implementation tasks automatically requires evaluating your current issue, plan, and spec presence. The system selects an execution mode like Autopilot or Guided based on this available context, ensuring the implementation phase matches your project's current workflow state.

How does the turbo-implementation pipeline handle errors during the git delivery workflow?

The turbo-implementation pipeline handles errors gracefully by offering fallbacks to keep the workflow moving. If issues arise during implementation or mode selection, it provides alternative paths to prevent blocking the delivery process.

Can I use this automated implementation workflow if I only have a git issue but no spec or plan?

You can use this workflow with only a git issue, as it auto-detects your git state and available context. The system will infer the appropriate execution mode, such as Manual, based on the absence of a spec or plan to keep the implementation moving.

Why does my automated delivery workflow need to chain to a completion step after implementation?

Your automated delivery workflow needs to chain to a completion step to ensure a seamless delivery pipeline. After successful implementation, turbo-completion finalizes the process, bridging the gap between workspace changes and actual project delivery.