Create or evaluate Architecture Decision Records with trade-off analysis.
npx skills add https://github.com/pgm1980/stryker-netx --skill architecture-pgm1980
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/pgm1980/stryker-netx/tree/main/.claude/skills/architecture Command: npx skills add https://github.com/pgm1980/stryker-netx --skill architecture-pgm1980
It helps you capture important architecture decisions in a consistent, reviewable format so teams can align on trade-offs and avoid repeating past debates.
Ask for an ADR by requesting: "Create an ADR deciding between Kafka and SQS for our event bus, including context, options, trade-offs, consequences, and action items."
High-intent search queries and answers about installing and using this skill.
Architecture Decision Records document system design decisions by capturing context, options considered, and consequences. They help teams align on technology trade-offs and avoid repeating past architecture debates in a consistent, reviewable format.
Create an ADR when choosing between competing architectures, reviewing design proposals, or drafting new components from requirements. ADRs are needed to explicitly document trade-offs, risks, costs, scalability concerns, and team fit for important technology adoption decisions.
Structure trade-off analysis by evaluating competing architecture options with explicit assessments of risks, costs, and scalability concerns. Produce a structured record covering context, decision, options, trade-offs, consequences, and action items to review design proposals.
Yes, evaluating design proposals with an ADR highlights risks, costs, scalability concerns, and team fit. The structured format prompts requirement and constraint-driven analysis that produces an actionable decision record for system design discussions.
An Architecture Decision Record should include context, decision, options with assessments, trade-off analysis, consequences, and action items. It optionally guides follow-ups based on connected connectors to support system design discussions.
aget-frameworkEvaluate architectural options against quality attributes and reversibility.
dipandhali2021Coordinate structured sprint retrospectives using Start-Stop-Continue, Mad-Sad-Glad, or 4Ls formats.
AIMFllysConvert requirements into justified architecture decisions with ADR documentation.
jc180105Design scalable software architectures with ADR-style decision documentation.
