Wave-Based Task Breakdown Break the feature into sized, dependency-ordered task waves. This makes it easier to keep track of progress as we build so we ensure that we're on track to build what the user expects: Process 1. Read the spec : Identify all behavioral requirements and technical changes from the agent plan or gjalla spec. 2. Identify tasks : Each task should touch 1-2 files and produce a small, reviewable diff that's verifiable. 3. Map dependencies : Which tasks must complete before others can start? 4. Group into waves : Tasks within a wave can be done in parallel; waves are sequent…