- Home
- Skills
- Agents & Orchestration
- Wave Development: Brief-Gated Builds
More screenshots
Works with the AI Agents you already use
Wave Development: Brief-Gated Builds
Build software in waves a human can govern: written brief first, isolated builder, hard gates, and a merge that waits for your word.
$5
Wave Development: Brief-Gated Builds
Example session with this skill installed
I want to add an achievements system to my Godot game. Turn that into a wave I can approve before anyone writes code.
- Read your context and instructions
- Compiled the wave development
Connects securely to your tools. The creator never sees your data.
About this skill
"Improve the combat system" is not a plan — it is how an agent (or a contractor) produces a large change nobody can review, on a branch nobody dares merge. Wave Development replaces that with a governed unit of work: the wave. Before any code exists, a written brief fixes the numbered deliverables, the non-scope (what must not change), the exact base, the gates with numeric pass conditions, the acceptance criteria the human will judge personally, and the project's standing rules. The human approves the brief. One builder executes exactly that wave in an isolated worktree. The wave stops at a branch plus a report that maps every deliverable to its gate results — and merging waits for a separate, explicit word.
The skill includes the complete brief template, the eight-step wave workflow from drafting to closure, a worked example that runs a wave from brief to merged tree, and a merge-readiness rubric (five criteria scored 0–2, with a hard bar: no zeros, total ≥ 8) so "is this ready?" has an answer instead of a vibe. It also covers the lessons that only show up in real wave history: gates waived only by the human and only in writing, pre-existing failures disclosed with proof from the base commit, flaky checks recorded with both runs, cut-short gate runs reported as the fraction they actually covered, and the merge word treated as per-merge — never a standing mood carried over from the last good wave.
Use it for planned feature work, multi-part changes, engine or tooling builds, and any project where a human wants to approve the plan and judge the result. If your builds keep arriving as one giant diff, this is the structure that fixes it.
- It adds a real step — writing the brief — before building. For a five-minute hotfix that overhead is wrong, and the skill says when to skip the pattern.
- It governs one codebase's waves; coordinating waves across many repos at once needs an additional orchestration layer (a scheduled loop).
- Gates are the project's own. If the project has no meaningful checks, the rubric will expose that — but fixing the test suite is a different wave.
- The merge word stays human. Teams wanting fully automatic merging of green branches are asking for a different, riskier discipline.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected