executor

Executes GSD plans with atomic commits, deviation handling, and checkpoint protocols.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill executor-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executor
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/gsd/.agents/skills/executor
Command: npx skills add https://github.com/amanpal3/SKILLs --skill executor-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing multi-task implementation plans manually leads to inconsistent commits, lost progress, and unhandled edge cases. This Skill automates plan execution with strict commit discipline, automatic deviation handling, and structured checkpoint pauses so work is never lost or silently skipped. ## Core Features & Use Cases - Atomic Task Commits: Executes each task in a PLAN.md file and creates one verified git commit per task, confirming the commit landed before continuing. - Automatic Deviation Handling: Applies four rules to auto-fix bugs, add missing critical functionality, resolve blocking issues, and escalate architectural decisions to the user. - Checkpoint & Continuation Protocol: Stops at human-verify, decision, or human-action checkpoints and supports fresh continuation agents that resume from verified commits. - Use Case: A coding agent receives a phased GSD plan with five tasks; the executor completes each task, commits it, pauses at a deployment authentication gate, and produces a SUMMARY.md documenting all deviations and results. ## Quick Start Execute the current GSD plan file, committing each task atomically and stopping at any checkpoint for my approval.

Frequently Asked Questions about executor

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

FAQPage Schema
How do I execute a GSD plan with atomic commits?▼

Invoke the executor with a PLAN.md file; it reads .gsd/STATE.md, executes each task sequentially, and runs git add, git commit, and git log as separate commands per task. It confirms each commit landed before moving to the next task.

How does the executor handle work not in the plan?▼

It applies four deviation rules: auto-fix bugs, auto-add missing critical functionality like validation or error handling, auto-fix blocking issues, and stop for user decisions on architectural changes. All deviations are tracked and reported in SUMMARY.md.

What happens when a task requires authentication like vercel login?▼

Authentication errors are treated as expected gates, not failures. The executor stops, returns a human-action checkpoint with exact login steps and a verification command, then a continuation agent resumes after you authenticate.

Can a continuation agent resume a partially completed plan?▼

Yes. A continuation agent verifies previous task commits exist via git log, skips completed tasks, and resumes from the specified task. It never redoes committed work.

Why does the executor forbid chained git commands with &&?▼

Windows PowerShell 5.1 rejects && and || operators with a parse error, so chained commands fail silently and no commit occurs. The executor runs git add, commit, and log as separate commands and verifies the commit output.