Skip to main content
WAVE engineering — Workers · Aggregate · Verify · Extend — the bounded-parallel pattern from the community “waves” workflows (rayfernando-skills, Wave-Engineering/claudecode-workflow). Unlike a plain task fan-out, the wave owns a verification spine: worker outputs are merged deterministically, a verifier judges the aggregate against a typed schema, and a follow-up wave runs only on the gaps the verifier names.

The mapping

Run it:
When to reach for it: breadth-first work where coverage is checkable — summarizing a corpus, auditing a codebase, migrating files — and a partial answer is worse than a slow one. When a single orchestrator can hold the whole task, deep-research’s lead-delegates-subtasks shape is simpler. See docs/prompting-techniques.md for where wave engineering sits in the full pattern catalog.