architect-refine-critique_skill

Overview

This skill runs a three-phase design review pipeline by chaining an architect, a refiner, and a critique subagent. It orchestrates sequential handoffs so each subagent focuses on one stage: initial design, improvement, and critical challenge. The goal is a structured, repeatable review cycle for system and module designs.

How this skill works

When invoked, the architect subagent generates an initial design for the specified target and name. The refiner subagent receives that design and produces an improved, more detailed version. The critique subagent then challenges assumptions, finds risks, and surfaces gaps. After the chain completes, the skill prompts the user to run a follow-up review command to discuss findings.

When to use it

• Preparing or documenting a new service, module, or API design
• Before approving significant refactors or architecture changes
• During design syncs to get a structured second opinion
• When drafting system design proposals for stakeholders
• To validate or stress-test an existing design before implementation

Best practices

• Provide a clear name and concise target description when invoking the pipeline
• Include context such as goals, constraints, and expected traffic or load
• Run iterative cycles: refine inputs based on critique and re-run the pipeline
• Keep each invocation focused on a single design boundary to avoid noisy outputs
• Use the follow-up review command to discuss and prioritize critique findings

Example use cases

• Designing a new microservice and validating data flow and scaling considerations
• Refactoring an authentication module and checking for security regressions
• Drafting an integration pattern between services and surfacing failure modes
• Creating a proposal for a new feature and getting a structured improvement pass
• Validating trade-offs and deployment strategies before sprint planning