architecture-decisioning
Guides the selection and documentation of architectural decisions using ADR patterns.
Best use case
architecture-decisioning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guides the selection and documentation of architectural decisions using ADR patterns.
Teams using architecture-decisioning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-decisioning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-decisioning Compares
| Feature / Agent | architecture-decisioning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guides the selection and documentation of architectural decisions using ADR patterns.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Architecture Decisioning Skill When a significant design choice must be made, use this skill to weigh options and document the decision clearly. ## Steps 1. **State the context.** Summarise the problem or requirement driving the decision. Reference relevant sections of `ARCHITECTURE.md` and other docs that impose constraints. 2. **Identify options.** List the viable alternatives. For each, describe the approach, including technologies, patterns and how it satisfies the requirements. 3. **Evaluate trade‑offs.** Compare the options against criteria such as complexity, performance, scalability, security, maintainability and alignment with existing architecture. Note pros and cons. 4. **Recommend a decision.** Select the option that best meets the criteria. Explain why it is preferred and address why other options were rejected. 5. **Document the decision.** Create or update an Architecture Decision Record (ADR) in a dedicated directory (e.g. `docs/adr/`). Include context, decision, consequences and links to relevant discussions. Ensure the ADR is referenced in `ARCHITECTURE.md`. 6. **Communicate and review.** Share the ADR with stakeholders for feedback. Incorporate suggestions and finalise. Make sure the decision is reflected in subsequent plans and implementations. Thoroughly documented decisions foster transparency and ease future maintenance or revisiting when requirements change.
Related Skills
architecture
Comprehensive system architecture design and implementation workflow that orchestrates expert analysis, technical decision-making, and architectural pattern selection using the integrated toolset. Handles everything from initial system analysis to implementation-ready technical specifications.
architecture-workshop
Framework for designing new architectural mechanisms when existing patterns don't fit
architecture-validator
Validate hexagonal architecture (Domain, Application, Infrastructure, Presentation). Use when creating new files in src/, reorganizing code, or when the user requests architecture validation.
architecture-validation
Dynamically validate codebase compliance with architectural decisions and constraints
architecture-to-json
Guide for extracting architectural diagrams, flowcharts, and sequence diagrams into a structured JSON format. Use this skill when you need to transform a visual or textual description of a system architecture or workflow into a clear, structured JSON representation.
architecture-tech-lead
This skill should be used when the user asks to 'review my architecture', 'improve testability', 'refactor for testing', 'reduce mocking in tests', 'too many mocks', 'extract pure functions', 'functional core imperative shell', 'design a feature', 'evaluate approaches', 'make code more testable', 'domain modeling', 'DDD design', 'bounded contexts', 'too much coupling', or needs architectural validation for Java/Spring Boot or TypeScript/Next.js codebases. Use for design decisions, not implementation.
architecture-synthesis
Generate a reference architecture specification from analyzed frameworks. Use when (1) designing a new agent framework based on prior art, (2) defining core primitives (Message, State, Tool types), (3) specifying interface protocols, (4) creating execution loop pseudocode, or (5) producing architecture diagrams and implementation roadmaps.
architecture-strategist
Use this agent when analyzing code changes from an architectural perspective, evaluating system design decisions, or ensuring changes align with established architectural patterns. Triggers on requests like "architecture review", "design evaluation", "system architecture analysis".
architecture-status
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).
architecture-spec
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure. Use when creating ARCHITECTURE.md or designing system architecture.
architecture-selection
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.
architecture-reviewer
Review software architecture for SOLID principles, design patterns, scalability, and maintainability. Use when evaluating system design or planning refactoring.