GSD Executor

Execute PLAN.md files atomically with per-task commits and deviation handling.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/getdatasurge/fresh-staged --skill gsd-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Executor
Source: https://github.com/getdatasurge/fresh-staged/tree/main/.agent/skills/executor
Command: npx skills add https://github.com/getdatasurge/fresh-staged --skill gsd-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages end-to-end plan execution by running PLAN.md files atomically, creating per-task commits, tracking state, and producing summaries to ensure traceability.

Core Features & Use Cases

  • Atomic plan execution with per-task commits and automatic deviation handling.
  • Checkpoint-enabled workflows that pause at defined points for human or architectural decisions.
  • Comprehensive state management with STATE.md updates and automated SUMMARY.md generation.
  • Works across authenticated environments and supports continuation/restoration of interrupted runs.

Quick Start

Run the GSD Executor against your PLAN.md to execute all tasks atomically, generating a SUMMARY.md and updating STATE.md.

Frequently Asked Questions about GSD Executor

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

FAQPage Schema
How do I execute a PLAN.md file atomically with per-task commits?

To execute a PLAN.md file atomically, run the GSD Executor against your plan to process all tasks sequentially, creating per-task commits and generating a SUMMARY.md while updating STATE.md for traceability.

What is automatic deviation handling in plan execution workflows?

Automatic deviation handling manages end-to-end plan execution by detecting variations during task runs, pausing workflows at defined checkpoints to allow for human or architectural decisions before resuming execution.

How does state management work during automated plan execution?

State management during automated plan execution tracks progress by continuously updating a STATE.md file, enabling the restoration and continuation of interrupted runs while producing a SUMMARY.md for comprehensive traceability.

Do I need specific dependencies to use checkpointing for plan execution?

No specific dependencies are required to use checkpointing for plan execution, as the GSD Executor operates independently to pause workflows at defined points and supports continuation across authenticated environments.

What's the best way to restore an interrupted plan execution run?

The best way to restore an interrupted plan execution run is to leverage the existing STATE.md file, which tracks workflow progress and allows the GSD Executor to resume atomic task execution from the last checkpoint.

Why does my plan execution pause at certain tasks instead of completing?

Plan execution pauses at certain tasks because checkpoint-enabled workflows are designed to halt at defined points, waiting for human or architectural decisions before proceeding with the next atomic commit.