qsd-quick

Execute ad-hoc tasks with atomic commits and STATE.md tracking.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ad-hoc tasks require reliable, auditable execution with minimal setup; this skill provides deterministic quick-task execution with state-tracking and atomic commits.

Core Features & Use Cases

  • Quick mode spawns qsd-planner (quick mode) + qsd-executor(s) to execute tasks with minimal overhead.
  • Quick tasks live in .planning/quick/ and updates STATE.md with "Quick Tasks Completed" entries for traceability.
  • Flags allow adjusting rigor: --discuss, --full, --validate, and --research to balance discussion, research, planning checks, and verification.

Quick Start

Describe a quick task you want completed and let qsd-quick execute it with atomic commits and state tracking.

Frequently Asked Questions about qsd-quick

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

FAQPage Schema
How do I automate ad-hoc coding tasks with atomic commits and state tracking?

To automate ad-hoc tasks with atomic commits and state tracking, use a quick workflow mode that spawns a planner and executors to rapidly execute work while updating a STATE.md file with completion entries for reliable traceability and safe-state management.

What is the best way to execute deterministic quick tasks without manual setup?

Executing deterministic quick tasks without manual setup is best handled by a quick mode that minimizes exploration overhead. It automatically orchestrates task execution and logs progress to a local planning directory for reliable audits.

Can I adjust the planning and verification rigor during quick task execution?

Yes, you can adjust planning and verification rigor during quick task execution by passing specific workflow flags. Flags such as --discuss, --full, --validate, and --research allow you to balance research, planning checks, and verification levels.

Does atomic commit task execution work for isolated ad-hoc workflows?

Atomic commit task execution works for isolated ad-hoc workflows by targeting tasks that require minimal exploration. It ensures safe-state management and task isolation by tracking progress in a dedicated quick tasks directory and STATE.md file.

When should I avoid using quick mode for task execution?

You should avoid using quick mode for task execution when your work requires deep exploration or extensive setup rather than rapid, ad-hoc completion. Quick mode targets minimal overhead and may lack the rigor needed for complex, non-deterministic workflows.