skills.rest
cody-hutson
cody-hutsonCOMMUNITY
Explore all skills by this author →
GitHub

pmo-principal-engineer

Evaluate design options, make build-vs-buy decisions, and author Architecture Decision Records.

Updated Jun 5, 2026
Search Tags:#solution design#non-functional requirements#build-vs-buy#architecture decision record#architecture decision
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-principal-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pmo-principal-engineer
Source: https://github.com/cody-hutson/pmo-platform/tree/main/release/skills/pmo-principal-engineer
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill pmo-principal-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines solution-level design decisions by offering guidance on architecture and NFR governance, facilitating build-vs-buy decisions, and authoring Architecture Decision Records (ADR).

Core Features & Use Cases

  • Architecture & NFR Governance: Assess and select architectures and define non-functional requirements for a component's solution.
  • Build-vs-Buy Decision Making: Evaluate whether to build or buy components based on cost, feasibility, and other factors.
  • ADR Authoring: Author and manage ADRs when design decisions are non-obvious or cross-cutting.
  • Use Case: As a Principal Engineer, you can use this Skill to decide the architecture for a new solution, determine the necessary non-functional requirements, decide whether to build or buy a component, and author an ADR for a complex decision.

Quick Start

To begin using the pmo-principal-engineer skill, follow these steps:

  1. Run 'pmo-principal-engineer <solution-context>' to start the process of architecture decision making.

Frequently Asked Questions about pmo-principal-engineer

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

FAQPage Schema
How do I document architecture decisions for non-obvious or cross-cutting design choices?▼

Authoring an Architecture Decision Record (ADR) captures non-obvious design choices by evaluating options against non-functional requirements and recording the context, decision, and consequences for complex solution-level designs.

What's the best way to evaluate build-vs-buy decisions for solution architecture?▼

Evaluating build-vs-buy decisions involves assessing components based on cost, feasibility, and non-functional requirements to determine whether to build internally or purchase externally for your solution boundaries.

How do I define non-functional requirements for a component's solution design?▼

Defining non-functional requirements (NFRs) for solution design requires assessing architecture options and selecting the specific governance constraints necessary to operate within a component's boundaries.

Do I need a technical review before making architecture decisions for a new solution?▼

Yes, invoking a technical review evaluates design options and informs architecture decision-making by providing the necessary analysis before finalizing build-vs-buy choices and authoring ADRs within a PMO.

When should I use an Architecture Decision Record in solution-level design?▼

You should author an ADR when design decisions are non-obvious, cross-cutting, or require formal governance within a component's boundary during solution-level architecture selection and NFR definition.

Related Skills

Explore More Software Engineering Skills→
MMXCMMXC

decision-frameworks

Evaluate engineering options using decision matrices and Architecture Decision Records.

Community
Intermediate
Design-System-ETDesign-System-ET

architecture-designer

Design scalable distributed systems and document architecture decisions with ADRs.

Official
Advanced
cody-hutsoncody-hutson

pmo-architect

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

Community
Advanced
Andy-HNUAndy-HNU

evaluating-new-technology

Evaluate emerging technologies and vendor options for build-vs-buy decisions.

Community
Intermediate