gsd-quick

To execute ad-hoc software engineering tasks with reliable state tracking, use a quick-mode executor that writes completed work directly to a STATE.md ledger. This ensures fast turnaround while maintaining auditable records and atomic commits.

The best way to automate quick tasks while skipping optional research phases is to use a quick workflow mode that omits optional agents by default. This approach prioritizes fast, deterministic execution while still supporting flags to enable research or verification when needed.

Yes, you need the GSD framework to run quick deterministic task execution. The framework is required to spawn the quick planner and executors that handle the automated workflow and update the task completion ledger.

State tracking for quick software automation tasks works by recording results in a STATE.md file using a Quick Tasks Completed ledger. This mechanism ensures that every fast turnaround task remains fully auditable without manual coordination overhead.

Yes, you can enable plan-checking and verification flags for quick workflow execution. Although quick mode skips optional agents by default to maximize speed, it supports configurable flags to activate discussion, research, full plan-checking, and verification.

You should avoid using quick mode for task planning and execution when your software engineering work requires deep research, extensive discussion, or complex multi-step verification by default, as quick mode skips these optional agents to prioritize fast, deterministic turnaround.