| name | design-orchestration |
| description | Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | ai-ml |
| category | llm-agents |
| risk | unknown |
| source | community |
| tags | ["skill","ai-ml","llm-agents","design","orchestration"] |
Design Orchestration (Meta-Skill)
Purpose
Ensure that ideas become designs, designs are reviewed, and
only validated designs reach implementation.
This skill does not generate designs.
It controls the flow between other skills.
Operating Model
This is a routing and enforcement skill, not a creative one.
It decides:
- which skill must run next
- whether escalation is required
- whether execution is permitted
Controlled Skills
This meta-skill coordinates the following:
brainstorming — design generationmulti-agent-brainstorming — design validation- downstream implementation or planning skills
Entry Conditions
Invoke this skill when:
- a user proposes a new feature, system, or change
- a design decision carries meaningful risk
- correctness matters more than speed
Routing Logic
Step 1 — Brainstorming (Mandatory)
If no validated design exists:
- Invoke
brainstorming
- Require:
- Understanding Lock
- Initial Design
- Decision Log started
You may NOT proceed without these artifacts.
Step 2 — Risk Assessment
After brainstorming completes, classify the design as:
- Low risk
- Moderate risk
- High risk
Use factors such as:
- user impact
- irreversibility
- operational cost
- complexity
- uncertainty
- novelty
Step 3 — Conditional Escalation
-
Low risk
→ Proceed to implementation planning
-
Moderate risk
→ Recommend multi-agent-brainstorming
-
High risk
→ REQUIRE multi-agent-brainstorming
Skipping escalation when required is prohibited.
