agentsclimarketplace
Sign in

Gsp subagent build loop

Skill mike007jd/game-superpowers/publish/clawhub/gsp-subagent-build-loop

Use when game implementation should default to a builder-reviewer-verifier loop instead of one monolithic pass.From its SKILL.md

Install
npx -y skills add mike007jd/game-superpowers --skill gsp-subagent-build-loop

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 310 tokens by cl100k_base, as published. Nobody here has run it

Game Subagent Build Loop

Goal

Turn a game build into a default multi-agent workflow: builder, reviewer, verifier. The goal is stronger and more stable output from one user prompt, not thrift.

Outputs

Follow the gsp-orchestrator output strategy:

  • inline (default): present subagent build loop plan in conversation.
  • minimal or full: write docs/game-studio/subagent-build-loop.md.

Default loop

For each meaningful build task or end-to-end slice:

  1. Dispatch a builder subagent to implement the slice.
  2. Dispatch a reviewer subagent using gsp-build-review.
  3. Dispatch a verifier subagent using gsp-playability-verifier.
  4. If review or verification fails, send the builder back with the concrete findings.
  5. Repeat until the slice is acceptable or the blocker should be surfaced to the user.

Parallel policy

Parallel builders are allowed only when ownership is disjoint. Examples: core loop vs HUD, feedback vs content pass, gameplay slice vs menus. Do not parallelize builders that fight over the same files or architectural choices.

Quality policy

  • benchmark and showcase builds should prefer this loop by default
  • greenfield polished-prototype work should usually prefer this loop
  • live-risky work may still use a tighter reviewer / verifier loop with smaller tasks

Important

Do not claim completion after the builder finishes. Review and verification are expected to find problems.

What ships with it: 5 files

4.1 KB alongside SKILL.md

examples/

tests/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.