Habilidades design-orchestration
📦

design-orchestration

Seguro

Orchestrate Design Workflows

This skill ensures design ideas are properly brainstormed, reviewed by multiple agents, and validated before reaching implementation. It prevents costly mistakes by enforcing a structured workflow.

Suporta: Claude Codex Code(CC)
🥉 72 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "design-orchestration". We need to redesign the authentication system

Resultado esperado:

Routing to design-orchestration workflow:

1. No validated design detected → Invoking brainstorming
2. After brainstorming: assess risk level
3. High-risk detected → REQUIRE multi-agent-brainstorming
4. After review: verify Execution Readiness

Current status: Awaiting design artifacts from brainstorming phase.

A utilizar "design-orchestration". Here is our low-risk UI change design

Resultado esperado:

Execution Readiness Check:

✓ Design exists
✓ Risk classified: LOW
✓ Decision Log present
✓ Assumptions documented

Result: Proceed to implementation planning

A utilizar "design-orchestration". Can we skip the multi-agent review?

Resultado esperado:

BLOCKED: Skipping required escalation is prohibited by design-orchestration.

This high-risk design requires multi-agent-brainstorming review before execution can proceed.

Auditoria de Segurança

Seguro
v1 • 2/24/2026

Static analysis detected 23 high-severity and 6 medium-severity patterns. Manual review confirms these are FALSE POSITIVES: backticks are markdown code formatting for skill names, and 'cryptographic algorithm' mentions are YAML frontmatter misinterpreted by the scanner. This is a legitimate workflow orchestration skill with no actual code execution, network requests, or malicious patterns.

1
Arquivos analisados
173
Linhas analisadas
2
achados
1
Total de auditorias

Problemas de Alto Risco (1)

SKILL.md:2SKILL.md:3SKILL.md:4SKILL.md:7SKILL.md:12
Weak Cryptographic Algorithm Detection (FALSE POSITIVE)
Static scanner detected 'weak cryptographic algorithm' at 23 locations. Manual review confirms this is YAML frontmatter content (name, description, risk fields) misinterpreted by the pattern matcher. No cryptographic code exists in this file.
Problemas de Risco Médio (1)
SKILL.md:39SKILL.md:40SKILL.md:60SKILL.md:94SKILL.md:97SKILL.md:105
External Command Detection (FALSE POSITIVE)
Static scanner detected 'Ruby/shell backtick execution' at 6 locations. These are markdown inline code spans (backticks) used to format skill names like `brainstorming`, not shell command execution.
Auditado por: claude

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
90
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Feature Design Governance

Apply structured review process to new feature designs before implementation begins

Risk-Aware Decision Making

Ensure high-risk system changes receive proper multi-agent validation

Design Quality Enforcement

Prevent premature implementation by requiring validated design artifacts

Tente Estes Prompts

New Feature Design Review 
Use design-orchestration to review the following feature proposal: [Describe your feature idea]. Follow the workflow: first invoke brainstorming if no design exists, then assess risk, and require multi-agent review for high-risk items.
Existing Design Validation 
Use design-orchestration to validate the attached design. Check for: Understanding Lock, Decision Log, design approval status. Block execution if any required artifacts are missing.
High-Risk Change Assessment 
Use design-orchestration to assess this change. Classify as low, moderate, or high risk based on user impact, irreversibility, operational cost, complexity, uncertainty, and novelty. Require multi-agent-brainstorming for high-risk items.
Execution Readiness Check 
Use design-orchestration to verify execution readiness. Confirm: design is approved, Decision Log is complete, major assumptions are documented, known risks are acknowledged. Block if conditions fail.

Melhores Práticas

  • Always invoke this skill first when starting any design work to establish proper workflow
  • Complete all required artifacts (Understanding Lock, Decision Log) before attempting to proceed to next phases
  • Trust the risk classification and allow the skill to enforce appropriate review levels

Evitar

  • Attempting to skip required review phases for time savings
  • Bypassing this skill to go directly from idea to implementation
  • Providing incomplete design artifacts and expecting execution to proceed

Perguntas Frequentes

What is design-orchestration?
Design-orchestration is a meta-skill that controls the flow between other design skills. It ensures designs are properly brainstormed, reviewed, and validated before implementation begins.
Does this skill generate designs?
No. This skill does not generate designs. It routes work to other skills (brainstorming, multi-agent-brainstorming) and enforces validation requirements.
When should I use this skill?
Use this skill whenever you propose a new feature, system, or change where correctness matters more than speed, or when a design decision carries meaningful risk.
What happens if I skip the required review?
The skill will block execution. Skipping required escalation or validation is prohibited. The workflow will return to the appropriate prior phase.
How does risk classification work?
The skill classifies designs as low, moderate, or high risk based on factors including user impact, irreversibility, operational cost, complexity, uncertainty, and novelty.
What artifacts must exist before execution?
Before execution, you need: approved design (single-agent or multi-agent), complete Decision Log, documented major assumptions, and acknowledged known risks.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/design-orchestration

Referência

main

Estrutura de arquivos

📄 SKILL.md