workstream-execute

name	workstream-execute
description	Use when executing a workstream from `.workstreams/<name>/tasks.json`, completing all waves serially and tasks within a wave in parallel. Trigger phrases: "ws execute", "workstream execute".

Overview

Use workstream-about skill to understand workstreams.

First read activity.json to see what was recently accomplished. If it does not exist, create it with [].

Open design.md and plan.md for context, and review.md if there exists one. Then open tasks.json and choose the next highest-priority wave that has any elements with done set to false. Continue until all waves are complete.

For every task, you must use the workstream-tdd skill to implement it.

Every task inside a wave is fully parallelizable. Dispatch a subagent for each task inside a wave. Once the sub-agents are done, make sure there are no conflicts between their work and that it works together.

You must NEVER work on more than one wave at a time. Finish the current wave completely before starting the next wave.

As soon as an individual task is finished and its task-local verification is green, you should usually mark that task as done in tasks.json. Do not wait for the whole wave to finish before updating task completion state.

However, you must NOT let the final remaining undone task in the current wave become done: true until the whole wave is actually finalized. Wave finalization means ALL of the following are already complete:

• the current wave has been integrated
• the wave review gate is green
• the wave commit has been created
• the wave entry has been appended to activity.json

In other words: task-local completion is enough for non-final tasks in a wave, but the last task in a wave must stay undone until the whole wave is truly complete.

After you integrate and verify the current wave, complete that wave's review gate before starting the next wave. A wave review gate means:

• the wave's listed verification is green
• the integrated result of the wave works together
• the next wave's prerequisites are satisfied

Append a dated progress entry to activity.json when you START a wave describing:

• which wave is starting
• the most important tasks in that wave
• what you plan to do next

After you complete and verify a wave, make one git commit for that wave with a clear message summarizing the completed task ids.

Append a dated progress entry to activity.json after each completed wave describing what changed, what was verified, and what wave comes next.

Also append a dated progress entry whenever you hit a meaningful blocker or important discovery that changes execution strategy. Do not log every thought or every task-level micro-step. Prefer fewer, higher-signal entries.

Do not git init, do not change remotes, do not push.

When the final wave has been fully finalized and ALL tasks in ALL waves have done set to true, output READY_FOR_REVIEW. Immediately stop execute-phase work after outputting that promise.