Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When making significant architectural decisions, documenting technology choices, recording design trade-offs, reviewing historical decisions, or establishing decision-making processes.
Standardized, traceable ADR documents that capture rationale, enable onboarding, and support future architecture reviews with low overhead.
Use Cases
A tech lead needs to choose a primary database for a new platform. Using this skill, they apply the MADR template to document context, considered options (PostgreSQL/MySQL/MongoDB), decision drivers, and consequences. The ADR is stored in docs/adr and indexed, giving the team a clear, reviewable record that prevents repeated debates and aids future maintenance.
An architect reviews a 2021 ADR that chose MongoDB and finds it outdated. Using the deprecation template, they write a superseding ADR with migration plan and lessons learned. This formally retires the old decision, aligns the team, and provides a pattern for future technology changes with managed risk.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
