design-doc-review

Review design documents through a seven-phase hardening pipeline.

3|1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ryankolean/summit-claude-skills --skill design-doc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-doc-review
Source: https://github.com/ryankolean/summit-claude-skills/tree/main/skills/design-doc-review
Command: npx skills add https://github.com/ryankolean/summit-claude-skills --skill design-doc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an expert design-doc-review workflow that converts ambiguous software designs into a structured, implementable blueprint through a seven-phase process including ingestion, structural audit, technical deep dive, continuity check, gap analysis with autoheal, adversarial final review, and hardened output.

Core Features & Use Cases

  • Phase-driven design doc review for RFCs, specs, ADRs, and architecture documents.
  • Autohealing missing sections with concrete, author-aligned content that preserves intent.
  • Adversarial final review to surface risks and ensure implementation readiness.

Quick Start

Paste your software design document and say review and harden this design to start the pipeline.

Frequently Asked Questions about design-doc-review

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

FAQPage Schema
How do I review and harden a software design document before implementation?

An adversarial design review is a final processing phase that stress-tests an architecture proposal to surface implementation risks, ensuring the hardened output is robust enough to execute without ambiguity or missing technical sections.

What is an adversarial design review for architecture proposals?

An adversarial design review is a final processing phase that stress-tests an architecture proposal to surface implementation risks, ensuring the hardened output is robust enough to execute without ambiguity or missing technical sections.

Can I use an automated review process for RFCs, specs, and ADRs?

The review pipeline handles missing sections through a gap autoheal phase, which automatically generates and injects concrete, author-aligned content that preserves your original design intent.

How does gap autoheal work when a design doc is missing sections?

The review pipeline handles missing sections through a gap autoheal phase, which automatically generates and injects concrete, author-aligned content that preserves your original design intent.

When do I need an implementation-ready blueprint for my software architecture?

To start the pipeline, simply paste your software design document into the prompt and request a review to initiate the automated structural audit, gap autoheal, and adversarial hardening process.

What's the best way to turn an ambiguous technical specification into an actionable plan?

To start the pipeline, simply paste your software design document into the prompt and request a review to initiate the automated structural audit, gap autoheal, and adversarial hardening process.