GSD Executor

Execute PLAN.md workflows with per-task commits and checkpointing.

Updated Aug 7, 2025
One-click install
npx skills add https://github.com/hGriff0n/velopitt --skill gsd-executor-hgriff0n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Executor
Source: https://github.com/hGriff0n/velopitt/tree/main/.agent/skills/executor
Command: npx skills add https://github.com/hGriff0n/velopitt --skill gsd-executor-hgriff0n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end execution of GSD plans by performing per-task commits and managing execution state, reducing manual tracking and ensuring auditable workflows.

Core Features & Use Cases

  • Atomic task execution with per-task commits and automatic plan progression
  • Deviation handling via predefined rules to auto-correct and continue
  • Checkpointing to pause and resume with a fresh agent
  • Automatic generation of SUMMARY.md and updates to STATE.md
  • PLAN.md loading and execution within an automation workflow

Quick Start

Provide PLAN.md and trigger the executor to run to completion, then review the generated SUMMARY.md and updated 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 automate plan execution with atomic commits?

Automate plan execution by loading a PLAN.md file and triggering the executor to run to completion, which performs per-task commits and updates execution state automatically.

How does checkpointing work when executing a PLAN.md workflow?

Checkpointing pauses the current execution state, allowing you to resume the PLAN.md workflow later with a fresh agent without losing progress or committing incomplete tasks.

Can I handle plan deviations automatically during task execution?

Yes, plan deviations are handled automatically via predefined deviation rules that auto-correct execution errors and continue the workflow without manual intervention.

What files are generated after running an automation workflow to completion?

After running an automation workflow to completion, the executor generates a SUMMARY.md file and updates the existing STATE.md file to provide an auditable record of the execution.

Do I need any external dependencies to run GSD plan automation?

No external dependencies are required to run GSD plan automation, as the executor independently manages state loading, plan parsing, and commit protocols.

When should I use an automated executor for state management instead of manual tracking?

Use an automated executor for state management when running complex PLAN.md workflows that require auditable per-task commits, resumable checkpointing, and deviation handling to reduce manual tracking errors.