From great-minds
Wave-based parallel execution of XML task plans. Spawns fresh-context sub-agents for each task, runs independent tasks in parallel waves, and creates atomic git commits per task. Inspired by GSD (Get Shit Done) methodology. When the Superpowers plugin is installed, this skill composes with `superpowers:subagent-driven-development`, `superpowers:using-git-worktrees`, and `superpowers:dispatching-parallel-agents` for the engineering discipline within each dispatched task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-minds:agency-executeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute a planned phase using wave-based parallel execution with atomic commits.
Execute a planned phase using wave-based parallel execution with atomic commits.
When running under the daemon (/agency-daemon), the build phase uses a structured build approach instead of raw wave execution:
spec.md, todo.md, and tests/ before any codetodo.md item by item, running tests after eachThe wave-based XML approach described below is used when invoking /agency-execute directly (outside the daemon). Both approaches produce the same output: committed code in the deliverables directory.
This skill executes plans generated by /agency-plan:
Read engineering/phase-{N}-plan.md
Parse all <task-plan> XML blocks. Build the wave execution order.
If no plan exists, tell the user to run /agency-plan {N} first.
Before executing anything:
# Clean working tree required
git status --porcelain
# Must be empty — uncommitted changes block atomic commits
# Ensure we're on the right branch
git branch --show-current
# Should be feature/{phase-name} or similar
# Build passes before we start
npm run build 2>&1 || echo "BUILD FAILED — fix before executing"
If pre-flight fails, STOP and report. Do not proceed with a dirty tree.
For each wave (1, 2, 3, ...):
For each task in the current wave, spawn a haiku sub-agent with:
You are executing a single task from a phase plan.
Your ONLY job is to complete this task and verify it works.
## Task Plan
{paste the full XML task-plan here}
## Rules
1. Read EVERY file listed in <context> before making changes
2. Follow <steps> in exact order
3. Run ALL <verification> checks before reporting done
4. Do NOT modify files outside your task's scope
5. Do NOT commit — the orchestrator handles commits
6. If a step fails, report the failure with full error output
## Report Format
When done, report:
- STATUS: PASS or FAIL
- FILES_CHANGED: [list of files you modified]
- VERIFICATION: [results of each check]
- ERRORS: [any issues encountered]
Launch all tasks in the wave simultaneously using parallel Agent calls.
Wait for all sub-agents in the wave to complete. For each:
PASS: Stage changed files and create atomic commit:
git add {files_changed}
git commit -m "{commit-message from task-plan}
Task: {task-id}
Wave: {wave-number}
Phase: {phase-number}
Co-Authored-By: Claude <[email protected]>"
FAIL: Log the failure, DO NOT commit. Add to retry queue.
Before proceeding to the next wave:
npm run buildnpm run testIf the build breaks after commits:
git revert {sha} --no-editAfter all waves complete, for any failed tasks:
After execution completes, update STATUS.md:
phase: {N}
state: executed
tasks_total: {count}
tasks_complete: {pass_count}
tasks_failed: {fail_count}
tasks_retried: {retry_count}
last_commit: {sha}
Write an execution report to engineering/phase-{N}-execution.md:
# Phase {N} Execution Report
**Date**: {date}
**Duration**: {approximate time}
**Branch**: {branch-name}
## Wave Results
| Wave | Tasks | Passed | Failed | Commits |
|------|-------|--------|--------|---------|
| 1 | 3 | 3 | 0 | abc1234, def5678, ghi9012 |
| 2 | 2 | 1 | 1 | jkl3456 |
| ... | ... | ... | ... | ... |
## Commit Log
| Task ID | Commit | Message |
|---------|--------|---------|
| phase-1-task-1 | abc1234 | feat: add user auth endpoint |
| ... | ... | ... |
## Failed Tasks
| Task ID | Error | Retry Status |
|---------|-------|--------------|
| phase-1-task-5 | Type error in... | RETRY_PASS / RETRY_FAIL |
## Next Steps
- Run `/agency-verify {N}` to validate all work
- {Any manual steps needed}
Before any PR is created from a task execution, run these conditional reviews:
If the task involves UI, frontend, CSS, components, or design:
Agent(model: "haiku", subagent_type: "jony-ive-designer",
prompt: "Review the changes in this branch for visual quality.
Read the changed files. Evaluate:
- Is every element intentional? Remove anything that doesn't need to be there.
- Does spacing, alignment, and typography feel considered?
- Would this embarrass us on a stage demo?
Write a brief visual review (pass/fail with notes) to rounds/{project}/jony-ive-review-{task-id}.md")
If the task involves copy, messaging, landing pages, emails, or user-facing text:
Agent(model: "haiku", subagent_type: "maya-angelou-writer",
prompt: "Review the user-facing text in this branch.
Read the changed files. Evaluate:
- Does every word earn its place?
- Is the tone consistent and human?
- Will people FEEL something, or just read something?
Write a brief copy review (pass/fail with notes) to rounds/{project}/maya-angelou-review-{task-id}.md")
If either reviewer returns FAIL, the task agent must address the feedback before creating the PR.
| Role | Model | Why |
|---|---|---|
| Orchestrator (you) | Sonnet/Opus | Needs full context of all waves |
| Task executors | Haiku | Fresh context, atomic scope, 5x cheaper |
| Debug agents | Haiku | Focused diagnosis, single task scope |
| Build verifiers | Haiku | Just running commands and checking output |
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub sethshoultes/great-minds-constellation --plugin great-minds