sp-fast

Executes trivial low-risk code changes directly without entering the full specify-plan workflow.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-fast-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-fast
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-fast
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-fast-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Full planning workflows add unnecessary overhead for tiny fixes like typos, missing imports, or small config edits. This Skill provides a guarded fast lane that completes genuinely trivial, local, low-risk changes directly while enforcing scope gates, verification, and safe upgrade paths when work grows. ## Core Features & Use Cases - Scope-Gated Fast Lane: Applies only when the change touches at most 3 files, crosses no shared registration surface or contract boundary, and has a known root cause. - Automatic Upgrade Routing: Redirects expanded or risky work to /sp-quick, /sp-specify, or /sp-debug based on consequence analysis triggers. - Inline Project Cognition Closeout: Runs project-cognition closeout planning and update commands after workflow-owned mutations, with verification evidence and truthful reporting. - Use Case: A developer asks to fix a typo in a CLI help string. The Skill confirms the scope gate, makes the edit directly, runs the smallest targeted verification, and reports exactly what changed and what was verified. ## Quick Start Ask the agent to use the sp-fast skill to fix a small typo in the CLI help text and verify it with a targeted check.

Frequently Asked Questions about sp-fast

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

FAQPage Schema
How do I make a quick trivial fix without full planning in spec-kit?▼

Invoke the sp-fast skill with a one-sentence description of the fix. It performs the change directly using leader-direct execution, runs the smallest meaningful verification, and reports what changed without creating spec, plan, or task artifacts.

When should I use sp-fast versus sp-quick?▼

Use sp-fast only when the change touches at most 3 files, avoids shared surfaces like router tables or export barrels, crosses no contract boundary, and has a known root cause. If any check fails or the consequence analysis gate triggers, the skill upgrades the work to sp-quick.

Does sp-fast require a spec-kit project structure?▼

Yes, it requires a spec-kit project with a .specify directory and access to the project-cognition runtime for compass queries and closeout updates. Without that structure the workflow contract cannot be satisfied.

What happens if a fast-path task grows beyond its scope?▼

The skill stops and redirects instead of forcing the task through. Work expanding past 3 files or touching shared surfaces upgrades to sp-quick, while lifecycle, security, or architecture-impacting changes route to sp-specify.

Why does sp-fast refuse bug fixes with unknown root causes?▼

The fast lane requires a known root cause before editing. If multiple plausible causes remain or diagnosis is still needed, the skill routes the work to sp-debug rather than applying a speculative symptom patch.