gsd-execute-phase

Agent Skills › AjayIrkal23/agentic-mercy-10x › gsd-execute-phase

gsd-execute-phase

GitHub

该技能用于按阶段执行开发计划，支持基于波次的并行执行、依赖分析及子智能体调度。提供分步执行、仅修复缺口及交互模式等可选功能，确保流程可控与状态同步。

skills/gsd-execute-phase/SKILL.md AjayIrkal23/agentic-mercy-10x

Trigger Scenarios

需要执行某个开发阶段的完整计划请求按波次或特定条件（如仅修复缺口）执行任务

Install

npx skills add AjayIrkal23/agentic-mercy-10x --skill gsd-execute-phase -g -y

More Options

Use without installing

npx skills use AjayIrkal23/agentic-mercy-10x@gsd-execute-phase

指定 Agent (Claude Code)

npx skills add AjayIrkal23/agentic-mercy-10x --skill gsd-execute-phase -a claude-code -g -y

安装 repo 全部 skill

npx skills add AjayIrkal23/agentic-mercy-10x --all -g -y

预览 repo 内 skill

npx skills add AjayIrkal23/agentic-mercy-10x --list

SKILL.md

Frontmatter

{
    "name": "gsd-execute-phase",
    "description": "Execute all plans in a phase with wave-based parallelization",
    "allowed-tools": [
        "Read",
        "Write",
        "Edit",
        "Glob",
        "Grep",
        "Bash",
        "Agent",
        "TodoWrite",
        "AskUserQuestion"
    ],
    "argument-hint": "<phase-number> [--wave N] [--gaps-only] [--interactive] [--tdd]"
}

Execute all plans in a phase using wave-based parallel execution.

Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.

Optional wave filter:

--wave N executes only Wave N for pacing, quota management, or staged rollout
phase verification/completion still only happens when no incomplete plans remain after the selected wave finishes

Flag handling rule:

The optional flags documented below are available behaviors, not implied active behaviors
A flag is active only when its literal token appears in $ARGUMENTS
If a documented flag is absent from $ARGUMENTS, treat it as inactive

Context budget: ~15% orchestrator, 100% fresh per subagent.

<execution_context> @$HOME/.claude/get-shit-done/workflows/execute-phase.md @$HOME/.claude/get-shit-done/references/ui-brand.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. </runtime_note>

Phase: $ARGUMENTS

Available optional flags (documentation only — not automatically active):

--wave N — Execute only Wave N in the phase. Use when you want to pace execution or stay inside usage limits.
--gaps-only — Execute only gap closure plans (plans with gap_closure: true in frontmatter). Use after verify-work creates fix plans.
--interactive — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.

Active flags must be derived from $ARGUMENTS:

--wave N is active only if the literal --wave token is present in $ARGUMENTS
--gaps-only is active only if the literal --gaps-only token is present in $ARGUMENTS
--interactive is active only if the literal --interactive token is present in $ARGUMENTS
If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
Do not infer that a flag is active just because it is documented in this prompt

Context files are resolved inside the workflow via gsd-sdk query init.execute-phase and per-subagent <files_to_read> blocks.

Execute end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).

Version History

581d130 Current 2026-07-19 09:09

Metadata

Files: 0
Version: fc73590
Hash: af6376d4
Indexed: 2026-07-19 09:09

gsd-execute-phase