team-review

Run three independent design reviews and generate a consolidated report.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/davekim917/bootstrap --skill team-review-davekim917
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-review
Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-review
Command: npx skills add https://github.com/davekim917/bootstrap --skill team-review-davekim917

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous, multi-lens design reviews to surface architecture concerns and ensure design quality before proceeding to implementation.

Core Features & Use Cases

  • Three independent reviewers (architecture, best-practices, adversarial) evaluate a design and produce deduplicated findings.
  • Outputs a consolidated review at docs/specs/<feature>/review.md and updates docs/specs/<feature>/decisions.yaml to guide next steps (/team-plan).
  • Conditional gating prevents moving forward until MUST-FIX items are resolved or explicitly waived.

Quick Start

Provide an approved design at docs/specs/<feature>/design.md and run the /team-review workflow to start the three-review cycle.

Frequently Asked Questions about team-review

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

FAQPage Schema
How do I automate multi-lens design reviews for software architecture?

Automate multi-lens design reviews by running an approved design through three independent reviewers, generating a consolidated review report with deduplicated architecture concerns to ensure design quality before implementation.

What is a multi-lens design review and when do I need it?

A multi-lens design review evaluates an approved design from three independent perspectives: architecture, best-practices, and adversarial. You need it to surface architecture concerns and ensure design quality before proceeding to implementation.

How do I run a team design review workflow with three independent reviewers?

To run the team design review workflow, provide an approved design at docs/specs/<feature>/design.md and execute the review cycle to trigger three independent reviewers that produce a consolidated report at docs/specs/<feature>/review.md.

Can I proceed to implementation if the design review has unresolved MUST-FIX items?

You cannot proceed to implementation if MUST-FIX items are unresolved. Conditional gating prevents moving forward until MUST-FIX items are resolved or explicitly waived, updating decisions.yaml to guide next steps.

Do I need an approved design document before starting an automated design review?

You need an approved design document at docs/specs/<feature>/design.md and CLAUDE.md context before starting the automated design review. These prerequisites ensure the three independent reviewers have sufficient context to evaluate.

What's the best way to consolidate architecture, best-practices, and adversarial review findings?

The best way to consolidate review findings is running an automated workflow that deduplicates findings from three independent reviewers into a single review.md report and updates decisions.yaml to guide downstream planning steps.