sg-execute

Execute GSD phase tasks sequentially from PLAN.md with idempotency checks.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-execute
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-execute
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents fragile, error-prone manual switching between planning artifacts and implementation steps by executing the current phase’s tasks directly from PLAN.md in the correct sequence.

Core Features & Use Cases

  • Direct phase execution from PLAN.md: Reads the current phase plan and runs each task sequentially (no Superpowers handoff).
  • Phase auto-resolution: Determines the phase number from STATE.md unless a phase argument is provided.
  • Idempotent execution via plan hash: Skips re-execution when HANDOFF.md already records the same plan hash for the phase.

Quick Start

Run /super-gsd:sg-execute to execute the current phase tasks referenced by your existing PLAN.md and update HANDOFF.md when finished.

Frequently Asked Questions about sg-execute

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

FAQPage Schema
How do I execute tasks sequentially from a markdown plan file?

Sequential task execution from PLAN.md is performed by reading the current phase plan and running each task directly in order, preventing manual switching between planning artifacts and implementation steps.

How does idempotent phase execution work for task orchestration?

Idempotent phase execution works by computing a phase plan hash and writing it to .planning/HANDOFF.md, allowing the system to skip re-execution when the same plan hash is already recorded for that phase.

Can I auto-resolve the current phase from state tracking files?

Yes, phase auto-resolution reads the current phase number directly from STATE.md unless a specific phase argument is provided explicitly in the command input.

What is the best way to coordinate hand-off tracking during milestone implementation?

Coordinating hand-off tracking is best handled by enforcing direct implementation mode, computing a phase plan hash, and recording the execution state in .planning/HANDOFF.md upon completion.

Do I need Superpowers executing-plans to run GSD phase tasks?

No, you do not need Superpowers executing-plans to run GSD phase tasks; the system executes the current phase implementation plan directly without any external Superpowers handoff.