architecture-decision

Create Architecture Decision Records with context, dependencies, and consequences.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill architecture-decision-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/dnkrow/skill/tree/main/claude-global/architecture-decision
Command: npx skills add https://github.com/dnkrow/skill --skill architecture-decision-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

architecture-decision helps teams capture and standardize major technical choices by producing complete Architecture Decision Records (ADRs) with context, alternatives, consequences, engine-specific compatibility, and cross-references to GDD requirements.

Core Features & Use Cases

  • ADR authoring with guardrails: Uses engine reference docs, post-cutoff change checks, and an architecture registry to prevent contradictory decisions.
  • Interactive collaboration and validation: Guides users through assumptions, validates the drafted ADR with an engine specialist (when configured), and runs a strategic technical director review gate.
  • Retrofit mode for existing ADRs: Detects missing ADR sections and appends only absent content without modifying existing text, then re-validates coverage.
  • Registry and dependency synchronization: Optionally updates docs/registry/architecture.yaml after explicit approval, and checks GDD naming consistency before writing.

Quick Start

Run architecture-decision with a title like: event-system-architecture --review lean.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I draft an Architecture Decision Record with engine compatibility and GDD traceability?

Drafting an Architecture Decision Record with engine compatibility and GDD traceability requires parsing review mode, loading engine reference documentation, enforcing architecture registry constraints, and validating specialist and technical director reviews to capture complete technical context.

Can I retrofit missing sections in existing ADR files without modifying the original content?

Yes, retrofit mode detects missing ADR sections and appends only absent content without modifying existing text, then re-validates coverage against engine-specific domains tied to GDD requirements.

What is the best way to prevent contradictory architecture decisions across multiple ADRs?

Preventing contradictory architecture decisions involves using an architecture registry to enforce constraints, checking post-cutoff changes, and optionally updating docs/registry/architecture.yaml after explicit approval to maintain consistency.

Does the ADR authoring process support automated technical director and specialist validation?

Yes, ADR authoring runs specialist and technical director validation gates when configured, guiding users through assumptions and validating drafted ADRs against loaded engine reference documentation before finalizing.

How do I maintain GDD naming consistency when updating the architecture registry?

Maintaining GDD naming consistency when updating the architecture registry requires checking GDD naming conventions before writing, then optionally updating docs/registry/architecture.yaml after receiving explicit approval.