skills.rest
erikhazzard
erikhazzardCOMMUNITY
Explore all skills by this author →
Website𝕏@erikhazzardGitHub

architecture__critiquing-design

Critique early-stage architecture designs to surface constraints and risks.

1|1|Updated Mar 16, 2026
Search Tags:#architecture#scalability#risk-management#system-design#stakeholders#design-review#tradeoffs
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill architecture-critiquing-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture__critiquing-design
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/architecture__critiquing-design
Command: npx skills add https://github.com/erikhazzard/vasir --skill architecture-critiquing-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, early-stage critique of architecture and multi-step designs to surface constraints, risks, and tradeoffs before code is written.

Core Features & Use Cases

  • Grounded review of the current stack and proposed designs to prevent over-engineering.
  • Structured outputs including a problem restatement, drivers table, steelman analysis, forcing-function tests, and a final recommendation.
  • Use cases include validating large features, cross-cutting infrastructure changes, or any design with capacity or resilience implications.

Quick Start

Provide a ground-truth architecture critique of the current design and deliver a concise, actionable recommendation.

Frequently Asked Questions about architecture__critiquing-design

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

FAQPage Schema
How do I review architecture designs for scalability and resilience risks before coding?▼

Architecture critique surfaces constraints and risks early by enforcing a structured review workflow with a ground-truth walk-through, drivers table, steelman analysis, and forcing tests to deliver a final recommendation.

What is the best way to prevent over-engineering cross-cutting infrastructure changes?▼

Preventing over-engineering requires grounded review of the current stack and proposed designs, analyzing tradeoffs and capacity implications to validate whether infrastructure changes are justified.

How do I conduct a structured design review for large features with multi-state designs?▼

A structured design review requires restating the problem, building a drivers table, performing a steelman analysis, applying forcing-function tests, and producing a final actionable recommendation.

When do I need an architecture critique for system design tradeoffs?▼

Architecture critique is needed for medium to large features, multi-state designs, or infrastructure changes driven by scale, decoupling, resilience, or future-proofing requirements.

Can I use forcing-function tests to validate stakeholder requirements during system design?▼

Forcing-function tests validate system designs by stress-testing proposed architectures against stakeholder drivers and capacity constraints before code implementation begins.

Related Skills

Explore More Software Engineering Skills→
misfitdevmisfitdev
2

frank-grimes

Critique ideas, code, and plans with evidence-first falsification review.

Official
Advanced
kennykankushkennykankush

max-prompt

Translate vague feedback into structured prompts for coding agents.

Community
Intermediate
loianeloiane
50

epic-slicing-planning

Plan Epic-level architecture and vertical-slice roadmaps for large features.

Community
Advanced
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced