AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Architecture Review

skill-ashermahonin-agentic-skills-architecture-review · by ashermahonin

Design or review software architecture using system context, container, component, runtime, deployment, data, API, integration, crosscutting concepts, and ADR artifacts. Use before large implementation, service-boundary changes, infrastructure changes, API or data contract changes, migrations, reliability work, security-sensitive design, or architecture artifacts `14-system-context.md` through `2…

↗ Repository
— No reviews yet
0 installs
40 views
0.0% view→install

Install

$ agentstack add skill-ashermahonin-agentic-skills-architecture-review

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-ashermahonin-agentic-skills-architecture-review)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Architecture Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Architecture Review

Role

Turn requirements and current-state evidence into a system shape that can be implemented, tested, operated, and changed. Prefer clarity and tradeoffs over ornamental diagrams.

Start By

  • Gather requirements, quality scenarios, current-state evidence, and constraints.
  • Name the architecture decision that matters most.
  • Identify boundaries: user/system, service/service, data/API, sync/async, build/runtime, trust zones.
  • Decide what must be documented as an ADR.

Procedure

  1. Draft the system context first, then containers, then components only where detail changes decisions.
  2. Map runtime scenarios for critical user and failure paths.
  3. Define data ownership, API contracts, integration contracts, and deployment assumptions.
  4. Review crosscutting concerns: auth, secrets, observability, errors, retries, rate limits, privacy, migration, rollback, and operations.
  5. Write tradeoffs explicitly, including what is intentionally not solved.
  6. Refuse implementation handoff until risky decisions have owners and validation paths.

Principal-Level Defaults

  • Follow ../../routing/principal-operating-model.md before moving from analysis to implementation.
  • Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.
  • Keep a decision trace: facts, assumptions, options considered, tradeoffs, selected path, validation evidence, and rollback or follow-up.
  • Escalate irreversible, security-sensitive, data-migration, production, or cross-boundary choices before write-heavy work.

Output Artifacts

  • System context
  • Container and component views
  • Runtime scenarios
  • Deployment view
  • Data model and API contracts
  • ADR candidates or decisions

Quality Bar

  • Architecture must answer how the system changes safely, not only how it works when happy.
  • Do not draw a component unless it affects ownership, contract, or risk.
  • Call out irreversible or expensive decisions.
  • Tie architecture back to requirements and quality scenarios.

Handoff

Hand off boundaries, contracts, ADRs, validation expectations, and unresolved risks to decomposition.

References

  • references/architecture-artifacts.md: Use this to decide which architecture artifacts are required.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills