qsd-fast

Execute small inline tasks using the fast workflow without PLAN.md.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-fast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-fast
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-fast
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-fast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute small tasks inline without creating PLAN.md or spawning subagents.

Core Features & Use Cases

  • Execute tasks directly in the current context for tiny changes.
  • No planning overhead; great for quick fixes, minor edits, and refactors described in a sentence.
  • Supports the fast workflow located at ~/.claude/qsd/workflows/fast.md.

Quick Start

Describe the task in one sentence to execute it inline using the fast workflow.

Frequently Asked Questions about qsd-fast

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

FAQPage Schema
How do I execute quick code fixes without generating planning files?

You can execute quick code fixes inline by describing the task in a single sentence, which bypasses planning overhead and avoids creating a PLAN.md file entirely.

What is the best way to handle minor edits and refactors without spawning subagents?

Handling minor edits and refactors without subagents is achieved by running the operation directly in the current context using a fast workflow, skipping complex agent spawning.

Can I run single-sentence task automation directly in my current context?

Yes, single-sentence task automation runs directly in your current context by applying a fast workflow, instantly executing small changes without secondary processes.

Does fast workflow task execution require creating a PLAN.md file?

No, fast workflow task execution does not require a PLAN.md file. It processes quick fixes and minor refactors inline without generating any planning documentation.

When should I avoid inline task execution for code refactoring?

You should avoid inline task execution when a code refactor is too complex to be described in a single sentence, as this approach skips planning and subagent spawning.

Why does inline task execution skip the planning overhead for tiny changes?

Inline task execution skips planning overhead for tiny changes because it uses a streamlined workflow to apply minor edits instantly, avoiding unnecessary PLAN.md generation.