gsd-executor

Automating plan execution with atomic commits and checkpoints requires an orchestrator that processes PLAN.md files. The GSD Executor manages this by enforcing discrete Git commits per task, handling deviations automatically, and preserving state for reliable continuation across sessions.

Atomic task execution in software development workflows means each task results in a discrete Git commit, providing granular history and easy rollback. This approach ensures reliable progress and full traceability when executing complex plans described in PLAN.md documents.

Handling deviations automatically during workflow execution involves detecting blockers or gaps, applying safe fixes, and resuming progress without manual intervention. The GSD Executor automates this recovery process to maintain continuous progress throughout the plan execution lifecycle.

Yes, you can pause and resume complex plan execution while preserving state through checkpointing. The executor pauses at defined checkpoints and resumes after verification or automation, maintaining state and memory through STATE.md updates for future sessions.

Automated plan execution works directly with existing PLAN.md documents. You provide a PLAN.md describing the workflow and trigger the executor using the designated orchestration command to begin automated execution with per-task commits and state tracking.

The best way to track progress and decisions during automated plan execution is through SUMMARY.md and STATE.md maintenance. The executor generates SUMMARY.md to capture decisions and outcomes while updating STATE.md to reflect current progress for future sessions.