# Orchestrate Design Reviews Before Implementation

Unreviewed designs can create avoidable implementation risks and costly rework. This skill routes design work through brainstorming, risk assessment, validation, and readiness checks.

## Install

```bash
npx skillstore add sickn33/design-orchestration
```

## Metadata

- Status: approved
- Slug: sickn33-design-orchestration
- Skillstore revision: r1
- Version status: missing
- Tree hash: fc24614b39dc4445cb1a5b79199b7b1065abf31be131dc206721c4a92b5d54c2
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/design-orchestration
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-design-orchestration
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-design-orchestration/manifest

## Capabilities

- Determines whether a validated design exists before implementation planning begins.
- Classifies design risk as low, moderate, or high using impact, complexity, uncertainty, novelty, and operational factors.
- Routes low-risk work to planning and escalates moderate-risk or high-risk work for additional review.
- Checks for an Understanding Lock, current design, and Decision Log before multi-agent review.
- Blocks implementation when approval, assumptions, risks, or required design artifacts are incomplete.

## Use Cases

- Route a New Product Feature: Assess a proposed feature, require design artifacts, and identify the next review or planning step.
- Review a System Change: Classify architectural risk and require multi-agent validation when operational impact or uncertainty is high.
- Check Implementation Readiness: Verify approval, assumptions, risks, and decision records before engineering work begins.

## Prompt Templates

### Route a Feature Request

```
Route this feature request through the design workflow. Identify required artifacts and the next skill to run: [feature request].
```

### Assess Design Risk

```
Assess this design as low, moderate, or high risk. Explain the factors and select the required next step: [design].
```

### Validate Review Inputs

```
Check whether this design package is ready for multi-agent review. Report missing artifacts and restrict the review scope: [design package].
```

### Decide Execution Readiness

```
Evaluate this reviewed design for implementation readiness. Route APPROVED, REVISE, or REJECT outcomes and state the next step: [review result].
```

## Limitations

- The skill coordinates workflow but does not generate designs.
- It depends on separate brainstorming, review, planning, or implementation skills.
- Risk classification is qualitative and does not use a numerical scoring model.
- It does not replace testing, environment validation, or expert review.

## Best Practices

- Provide the current design, Understanding Lock, and Decision Log before requesting orchestration.
- Document why each risk factor changes the required review level.
- State the final review disposition and next step explicitly.

## Anti Patterns

- Do not begin implementation before design approval and readiness checks.
- Do not use multi-agent review to reopen scope or add new ideas.
- Do not silently skip, add, or reduce required review stages.

## Security Audit

- Audited at: 2026-07-23T22:09:39.449\+00:00
- Summary: All six static findings are false positives caused by Markdown backticks around companion skill names, not executable shell syntax. The reviewed file contains no commands, scripts, network activity, secret access, or prompt injection.

## Stats

- Views: 99
- Downloads: 11
- Favorites: 0
- Popularity score: 0