Merge Wave A and Wave B outputs into docs/project-context.yaml.
npx skills add https://github.com/sizukutamago/blueprint-plugin --skill wave-aggregator
Please help me install this Agent Skill. Skill: wave-aggregator Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/wave-aggregator Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill wave-aggregator
This skill consolidates parallel Wave A and Wave B outputs into a single, authoritative Blackboard file, eliminating conflicts and ensuring consistency in design decisions.
Run the wave-aggregator once Wave A and Wave B finish to merge their outputs and update docs/project-context.yaml with the unified context.
High-intent search queries and answers about installing and using this skill.
To merge conflicting parallel outputs into a unified context, aggregate Wave A and Wave B results using a two-step reduce process of normalization and adjudication to resolve contradictions, then write the coherent state to docs/project-context.yaml.
Resolving conflicting decisions from parallel wave phases requires an adjudication pass driven by contract_outputs from the Lead, applying normalization to align Wave A/B outputs before enforcing a deterministic single-writer update to the blackboard.
Yes, you need contract_outputs from the Lead to drive the adjudication pass for blackboard conflict resolution, ensuring that contradictions between Wave A and Wave B are resolved authoritatively and unresolved issues are properly reported.
A single-writer rule ensures deterministic writes to the shared blackboard file by restricting updates to a single aggregation pass, preventing race conditions and maintaining consistency when merging parallel agent team outputs into docs/project-context.yaml.
During parallel wave aggregation, unresolved issues that cannot be reconciled through normalization and adjudication are reported back to the Lead, ensuring the unified context written to the blackboard remains authoritative and free of silent failures.
No, consolidating parallel wave outputs requires docs/project-context.yaml as the deterministic write target, ensuring the unified context is persisted to a single authoritative blackboard file structure.
mhylleCoordinates parallel implementation waves with a central reviewer and lead for shared-file governance.
Atlas-Memory-FrameworkConvert implementation plans into dependency-resolved Automation Issue Manifests.
sizukutamagoGenerate complete design documentation by coordinating agent-teams across Wave A/B/C.
VectorInstituteResolve git merge conflicts across dependency, source, and configuration files.
