skills.rest
quantfiction
quantfictionCOMMUNITY
Explore all skills by this author →
GitHub

review-design

Coordinate parallel design reviews and enforce gate criteria before decomposition.

Updated Aug 23, 2026
Search Tags:#workflow#tdd#issue-tracking#design-review#parallel-review#gate-approval
One-click install
npx skills add https://github.com/quantfiction/dotfiles --skill review-design-quantfiction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-design
Source: https://github.com/quantfiction/dotfiles/tree/main/claude/plugins/global-skills/skills/review-design
Command: npx skills add https://github.com/quantfiction/dotfiles --skill review-design-quantfiction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate multi-perspective design reviews to ensure that gate criteria are satisfied before proceeding to implementation and decomposition steps.

Core Features & Use Cases

  • Orchestrates parallel reviews from security, performance, API design, and domain perspectives.
  • Consolidates findings with anchored IssueIds and delivers a formal verdict to progress to /write-beads.
  • Enforces an iteration policy with DESIGN_LEDGER updates and DESIGN_REVIEW artifacts.

Quick Start

Provide the TDD and initiate parallel reviews to determine the DESIGN_REVIEW verdict.

Frequently Asked Questions about review-design

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

FAQPage Schema
How do I coordinate multi-perspective technical design reviews before implementation?▼

Technical design reviews gate progress by requiring parallel reviews from security, performance, API design, and domain perspectives on a TDD. Reviewers consolidate findings with anchored IssueIds to deliver a formal verdict before implementation.

What is the best way to enforce gate approval criteria for issue tracking in a TDD workflow?▼

Gate approval criteria are enforced by consolidating parallel review findings into anchored IssueIds within a formal revise loop. This process updates the DESIGN_LEDGER and consumes DESIGN_REVIEW.md artifacts to track issue resolution before decomposition.

How do I track and consolidate issues found during parallel design reviews?▼

Issues found during parallel design reviews are tracked using an anchored issue taxonomy that assigns explicit IssueIds to findings from security, performance, API, and domain reviewers. These findings are consolidated to deliver a formal verdict.

Do I need a Technical Design Document to start a parallel review process?▼

Yes, a Technical Design Document (TDD) is required to start the parallel review process. The TDD provides the necessary context for security, performance, API design, and domain reviewers to evaluate gate criteria and generate a verdict.

What happens if a technical design document fails the gate review verdict?▼

When a TDD fails the gate review verdict, the workflow enforces an iteration policy with a formal revise loop. The design document must be updated to address consolidated issues before re-initiating parallel reviews and updating the DESIGN_LEDGER.

Related Skills

Explore More Software Engineering Skills→
KibbeyKibbey

builder

Implement Technical Design Documents into phased, code-reviewed features.

Community
Advanced
steven-3steven-3

brainstorming

Guide design exploration and produce an approved plan before implementation.

Community
Intermediate
rube-derube-de
10

council

Coordinate parallel AI consultants to review code and deliver weighted, filtered reports.

Community
Advanced
LerianStudioLerianStudio
205

dev-validation

Automate development completion validation with acceptance criteria checks and explicit user approval.

Official
Advanced