reviewing-python-architecture

Review ADRs against testing principles, Atemporal voice rules, and PDR constraints.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill reviewing-python-architecture-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-python-architecture
Source: https://github.com/outcomeeng/claude/tree/main/plugins/python/skills/reviewing-python-architecture
Command: npx skills add https://github.com/outcomeeng/claude --skill reviewing-python-architecture-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews ADRs and architecture decisions against established testing principles and Atemporal rules to enforce durable architectural truths.

Core Features & Use Cases

  • Validates ADR sections against /testing Stage definitions and Atemporal constraints.
  • Rejects ADRs that narrate code history, reference current files, or describe migrations.
  • Outputs violations with the specific principle and provides a corrected architecture example.

Quick Start

Run an ADR review against your document set to identify violations and receive corrected architectural guidance.

Frequently Asked Questions about reviewing-python-architecture

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

FAQPage Schema
How do I review ADRs against testing principles and atemporal constraints?

Validating ADRs involves checking architecture decisions against testing Stage definitions, atemporal voice rules, and PDR constraints. The review process rejects temporal narration and references to current code, outputting violations with corrected architecture guidance.

What is an atemporal rewrite for architecture decisions?

An atemporal rewrite removes temporal narration, code history, and migration plan references from architecture decisions. It enforces durable architectural truths by ensuring ADRs do not describe transitions or reference current files, outputting violations with corrected guidance.

How do I enforce Stage 5 exceptions for test doubles in Python architecture?

Enforcing Stage 5 exceptions for test doubles requires reviewing the ADR against testing principles. The review identifies violations where test doubles do not meet Stage 5 exceptions and outputs specific principle violations with corrected architecture guidance.

Why does my ADR review reject references to current code and migration plans?

ADR reviews reject references to current code and migration plans because they violate atemporal voice rules. The review enforces durable architectural truths by rejecting temporal narration and requires atemporal rewrites to output corrected architecture guidance.

What are the limitations of reviewing Python architecture decisions against PDR constraints?

The scope of reviewing Python architecture decisions against PDR constraints is limited to architecture decisions and ADR artifacts. It does not cover temporal narration, references to the current code, or migration plans, and only outputs violations with corrected architecture guidance for these in-scope elements.