deliverable-playbook

To aggregate deliverable.json fragments, you coordinate a scatter-gather workflow where domain squads produce outputs independently, then a meta-squad runs an aggregate.ts script to distill them into a single consolidated artifact.

A scatter-gather workflow for artifact generation distributes fragment creation tasks across parallel domain squads, then gathers and validates their outputs to ensure consistency before aggregating them into a final deliverable file.

You track distributed squad progress using standard MCP tools and outbox messages that broadcast signals for discovery, analysis, and validation phases to keep stakeholders informed throughout the aggregation process.

Yes, the aggregation process uses a worktree-based discovery and validation process to ensure consistency across all domain fragments before the meta-squad compiles them into the final deliverable.json.

No, the deliverable aggregation playbook requires no external dependencies, relying solely on its internal scatter-gather workflow, aggregate.ts script, and worktree-based validation process to coordinate squads.

The best way to consolidate parallel worktree outputs is using a meta-squad aggregation script that gathers domain fragments, stores results in a .squad/aggregation folder, and validates them into a single deliverable.json.