AgentStack
SKILL verified MIT Self-run

Architecture Decisions

skill-xopoko-plug-n-skills-architecture-decisions · by Xopoko

Use when structural code choices need durable rationale: ADRs, tradeoffs, consequences, reversibility, ownership, review triggers, and validation plans.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-xopoko-plug-n-skills-architecture-decisions

✓ 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.

Are you the author of Architecture Decisions? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Architecture Decisions

Use when making, documenting, reviewing, or revising an architecture decision.

ADR Threshold

Create or review an ADR when a choice:

  • shapes module boundaries, ownership, data ownership, runtime topology, or integration style;
  • changes reliability, scalability, security, performance, operability, testability, or cost;
  • introduces hard-to-reverse dependency, platform, data model, framework, or protocol;
  • affects multiple teams, services, packages, apps, release trains, CODEOWNERS/OWNERS coverage, or cross-owned dependencies;
  • needs a revisit trigger because evidence may change.

Skip ceremony for small local implementation choices unless asked.

Contract

Capture status, context/forces, options, decision/rationale, consequences, affected components, migration plan, fitness functions, owner/review path, ownership exception path, expiry/revisit trigger.

Use architecture_intelligence.decision.v1 for durable output.

Review Questions

  • What source/runtime evidence supports the decision?
  • Which quality attribute improves and which gets worse?
  • What is the smallest reversible step?
  • What would make this decision wrong?
  • How will drift be detected?
  • Who owns implementation and later review?
  • Which owners must review cross-owned dependency/runtime changes?
  • Which tests, metrics, or operational signals prove it worked?
  • What rationale would be lost if this stayed only in chat or PR comments?

Verdict

  • accept: evidence and validation are sufficient.
  • sharpen: promising but missing constraints, options, owner, or validation.
  • block: high-risk or unsupported.

Before accepted, require explicit alternatives, named tradeoffs, evidence stronger than preference/trend, ownership/revisit trigger, and drift-detection fitness functions.

Do not accept decisions backed only by preference, trend, or unsupported scale claims. Mark needs-validation until evidence and fitness functions are credible.

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.

Versions

  • v0.1.0 Imported from the upstream source.