design-doc-orchestrator

Generate complete design documentation by coordinating agent-teams across Wave A/B/C.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-doc-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-doc-orchestrator
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/design-doc-orchestrator
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-doc-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the creation of complete system design documentation by coordinating a multi-wave agent-teams workflow, transforming scattered requirements into coherent outputs.

Core Features & Use Cases

  • Orchestrates Wave A/B/C parallel execution to generate architecture, data, API, and design docs
  • Provides TaskList DAG coordination, blackboard integration, and consistency checks
  • Use Case: You need a full design doc set for a new project within tighter timelines by automating multi-team collaboration.

Quick Start

To run, invoke the orchestrator with a design-docs request. It will spawn Wave A teammates and progressively produce docs/ outputs.

Frequently Asked Questions about design-doc-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate generating full design documentation including ADRs and API specs?

Automate design documentation by orchestrating multi-wave agent teams that execute in parallel to produce ADRs, architecture, data models, API specs, and UI guidelines. The workflow coordinates outputs via a TaskList DAG and Blackboard integration to ensure consistency and traceability across all generated docs.

What is the best way to coordinate parallel agent teams for architecture and data model documentation?

Coordinate parallel agent teams using a multi-wave execution model spanning Wave A, B, and C. A TaskList DAG manages dependencies between waves while Blackboard integration shares state, enabling teams to generate architecture and data model documentation concurrently with consistency checks applied throughout.

How does blackboard integration work for multi-wave design doc generation?

Blackboard integration provides shared state across Wave A, B, and C agent teams during design doc generation. Each wave reads from and writes to the blackboard, allowing downstream waves to access upstream outputs and enforcing consistency checks across architecture, API, and design documentation.

Can I use this orchestration approach for a new project that needs a complete design doc set quickly?

Yes, this orchestration suits new projects requiring a full design doc set under tight timelines. By spawning Wave A teammates and progressively producing docs outputs, it transforms scattered requirements into coherent architecture, data, API, and design documentation through automated multi-team collaboration.

What types of design documents are produced through multi-wave agent orchestration?

Multi-wave agent orchestration produces a complete suite of design documents including ADRs, architecture documentation, data models, API specifications, and UI/design guidelines. Each wave progressively generates these outputs with consistency checks ensuring traceability across the full documentation set.

Do I need a TaskList DAG to orchestrate design docs across multiple agent teams?

A TaskList DAG is required to coordinate dependencies and execution order across Wave A, B, and C agent teams. It ensures consistent, traceable outputs by managing the parallel workflow that generates architecture, data models, API specs, and design guidelines through Blackboard integration.