Document architecture decisions using ADRs and structured trade-off analyses.
npx skills add https://github.com/TwuanMinn/fadelab --skill architecture-twuanminn
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/TwuanMinn/fadelab/tree/main/.agent/skills/skills/architecture Command: npx skills add https://github.com/TwuanMinn/fadelab --skill architecture-twuanminn
Architectural decisions often lack a structured reasoning process. This Skill provides a framework to analyze requirements, compare options, document trade-offs, and capture rationale using ADRs.
Draft an Architecture Decision Record for your current design choice, including context, options, and trade-offs.
High-intent search queries and answers about installing and using this skill.
Architecture Decision Records document design choices by capturing context, comparing options, and recording trade-offs. This framework provides ADR templates to structure rationale and ensure architectural decisions are systematically evaluated and traceable.
Evaluating architecture trade-offs involves analyzing requirements against a library of architecture patterns. This framework structures the comparison process, guiding you to weigh options methodically and document the resulting decision records for your project.
Selecting architecture patterns requires mapping project requirements to known design solutions. This framework provides pattern references and example workflows to guide pattern selection, ensuring chosen patterns align with your specific trade-off evaluations.
You need an Architecture Decision Record when a design choice involves significant trade-offs or impacts multiple components. Using ADR documentation captures the reasoning process, preventing undocumented architectural decisions and providing future context.
Yes, you can apply this framework to existing projects by drafting an Architecture Decision Record for current design choices. The structured requirements analysis and trade-off evaluation process adapts to document decisions across various project stages.
Yes, requirements analysis is a core component supported before pattern selection. The framework integrates requirements analysis with trade-off evaluation, ensuring architecture patterns are chosen based on structured project needs rather than assumptions.
ucirelloDefine STPA analysis purpose by identifying losses, hazards, and constraints.
wilsonkichoiGenerate SPEC.md and HANDOFF.md documents from approved Phase 1 research.
MartinNevlahaDesign system architecture and generate ADRs, component diagrams, and interface definitions.
GeargrindadminAnalyze architectural trade-offs and document decisions with ADR templates.
