design-orchestration

Design Orchestration - Design Workflow Orchestration and Verification Control

Skill Overview

Design Orchestration is a design workflow orchestration skill that, by coordinating brainstorming, multi-agent review, and execution readiness checks, ensures ideas are designed, designs are reviewed, and only verified designs proceed to the implementation phase.

Applicable Scenarios

When you propose a new feature, new system, or major change, Design Orchestration ensures the design goes through a complete brainstorming and any necessary multi-agent review processes, preventing implementation from starting without adequate verification.

For design decisions that have large user impact, are irreversible, have high operational cost, or are highly complex, this skill enforces risk assessment and the appropriate level of review to prevent high-risk designs from skipping verification steps.

When your team needs to ensure correctness over speed and establish a standardized design process, Design Orchestration, as a meta-skill, can coordinate other skills and enforce design verification rules.

Core Features

Automatically determines which skill to call next (brainstorming or multi-agent review) based on whether the design has a validated solution, and enforces completion of specific steps and deliverables (such as aligned understanding, initial design, decision log) before proceeding, preventing necessary steps from being skipped.

After brainstorming completes, automatically performs a risk assessment and classifies the design as low/medium/high risk based on factors like user impact, irreversibility, operational cost, and complexity, then decides whether to proceed directly to implementation planning, to recommend review, or to require multi-agent review.

Before allowing implementation, automatically confirms whether the design has been approved, the decision log is complete, key assumptions have been recorded, and known risks have been acknowledged. If any condition is not met, execution is blocked and the relevant skill is invoked to fill the gaps.

Frequently Asked Questions

What's the difference between Design Orchestration and the brainstorming skill?

Design Orchestration is a routing and control skill — it does not generate design content but decides which skill should be called and when to allow progression to implementation. Brainstorming is responsible for generating design proposals, while Design Orchestration ensures the process is executed correctly.

When must multi-agent review be used?

Based on the risk assessment, high-risk designs must use multi-agent review, medium-risk designs are recommended to use it, and low-risk designs can proceed directly to implementation planning. Risk factors include user impact scope, irreversibility of changes, operational cost, system complexity, uncertainty, and technological novelty.

Will this skill generate designs?

No. Design Orchestration is a meta-skill that only controls and coordinates the execution flow of other skills. Design content is generated by the brainstorming skill, reviews are performed by the multi-agent-brainstorming skill, and Design Orchestration ensures these steps occur in the correct order and that necessary verifications are not skipped.