agentleFS
Sign inStart free
adrianoanthonymma16-boopadrianoanthonymma16-boop/opencode-agents/skills/gsd-execute-phase/SKILL.md

gsd-execute-phase

Skill1 starsChanged 57 days agoMITView on GitHub

Execute all plans in a phase with wave-based parallelization

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 2 are common, 0 are distinctive, and 2 are very specific to this project.

  • 2

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a documented flag is absent from $ARGUMENTS, treat it as inactive

    line 18
  2. Very specific:

    Copilot (VS Code): Use vscode_askquestions wherever this workflow calls question.

    line 29
  3. Common:

    If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering

    line 44
  4. Common:

    Do not infer that a flag is active just because it is documented in this prompt

    line 45

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<objective> 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. </objective>

<execution_context> @/home/tony/.config/opencode/gsd-core/workflows/execute-phase.md @/home/tony/.config/opencode/gsd-core/references/ui-brand.md </execution_context>

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

<context> 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-tools query init.execute-phase and per-subagent <required_reading> blocks. </context>

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free