Skills design-orchestration
📦

design-orchestration

Content revision r1 Safe ⚙️ External commands

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.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "design-orchestration" from https://skillstore.io/skills/sickn33-design-orchestration.md and its manifest at https://skillstore.io/api/skills/sickn33-design-orchestration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-design-orchestration.md Signed manifest GET /api/skills/sickn33-design-orchestration/manifest Signed lockfile GET /api/skills/sickn33-design-orchestration/lockfile

Test it

Using "design-orchestration". A team proposes a small, reversible label change with a completed design and Decision Log.

Expected outcome:

Risk: Low. The design is validated and reversible. Proceed to implementation planning.

Using "design-orchestration". A team proposes a new payment flow with unresolved compliance assumptions.

Expected outcome:

Risk: High. Run multi-agent-brainstorming after documenting compliance assumptions and completing the Decision Log.

Using "design-orchestration". A reviewed architecture is marked REVISE because its rollback strategy is incomplete.

Expected outcome:

Execution is blocked. Return the design for revision, resolve the rollback decision, and repeat review.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

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.

1
Files scanned
175
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (6)
SKILL.md:36 SKILL.md:37 SKILL.md:57 SKILL.md:91 SKILL.md:94 SKILL.md:102
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-design-orchestration/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-design-orchestration/security.svg)](https://skillstore.io/skills/sickn33-design-orchestration?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-design-orchestration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-design-orchestration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-design-orchestration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). design-orchestration security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-design-orchestration/audits/5

BibTeX citation

@techreport{sickn33-sickn33-design-orchestration-2026, author = {sickn33}, title = {design-orchestration security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-design-orchestration/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "design-orchestration security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-design-orchestration/audits/5" identifiers: - type: other value: "skillstore:sickn33-design-orchestration:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

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.

Try These Prompts

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].

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.

Avoid

  • 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.

Frequently Asked Questions

Does this skill create the design?
No. It routes work between design generation, validation, and implementation planning skills.
When is multi-agent review required?
It is required for high-risk designs and recommended for moderate-risk designs.
What information supports risk classification?
The skill considers user impact, irreversibility, operational cost, complexity, uncertainty, and novelty.
What artifacts are required for review?
Provide a completed Understanding Lock, the current design, and a Decision Log.
Can review introduce new features or scope?
No. Multi-agent review is limited to critique, revision, and decision resolution.
What happens when readiness checks fail?
Implementation is blocked, and the workflow returns to the appropriate design or review step.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

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

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

9 downloads · 99 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all