system-architect

Enforce architectural governance by producing ADRs and gating PRs.

Updated Aug 27, 2026

Search Tags:#architecture #documentation #adr #governance #design-review #pr-review #architecture-decision-records

Ready to run

npx skills add https://github.com/dsieczko/claude-agent-plugins --skill system-architect-dsieczko

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/dsieczko/claude-agent-plugins/tree/main/architect-agent/skills/system-architect
Command: npx skills add https://github.com/dsieczko/claude-agent-plugins --skill system-architect-dsieczko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System architect for Sentinel. Owns structural integrity, service boundaries, ADRs, and architecture reviews. Enforces ADR requirements as a gate on PRs. Does NOT write code or merge PRs — produces designs, reviews, and decision records.

Core Features & Use Cases

Enforces ADR requirements as PR gates to ensure architectural governance.
Produces and maintains ADRs, architecture reviews, and design decisions.
Reviews PRs for cross-domain boundaries, data ownership, and service boundaries.
Provides architecture coaching and guardrails for PR discussions.

Quick Start

Request an architecture review on the current PR to ensure ADR triggers are applied.

Frequently Asked Questions about system-architect

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

FAQPage Schema

How do I enforce architecture decision records as a gate on pull requests?▼

Enforce ADRs as PR gates by triggering architecture reviews for cross-domain boundary changes, verifying upstream ownership, and mandating decision records in docs/adrs before approval. This maintains service boundary integrity and architectural governance across workflows.

What is an architecture review for service boundaries and cross-domain ownership?▼

An architecture review for service boundaries evaluates pull requests to ensure cross-domain data ownership and structural integrity are maintained. It produces ADRs and design decisions to enforce governance without directly writing or merging code.

When do I need to create an architecture decision record?▼

Create an ADR when a pull request triggers architectural governance criteria, such as modifying service boundaries or upstream data ownership. ADRs document the design decisions and must be stored in docs/adrs to satisfy PR gating requirements.

Does this architecture governance approach write or merge code for my service?▼

No, this architecture governance approach does not write or merge code. It strictly produces ADRs, architecture reviews, and design documentation, providing coaching and guardrails for PR discussions to enforce structural integrity.

How do I start an architecture review on the current PR?▼

Start an architecture review on the current PR by requesting an evaluation against architectural criteria. The review identifies ADR triggers, checks upstream ownership and service boundaries, and outputs required decision records in docs/adrs.