pmo-architect

Assess cross-component architecture, integration design, and blast-radius for software systems.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmo-architect
Source: https://github.com/cody-hutson/pmo-platform/tree/main/release/skills/pmo-architect
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pmo-principal-engineer, pmo-technical-analyst, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides expert-level system architecture guidance, facilitating complex software design decisions across components, middleware, and data architecture.

Core Features & Use Cases

  • Cross-Component Design: Assesses system-level architecture decisions and interactions between components.
  • Integration Design and Review: Evaluates integration design, blast-radius assessment, and system-level ADR authorship.
  • Use Case: When planning a new software system, use this Skill to design the architecture across components, ensure integration design is robust, and assess the blast-radius of proposed changes.

Quick Start

To perform a system design review, invoke the pmo-architect skill with the command: 'pmo-architect system design review'.

Frequently Asked Questions about pmo-architect

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

FAQPage Schema
What is blast-radius assessment in system architecture design?

Blast-radius assessment evaluates the potential impact of proposed changes across components and middleware. It identifies cross-component interactions to ensure integration design is robust before system-level architecture decisions are finalized.

How do I design architecture for complex software systems across multiple components?

To design architecture for complex software systems, assess cross-component architecture and evaluate integration design interactions. You can invoke system design review processes to guide middleware and data architecture decisions for your new software system.

Do I need specific technical analyst skills to perform a system design review?

Yes, performing a system design review requires pmo-principal-engineer and pmo-technical-analyst skills. These dependencies provide the necessary within-component design analysis and technical review to support system-level architecture guidance and blast-radius assessment.

What is the best way to document system-level architecture decisions?

The best way to document system-level architecture decisions is through system-level ADR authorship. ADRs capture cross-component design choices, integration design evaluations, and blast-radius assessments for complex software designs.

When should I assess cross-component architecture and integration design?

You should assess cross-component architecture and integration design when planning a new software system or evaluating proposed changes. This ensures interactions between components, middleware, and data architecture are robust before finalizing system-level architecture decisions.