Skip to content

mmaideveloper/aiarchitecttoolkit / skills/review-architecture-conformance

review-architecture-conformance

Verified

Review an implementation, code change, pull request, or deployed design against linked use cases, Business Decision Records, approved ADDs, C4 views, accepted ADRs, quality attributes, and applicable governance safeguards. Use when checking architecture conformance, identifying undocumented drift, assessing stale artifacts, or producing an Architecture Conformance Review (ACR); do not use it to approve or rewrite decisions automatically.

Review Architecture Conformance

Workflow

  1. Read AGENTS.md, the change diff/code/tests/configuration, and all linked architecture artifacts.
  2. Determine the authoritative baseline: reviewed/approved use cases and BDRs, approved ADD content, accepted ADRs, applicable current/target C4 views, and the project governance profile. Proposed artifacts are advisory only.
  3. Build a requirement-to-evidence matrix using references/review-method.md.
  4. Inspect responsibilities, dependencies, interfaces, data flows, trust boundaries, deployment, failure modes, logging, oversight, and test evidence.
  5. Classify each variance as Conformant, Documented deviation, Undocumented drift, Artifact stale, or Not verifiable.
  6. Report findings by severity with exact code/artifact references and a concrete remediation. Do not modify code unless separately requested and authorized.
  7. Create architecture/reviews/ACR-NNN-<slug>.md when the user requests a persistent review; otherwise return the review in chat.

Rules

  • Do not treat an accepted ADR as proof that implementation conforms.
  • Do not treat current code as authority that silently overrides an accepted decision.
  • Recommend a new/superseding ADR when reality requires a decision change.
  • Recommend artifact updates when implementation is correct but documentation is stale.
  • Verify applicable privacy, data lifecycle, security, accessibility, safety, transparency, traceability, and human-oversight safeguards.
  • Never expose personal/health data, secrets, credentials, or sensitive operational values in findings.
  • Never claim approval; identify required owners and decision points.

Output

Lead with overall result and blocking findings. Include baseline artifacts, evidence matrix, findings with severity, compliance assessment, required artifact/code changes, unverifiable items, and recommended owner/action.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall