architecture-review

Validate architecture decisions against design principles during planning and verification phases.

4|Updated Jan 8, 2026

Search Tags:#architecture #modularity #design-patterns #architecture-review #API-design #SoC

Ready to run

npx skills add https://github.com/mnthe/hardworker-marketplace --skill architecture-review-mnthe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/mnthe/hardworker-marketplace/tree/main/plugins/ultrawork/skills/architecture-review
Command: npx skills add https://github.com/mnthe/hardworker-marketplace --skill architecture-review-mnthe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture and design pattern validation during planning and verification phases for ultrawork sessions, helping ensure correct module boundaries and maintainability.

Core Features & Use Cases

SoC assessment: Checks separation of concerns, boundaries, and modularity across components.
Pattern & API review: Evaluates design patterns, interfaces, and API consistency.
Planning & verification alignment: Verifies plan-to-implementation coherence and documents architectural risks.

Quick Start

To initiate an architecture review in an ultrawork session, invoke the architecture-review skill during planning or verification on the project design docs.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I validate separation of concerns and modularity in my software architecture?▼

You can validate separation of concerns by assessing component boundaries and modularity across your project design docs. This architecture review process enforces clear interfaces, evaluates API consistency, and documents design trade-offs during planning and verification phases.

What is the best way to review API design and design patterns during project planning?▼

Reviewing API design and design patterns during project planning involves evaluating interfaces and API consistency against defined design principles. This ensures plan-to-implementation coherence and proactively documents architectural risks before development begins.

How do I check if my architecture plan aligns with implementation coherence?▼

Checking architecture plan alignment involves verifying plan-to-implementation coherence during the verification phase. This process assesses component boundaries, documents architectural risks, and ensures the actual implementation matches the defined design principles.

Can I use architecture review to assess component boundaries in an ultrawork session?▼

Yes, you can use architecture review in an ultrawork session to assess component boundaries. Invoking the review during planning or verification phases enforces separation of concerns, validates API design, and enables evidence collection for design trade-offs.

When do I need to document architectural risks and design trade-offs?▼

You need to document architectural risks and design trade-offs during the planning and verification phases of your project. Documenting these risks ensures modularity, validates API consistency, and maintains separation of concerns across component boundaries.

Why does my architecture review require defined design principles for validation?▼

Architecture review requires defined design principles to validate decisions effectively. Without these principles, the process cannot enforce separation of concerns, evaluate design patterns, or verify that component boundaries and API design meet the required standards.