Design Orchestration
- 497 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
design-orchestration is a meta-skill that routes feature work through brainstorm, risk-based multi-agent review, and execution readiness gates for developers who must block risky ideas from skipping design validation.
About
design-orchestration is a sickn33/antigravity-awesome-skills meta-skill dated 2026-02-27 that controls design workflow order without generating designs itself. It ensures ideas become designs, designs receive review, and only validated designs reach implementation by deciding which skill runs next, whether escalation is required, and whether execution is permitted. Developers use it when risky feature ideas need enforced gates between brainstorming, multi-agent review, and coding. The skill is routing and enforcement only—it orchestrates other skills rather than producing UI or architecture artifacts directly. Reach for it when agent teams tend to skip design validation and jump straight to code.
- Meta-skill that routes work—it does not generate designs itself
- Step 1 mandates `brainstorming` with Understanding Lock, Initial Design, and Decision Log
- Step 2 classifies designs as low, moderate, or high risk before escalation
- Coordinates `multi-agent-brainstorming` for validation on higher-risk paths
- Hard gate: execution and downstream planning skills only after validated design
Design Orchestration by the numbers
- 497 all-time installs (skills.sh)
- Ranked #760 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill design-orchestrationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 497 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you enforce design review gates before coding?
Enforce brainstorm → risk-based review → execution gates so risky feature ideas do not skip design validation.
Who is it for?
Engineering leads running multi-agent feature workflows who need enforced brainstorm-review-execute ordering before risky code changes.
Skip if: Developers who already have approved designs and only need direct UI generation or implementation without process routing.
When should I use this skill?
A risky feature idea needs orchestrated brainstorming, multi-agent design review, and an execution readiness check before coding.
What you get
Validated design ready for implementation, escalation decisions, and blocked or approved execution gate status
By the numbers
- Enforces a 3-stage gate flow: brainstorm, multi-agent review, execution readiness
Files
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.
---
Step 4 — Multi-Agent Review (If Invoked)
If multi-agent-brainstorming is run:
Require:
- completed Understanding Lock
- current Design
- Decision Log
Do NOT allow:
- new ideation
- scope expansion
- reopening problem definition
Only critique, revision, and decision resolution are allowed.
---
Step 5 — Execution Readiness Check
Before allowing implementation:
Confirm:
- design is approved (single-agent or multi-agent)
- Decision Log is complete
- major assumptions are documented
- known risks are acknowledged
If any condition fails:
- block execution
- return to the appropriate skill
---
Enforcement Rules
- Do NOT allow implementation without a validated design
- Do NOT allow skipping required review
- Do NOT allow silent escalation or de-escalation
- Do NOT merge design and implementation phases
---
Exit Conditions
This meta-skill exits ONLY when:
- the next step is explicitly identified, AND
- all required prior steps are complete
Possible exits:
- “Proceed to implementation planning”
- “Run multi-agent-brainstorming”
- “Return to brainstorming for clarification”
- "If a reviewed design reports a final disposition of APPROVED, REVISE, or REJECT, you MUST route the workflow accordingly and state the chosen next step explicitly."
---
Design Philosophy
This skill exists to:
- slow down the right decisions
- speed up the right execution
- prevent costly mistakes
Good systems fail early. Bad systems fail in production.
This meta-skill exists to enforce the former.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use design-orchestration for process enforcement across design skills; pick a generator skill when you need actual UI or architecture output.
FAQ
Does design-orchestration generate UI or architecture designs?
design-orchestration does not generate designs. The meta-skill routes work through brainstorming, multi-agent review, and execution readiness, deciding which skill runs next and whether coding is permitted.
What problem does design-orchestration solve?
design-orchestration prevents risky feature ideas from skipping design validation. It enforces that ideas become reviewed designs before any implementation skill is allowed to execute.
Is Design Orchestration safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.