{"enrichment":{"faq":[{"a":"architecture-decision structures your documentation by capturing context, constraints, at least three viable options, and explicit trade-offs. It enforces a rigorous format\u2014similar to ADR (Architecture Decision Record) or RFC templates\u2014that records both positive and negative consequences. This ensures decisions remain auditable, reversible, and justified for future teams reviewing why a choice was made.","q":"How do I document architecture decisions?"},{"a":"architecture-decision uses a structured template that includes: the decision's context and constraints, multiple architectural options evaluated side-by-side, a trade-off analysis comparing reliability, scalability, cost, and maintainability, and documented consequences (both positive and negative). This format makes it easy to compare approaches and understand why one was selected over alternatives.","q":"What format should an ADR template for design choices follow?"},{"a":"architecture-decision provides a trade-off matrix framework to evaluate critical factors: reliability, scalability, cost, and maintainability. For SQL vs NoSQL, you'd document constraints (consistency vs availability needs), list both options plus at least one hybrid approach, then explicitly compare each on your key criteria. This structured comparison captures trade-offs and consequences for each choice.","q":"How can I compare database options like SQL vs NoSQL?"},{"a":"architecture-decision requires you to record context (why the decision matters), constraints (what limits your options), at least three viable approaches, and explicit consequences\u2014both positive outcomes and negative trade-offs\u2014for each option. This comprehensive capture ensures stakeholders understand what was gained and lost, making decisions transparent and reversible if circumstances change.","q":"What should I include when documenting design trade-offs?"},{"a":"architecture-decision enforces a rigorous evaluation process: define your constraints upfront, present multiple options (minimum three), then systematically compare them using a trade-off matrix covering reliability, scalability, cost, and maintainability. By documenting both positive and negative consequences, you create a formal decision record (ADR/RFC/RFD) that justifies your choice and remains auditable for future reference.","q":"How does architecture-decision help evaluate architectural options?"},{"a":"Yes. architecture-decision applies to any architectural decision\u2014infrastructure, technology, or design. Whether comparing cloud providers, container orchestration platforms, or deployment strategies, the skill guides you through the same structured process: context, constraints, multiple options, trade-off analysis, and documented consequences. This ensures infrastructure decisions are as well-justified and auditable as any other architectural choice.","q":"Can architecture-decision be used for infrastructure choices?"}],"shadow_tags":["decision-framework","trade-off-analysis","design-documentation","options-evaluation","constraint-driven","consequence-mapping","decision-history","architecture-governance","option-comparison"],"summary_rewrite":"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."},"files":[{"bytes":3949,"path":"app/skills/architecture-decision/SKILL.md","sha256":"dc29d15d78face096672ff2acbc7adb7594e41cebabc60b6ffc76d47a812052d","url":"https://skillfed.io/files/softspark/ai-toolkit/architecture-decision/cbde000e/SKILL.md"}],"id":"softspark/ai-toolkit/architecture-decision","links":{"html":"https://skillfed.io/softspark/ai-toolkit/architecture-decision","md":"https://skillfed.io/softspark/ai-toolkit/architecture-decision.md","repo":"https://github.com/softspark/ai-toolkit"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":21,"language":"Python","last_updated":"2026-07-27","license":"Apache-2.0","name":"architecture-decision","publisher":"softspark","stars":161},"relations":{"categories":["architecture","design-systems","technical-governance"],"similar":[{"id":"tech-leads-club/agent-skills/create-adr"},{"id":"wshobson/agents/architecture-decision-records"},{"id":"jwynia/agent-skills/architecture-decision"},{"id":"dawiddutoit/custom-claude/create-adr-spike"},{"id":"Jeffallan/claude-skills/architecture-designer"},{"id":"openyak/openyak/architecture"},{"id":"govctl-org/govctl/decision-analysis"},{"id":"softspark/ai-toolkit/architecture-audit"},{"id":"anthropics/knowledge-work-plugins/architecture"},{"id":"existential-birds/beagle/adr-writing"}]},"slug":{"owner":"softspark","repo":"ai-toolkit","skill":"architecture-decision"},"version":"cbde000e"}