dev-room

Review codebases, architecture, API design, and UX flows with staged expert output.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/KBRglobal/advisiorai --skill dev-room
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-room
Source: https://github.com/KBRglobal/advisiorai/tree/main/skills/dev-room
Command: npx skills add https://github.com/KBRglobal/advisiorai --skill dev-room

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, adversarial technical review process that surfaces design flaws, performance risks, and unclear abstractions so teams can make concrete build-or-abandon decisions. It condenses diverse engineering philosophies into a single, prioritized output so you stop debating and start executing.

Core Features & Use Cases

  • Ten expert perspectives: Synthesizes opinions from systems, DX, UX, compiler, and shipping-focused engineers to expose tradeoffs and hidden risks.
  • Fixed deliverable format: Produces initial reactions, an interactive debate, hard questions to answer, confidence scoring, a risk map, a prioritized week-one plan, and explicit technical decisions.
  • Applicable scenarios: Stack selection, architecture reviews, API design critiques, developer-experience audits, performance troubleshooting, and UI/UX flow reviews.
  • Triggers & integration: Use when sharing code snippets, architecture diagrams, API specs, or asking "dev review" / "architecture review" / "what stack should I use".

Quick Start

Paste your code or architecture spec and ask dev review to get a ten-expert critique with debate, hard questions, a risk map, confidence scores, a prioritized week-one plan, and concrete technical decisions.

Frequently Asked Questions about dev-room

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

FAQPage Schema
How do I get a structured architecture review for my codebase?

A structured architecture review synthesizes ten expert engineering perspectives into a staged output, surfacing design flaws and technical debt through debate, hard questions, and a risk map to deliver concrete build decisions. You trigger it by pasting architecture diagrams or specs.

What is the best way to run an adversarial API design critique?

An adversarial API design critique evaluates API specs by applying diverse engineering philosophies—like DX and systems perspectives—to expose tradeoffs and hidden risks. It produces confidence scoring, a prioritized week-one plan, and explicit technical decisions to stop debates and start executing.

Can I use a technical war room for developer-experience audits and UI flow reviews?

Yes, a technical war room supports developer-experience audits and UI/UX flow reviews. It evaluates product specs and DX flows across web and backend contexts, generating interactive debates and a risk map that highlight performance risks and unclear abstractions.

How do I facilitate a stack selection debate that ends in a concrete decision?

Facilitate stack selection by submitting your options to an expert review process that generates initial reactions, interactive debates, and hard questions. This yields confidence scoring and explicit technical decisions, replacing endless team debates with a prioritized week-one plan.

When do I need an expert code review instead of standard static analysis?

You need an expert code review when standard static analysis cannot resolve architecture debates or unclear abstractions. It applies adversarial technical perspectives to code snippets, producing a risk map and concrete technical decisions that address design flaws and performance risks missed by automated tools.