fastlane

Orchestrates lightweight spec-driven implementation with a single coder subagent in the current workspace.

Updated May 19, 2026
One-click install
npx skills add https://github.com/davidsunglee/pi-flow --skill fastlane-davidsunglee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fastlane
Source: https://github.com/davidsunglee/pi-flow/tree/main/packages/pi-flow-core/skills/fastlane
Command: npx skills add https://github.com/davidsunglee/pi-flow --skill fastlane-davidsunglee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Small features and non-trivial bug fixes often do not justify a heavyweight multi-agent planning workflow, yet still need structured execution, testing, and review. This Skill provides a lightweight inline orchestration path that takes a spec or idea to committed, reviewed code without worktrees or coordinator subagents. ## Core Features & Use Cases - Inline orchestration: Runs every step in the orchestrator session, dispatching one coder subagent with high thinking and a one-time NEEDS_CONTEXT retry. - Verification and baseline comparison: Runs the project test suite through a shared test-runner artifact contract, with optional stash-based baseline comparison to separate pre-existing failures from new regressions. - Commit, review, and closure gates: Invokes commit, refine-code review, idea closure, and branch finishing only at defined checkpoints, never pushing automatically. - Use Case: After running define-spec on a small feature, invoke fastlane with the spec path or an IDEA-<id> to get a checklist-confirmed implementation, test verification, code review, and a committed result on the current branch. ## Quick Start Run fastlane on docs/specs/my-small-feature.md to implement, test, review, and commit the change in the current workspace.

Frequently Asked Questions about fastlane

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

FAQPage Schema
How do I implement a small feature from a spec without a full planning workflow?▼

Use fastlane with a spec path under docs/specs/ or an IDEA-<id>. It generates a short implementation checklist, dispatches one coder subagent, runs the project test suite, and commits the result after a refine-code review.

What inputs does fastlane accept?▼

Fastlane accepts either a markdown spec path under docs/specs/ or an idea ID matching IDEA-<8 hex chars>, which it reads through the built-in idea tool. Freeform input is rejected; run define-spec first to shape a spec.

When should I use fastlane instead of the deep generate-plan workflow?▼

Use fastlane for small features or non-trivial bug fixes that fit a lightweight current-workspace path. Specs with an Approach section, many requirements, or flagged Non-Goals like multi-subsystem or migration are better served by generate-plan.

Does fastlane work on protected branches like main?▼

Yes. Fastlane warns that it will commit directly to main, master, or develop and proceeds automatically. It never creates a worktree and never pushes; branch finishing is skipped on protected branches.

What happens when the test suite fails after a fastlane implementation?▼

Fastlane surfaces the failing identifiers and offers to continue with the failures recorded as concerns, run a baseline comparison by stashing changes and re-running the suite, or stop with changes left uncommitted for manual triage.

What happens if the coder subagent gets blocked?▼

A BLOCKED status stops fastlane immediately with the blocker surfaced and partial changes left uncommitted. A NEEDS_CONTEXT status triggers one retry after the user supplies the missing context; a second NEEDS_CONTEXT stops the run.