Architecture Decision
Architecture Decision helps you systematically evaluate design choices, document trade-offs, and select appropriate patterns for your context. It provides frameworks for creating Architecture Decision Records, assessing technical debt, and balancing quality attributes like performance, scalability, and maintainability.
Architecture Decision helps you document and record architectural decisions made during system design using structured templates and trade-off analysis.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-02-24
Architecture Decision helps you document and record architectural decisions made during system design using structured templates and trade-off analysis. Architecture Decision helps you systematically evaluate design choices, document trade-offs, and select appropriate patterns for your context. It provides frameworks for creating Architecture Decision Records, assessing technical debt, and balancing quality attributes like performance, scalability, and maintainability.
Use it when
- Architecture Decision provides templates for creating Architecture Decision Records (ADRs) that structure your documentation.
- Architecture Decision establishes a framework for maintaining a log of architectural choices throughout your project lifecycle.
Install
jwynia/agent-skills/architecture-decision · repository language: TypeScript
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I document architecture decisions with Architecture Decision?
Architecture Decision helps you systematically document design choices through structured frameworks. You can create Architecture Decision Records that capture your rationale, trade-offs, and context for each major architectural choice. This ensures your team understands not just what was decided, but why—making it easier to onboard new members and revisit decisions later.
What is an architecture decision record template and how does Architecture Decision use it?
Architecture Decision provides templates for creating Architecture Decision Records (ADRs) that structure your documentation. These templates guide you through capturing the decision context, alternatives considered, chosen solution, and trade-offs involved. By using a consistent template, Architecture Decision ensures all architectural choices are documented uniformly across your project.
How can Architecture Decision help me track design decisions over time?
Architecture Decision establishes a framework for maintaining a log of architectural choices throughout your project lifecycle. This decision log becomes a historical record showing how your system design evolved, what alternatives were rejected and why, and how trade-offs between quality attributes like performance and maintainability were resolved. This preserves architectural reasoning for future reference.
How does Architecture Decision help balance architectural trade-offs?
Architecture Decision helps you systematically evaluate and document trade-offs when selecting design patterns. It guides you through assessing how different choices impact quality attributes such as performance, scalability, and maintainability. By making these trade-offs explicit and recorded, your team can make informed decisions aligned with your system's actual requirements.
Can Architecture Decision help communicate architectural choices to my team?
Yes. Architecture Decision provides structured documentation that communicates not only what architectural choices were made, but also the context and justification behind them. This framework makes it easier for team members to understand design decisions, reduces miscommunication about system architecture, and creates a shared reference for architectural reasoning across your project.
How does Architecture Decision support architectural decision making?
Architecture Decision offers a systematic framework for the entire decision-making process. It helps you document trade-offs, assess technical debt implications, and select appropriate patterns for your specific context. By providing structure and guidance, Architecture Decision ensures your architectural decisions are well-reasoned, traceable, and aligned with your system's quality attributes and business goals.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Document and record architectural decisions made during system design”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
System Design helps you translate validated requirements into sound architecture by diagnosing common pitfalls: missing requirements clarity, under- or over-engineering, overlooked integration points, and unexamined risky decisions. Work through six diagnostic states to identify where your design thinking breaks down, then apply targeted interventions—data flow mapping, component identification, integration checklists, and architecture decision records—to reach a validated design ready for implementation.
Senior Architect guides system design through structured phases: requirements analysis, architecture evaluation, and decision documentation. It produces Architecture Decision Records, trade-off analyses, and scalability blueprints grounded in proven patterns.
This skill structures architecture decisions by enforcing a rigorous trade-off analysis: context, constraints, at least three viable options, and explicit consequences. It produces formal decision records (ADR/RFC/RFD) that capture both positive and negative outcomes, ensuring decisions remain auditable and reversible.
Architecture Designer guides you through system design from requirements to documented decisions. It creates architecture diagrams, evaluates technology trade-offs, and produces Architecture Decision Records for key choices. Use it to structure microservices, plan scalability, and validate designs with stakeholders.
Requirements Analysis guides you through discovering actual problems versus assumed solutions, clarifying vague needs into testable requirements, and surfacing hidden constraints before they derail your project. It provides diagnostic states, targeted questions, and structured exercises to move from solution-first thinking to validated requirements.
This skill guides you through GitHub-driven agile setup and troubleshooting, from CLI installation through backlog management and pull request discipline. It helps you establish healthy practices around issues, branches, and context preservation—ensuring your work stays traceable and your team stays aligned.
More skills architecture (Apache-2.0) · architecture (MIT)