Capture architectural decisions with ADR templates and rationale.
npx skills add https://github.com/boomNDS/soop-discoard-bot --skill architecture-boomnds
Please help me install this Agent Skill. Skill: architecture Source: https://github.com/boomNDS/soop-discoard-bot/tree/main/.agents/skills/architecture Command: npx skills add https://github.com/boomNDS/soop-discoard-bot --skill architecture-boomnds
This skill provides a structured approach to capturing architectural decisions and their rationale via Architecture Decision Records (ADRs), enabling traceable design choices across projects.
Create your first ADR-001 describing the problem, constraints, and the chosen approach. Then document options and expected consequences.
High-intent search queries and answers about installing and using this skill.
An Architecture Decision Record (ADR) documents context, options, decisions, and consequences for software design. You need ADRs to establish traceability and structured rationale when capturing architectural choices across a project lifecycle.
To document architecture trade-offs, use structured ADR templates to record context and compare design patterns. This framework provides trade-off analysis guidance to compare alternatives, justify technology selection, and capture expected consequences.
The best way to start writing an ADR is to create ADR-001 describing the problem, constraints, and chosen approach. Document the design options analyzed and expected consequences to enforce context recording and traceability.
Yes, you can use ADRs to align teams and maintain a design history for modularization. This framework enforces collaboration and traceability by applying ADR templates to record rationale for technology selection and system design.
Yes, this architecture framework works standalone without external dependencies. It enforces ADR templates and pattern selection guidance directly, providing structured decision documentation for software projects needing traceable design choices.
You should not use informal documentation because it lacks traceability and structured rationale. ADRs enforce context recording, trade-off analysis, and pattern selection guidance, ensuring architectural decisions remain aligned and traceable across the project lifecycle.
FoundationForgeCreate and evaluate Architecture Decision Records with structured context and trade-offs.
rickardpReplace or deprecate ADRs while preserving decision history and rationale.
clawpod-appDocument Architecture Decision Records with context, options, and trade-offs.
senior-siganCapture architectural decisions as structured ADR documents with context and rationale.
