Analyzes requirements and trade-offs to document architectural decisions.
npx skills add https://github.com/Durannd/skills --skill architecture-durannd
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/Durannd/skills/tree/main/skills/architecture Command: npx skills add https://github.com/Durannd/skills --skill architecture-durannd
This Skill provides a comprehensive framework to analyze, evaluate, and document architectural decisions, ensuring systematic and well-informed system design.
Use the architecture skill to evaluate trade-offs in choosing between microservices and monolith architecture for a new project.
High-intent search queries and answers about installing and using this skill.
To document system design decisions, you analyze project constraints, evaluate architectural trade-offs like microservices versus monoliths, and record the justification in an Architecture Decision Record to ensure traceability and accountability.
An Architecture Decision Record (ADR) is a document capturing software design choices, their trade-offs, and constraints. You need it when making significant technology selections or deployment pattern choices to maintain clarity for future reference.
Analyze requirements by gathering system constraints and evaluating scalability needs, then compare microservices and monolith options by documenting their specific pros and cons to justify your architectural selection.
Yes, you can use this framework for deployment strategy decisions and technology selection. It facilitates systematic decision-making by aligning your technology choices and deployment patterns with project constraints.
Systematic architecture decision-making frameworks require thorough requirements analysis and trade-off evaluation upfront. Limitations include the time investment needed to document decisions and the necessity of having clearly defined project constraints before evaluating options.
Evaluating architectural trade-offs helps with system design accountability by ensuring every technology and pattern selection is well-justified, traceable to project constraints, and documented for future revisiting and clarity.
dallenpyrahConduct five-question interviews to explore problem spaces and define constraints.
FleronGenerate engineering implementation plans with tasks, dependencies, and assignments.
htafollaCreates system blueprints and plans technology selections for software architecture projects.
MinhHoangDonoAnalyze technical requirements and produce system design recommendations with trade-offs.
