gsd-quick

To execute ad-hoc tasks with atomic commits and state tracking, use a quick mode workflow that spawns a planner and executors to process the tasks, update a STATE.md file, and store definitions under a dedicated planning directory.

Tracking one-off development tasks separately from planned phases involves storing task definitions in a distinct quick tasks directory and logging completed results into a specific STATE.md table, ensuring deterministic state without modifying the main project roadmap.

Yes, you can skip optional agents when automating quick tasks. The quick execution mode supports skipping these agents to prioritize speed while still enforcing guaranteed execution gates throughout the planning and execution lifecycle.

State tracking for fast code changes works by appending completed task results to a Quick Tasks Completed table within STATE.md. This enforces deterministic state preservation and maintains guaranteed execution gates without altering the broader roadmap.

You should use a quick task workflow instead of a full planning phase for small, ad-hoc tasks that require guaranteed execution and atomic commits but do not warrant updating the main project roadmap or engaging the complete planning lifecycle.