Gsd Execute Phase
Developmentgsd-execute-phaseGsd Execute Phase is an Agent Skill for development published in the rokicool/gsd-opencode repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Implementation of gsd-execute-phase command
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/rokicool/gsd-opencode/blob/HEAD/gsd-opencode/skills/gsd-execute-phase/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gsd-execute-phase, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 Nexecutes only WaveNfor 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/.config/opencode/get-shit-done/workflows/execute-phase.md @$HOME/.config/opencode/get-shit-done/references/ui-brand.md </execution_context>
Available optional flags (documentation only — not automatically active):
--wave N— Execute only WaveNin the phase. Use when you want to pace execution or stay inside usage limits.--gaps-only— Execute only gap closure plans (plans withgap_closure: truein 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 Nis active only if the literal--wavetoken is present in$ARGUMENTS--gaps-onlyis active only if the literal--gaps-onlytoken is present in$ARGUMENTS--interactiveis active only if the literal--interactivetoken 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-tools init execute-phase and per-subagent <files_to_read> blocks.