gsd-execute-phase

Execute PLAN.md tasks sequentially with atomic commits and DCO sign-off.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-execute-phase-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/gsd-execute-phase
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-execute-phase-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates reliable execution of a PLAN.md by driving deterministic task execution, committing changes incrementally, and enforcing TDD discipline.

Core Features & Use Cases

  • Atomic task execution with per-task commits and DCO sign-off
  • Deviation handling: document, justify, and continue with alternative plan
  • End-to-end workflow orchestration of planning, execution, and verification

Quick Start

Provide PLAN.md in the project root and invoke the execute phase to begin processing tasks in order.

Frequently Asked Questions about gsd-execute-phase

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

FAQPage Schema
How do I automate PLAN.md execution with atomic commits and TDD?

To automate PLAN.md execution, place the file in your project root and invoke the execute phase to process tasks in order, validate with tests, and perform atomic commits with DCO sign-off.

What is atomic task execution in software development planning?

Atomic task execution is performing development tasks in sequential order, validating each with tests, and committing changes incrementally with DCO sign-off to ensure deterministic and verifiable software delivery.

Do I need a specific test and version-control workflow setup to use atomic commits?

Yes, you need a configured test and version-control workflow in your project environment to support atomic commits with DCO sign-off and ensure changes are validated before integration.

How does deviation handling work when executing a development plan?

Deviation handling documents and justifies any necessary departures from the original PLAN.md, allowing the workflow to continue executing with an alternative plan while maintaining a reliable record.

What's the best way to orchestrate end-to-end development workflows with TDD discipline?

The best way to orchestrate end-to-end TDD workflows is using a deterministic execution phase that coordinates planning, task execution, test validation, and incremental commits aligned to your plan.

Why does plan execution fail without a PLAN.md in the project root?

Plan execution fails without PLAN.md in the project root because the workflow requires this file as the structural source to coordinate deterministic task execution, test validation, and atomic commits.