skills.rest
GigaFyde
GigaFydeCOMMUNITY
Explore all skills by this author →
Website𝕏@GigaFydeGitHub

project-orchestrator:design-reviewer

Review design documents for completeness and feasibility gaps.

Updated Feb 15, 2026
Search Tags:#integration#requirements#feasibility#risk-assessment#design-review#design-doc
One-click install
npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-design-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-orchestrator:design-reviewer
Source: https://github.com/GigaFyde/project-orchestrator/tree/main/skills/design-reviewer
Command: npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-design-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews design documents before implementation to identify gaps, ambiguities, and risks early in the project lifecycle.

Core Features & Use Cases

  • Two-stage review: Completeness (scenarios, edge cases, integration gaps) and feasibility (race conditions, failure modes, workflow).
  • Context-aware evaluation: Analyzes the design against existing commands and patterns to ensure compatibility and minimal disruption.
  • Actionable outputs: Produces a structured report detailing issues, implications, and recommended mitigations.

Quick Start

Provide a design document path and initiate the two-stage review to begin the assessment.

Frequently Asked Questions about project-orchestrator:design-reviewer

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

FAQPage Schema
How do I review a design document to identify gaps and risks before coding starts?▼

Reviewing a design document before implementation involves a two-stage assessment of completeness for edge cases and integration gaps, alongside feasibility checks for race conditions and failure modes, ultimately producing a structured report of issues and mitigations.

What is the best way to assess integration feasibility and identify failure modes in an early-stage design doc?▼

Assessing integration feasibility in a design doc requires context-aware evaluation against existing commands and patterns to ensure compatibility, analyzing workflow for failure modes and race conditions, and generating actionable outputs detailing issues and recommended mitigations.

How do I check if an integration plan covers edge cases and workflow scenarios adequately?▼

Checking an integration plan for adequate edge case and workflow coverage requires a completeness review stage that evaluates scenarios and integration gaps, ensuring minimal disruption by analyzing the design against existing patterns.

Can I use an automated risk assessment for early-stage project design documents?▼

You can use an automated risk assessment for early-stage design documents by providing the design doc path to initiate a two-stage review, which evaluates completeness and feasibility to output a structured report of identified risks and mitigations.

What should a structured design review report include to prevent project risks?▼

A structured design review report should include actionable outputs detailing identified issues, their implications, and recommended mitigations, generated after evaluating the design document's completeness and feasibility to catch risks before implementation.

Related Skills

Explore More Software Engineering Skills→
korchasakorchasa

agent-tech-lead

Select design variants, update system design specifications, and manage Git branches and draft pull requests.

Community
Advanced
ryanthedevryanthedev
60

reviewing-module-design

Analyze module designs for complexity, depth, information hiding, and abstraction weaknesses.

Community
Advanced
sbonocsbonoc

blueprint-sdd-traceability-keeper

Verify requirement traceability across specifications, code, and tests.

Community
Intermediate
jason660519jason660519

plan-review

Critique implementation plans with failure-mode mapping and mandatory diagrams.

Community
Advanced