architect-refine-critique

Orchestrate three-phase software design reviews with Architect, Refiner, and Critique agents.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/igoyetche/send-to-kindle --skill architect-refine-critique-igoyetche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-refine-critique
Source: https://github.com/igoyetche/send-to-kindle/tree/main/.claude/skills/architect-refine-critique
Command: npx skills add https://github.com/igoyetche/send-to-kindle --skill architect-refine-critique-igoyetche

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the software design process by orchestrating a three-phase review cycle, ensuring robust and well-considered architectural decisions before implementation.

Core Features & Use Cases

  • Automated Design Chaining: Sequentially applies Architect, Refiner, and Critique agents to a design target.
  • Structured Review Output: Generates detailed design documents, refinement notes, and critique findings.
  • Use Case: When proposing a new microservice architecture, use /arc new-service-design /path/to/design/doc to generate an initial design, refine it based on best practices, and then have it rigorously critiqued for potential flaws.

Quick Start

Initiate a design review for a new feature named 'user-authentication' by running the command /arc user-authentication /path/to/feature/spec.md.

Frequently Asked Questions about architect-refine-critique

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

FAQPage Schema
How do I run a structured design review for a new software architecture?

Run a structured software architecture design review by executing the command with a target name and spec path. This triggers a three-phase process that generates design documents, refinement logs, and critique reports.

What is an iterative architect-refine-critique workflow for software design?

An iterative architect-refine-critique workflow sequentially applies an Architect agent, a Refiner, and a Critique agent to a design target. This cycle facilitates rigorous examination and improvement of architectural proposals before implementation.

Can I use this design review process for refactoring an existing microservice architecture?

Yes, you can use this design review process for refactoring an existing microservice architecture. It applies separation of concerns and DDD principles to generate refinement logs and critique findings for your current design.

What's the best way to critique architectural proposals for potential flaws before implementation?

The best way to critique architectural proposals is to use a three-phase review cycle that generates a critique report. This ensures rigorous examination of your design document and culminates in a facilitated ADR discussion.

Does this software design review tool require any specific dependencies or environment setup?

No external dependencies are required to run this software design review tool. It operates independently using internal scripts, references, and assets to orchestrate the Architect, Refiner, and Critique agents.

When do I need an ADR discussion during an architecture design review?

You need an ADR discussion at the culmination of an architecture design review. After the Architect and Refiner agents generate and improve the design, the Critique agent produces findings to facilitate this final decision record.