design-orchestration

Route design work through brainstorming, review, and approval before implementation.

41|5|Updated Sep 30, 2025

Search Tags:#brainstorming #risk assessment #decision log #design orchestration #workflow routing #execution readiness

Ready to run

npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill design-orchestration-efekrbas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-orchestration
Source: https://github.com/efekrbas/discord-hypesquad-manager/tree/main/.agents/skills/design-orchestration
Command: npx skills add https://github.com/efekrbas/discord-hypesquad-manager --skill design-orchestration-efekrbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from jumping into implementation too early by enforcing a clear path from idea to validated design, so important decisions are reviewed instead of rushed.

Core Features & Use Cases

Workflow Routing: Directs work through brainstorming, review, escalation, and approval in the right order.
Risk-Based Enforcement: Distinguishes low-, moderate-, and high-risk decisions and escalates when extra review is required.
Execution Readiness: Checks for required artifacts like an understanding lock, decision log, and approved design before downstream work begins.
Use Case: A team proposing a major feature change can use this Skill to ensure the idea is clarified, reviewed, and approved before implementation planning starts.

Quick Start

Use the design-orchestration skill to route this feature through brainstorming, risk review, and execution-readiness checks before implementation.

Frequently Asked Questions about design-orchestration

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

FAQPage Schema

How do I prevent teams from starting implementation before a design is validated?▼

To prevent premature implementation, use design orchestration to route work through brainstorming, review, and approval sequences. This process requires an understanding lock, a decision log, and execution-readiness checks before any downstream planning or coding begins.

What is the best way to route risky product changes through a design review?▼

The best way to route risky product changes is applying risk-based enforcement during design orchestration. This distinguishes low-, moderate-, and high-risk decisions, automatically escalating high-risk items to require extra review before final approval.

How does risk assessment factor into design workflow routing?▼

Risk assessment factors into design workflow routing by categorizing decisions as low, moderate, or high risk. High-risk product changes trigger an escalation requiring additional review and approval before passing the execution-readiness check.

Do I need a decision log to pass execution-readiness checks for a new feature?▼

Yes, a decision log is required to pass execution-readiness checks. Design orchestration mandates specific artifacts including a decision log and an understanding lock to be approved before releasing a new feature to downstream implementation.

Why does my team skip the brainstorming phase before implementation planning?▼

Teams skip brainstorming when lacking enforced design orchestration. Implementing workflow routing directs work sequentially through brainstorming, review, and approval, ensuring ideas are clarified and validated before implementation planning starts.