Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Record why an architectural choice was made to prevent agents or humans from unintentionally reverting it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/documentation-systems:architecture-decision-recordsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Code tells you *how* a system works. ADRs tell you *why* it works that way, preventing future maintainers (and AI agents) from suggesting "improvements" that were already tried and discarded.
Share bugs, ideas, or general feedback.
Code tells you how a system works. ADRs tell you why it works that way, preventing future maintainers (and AI agents) from suggesting "improvements" that were already tried and discarded.
When finalizing a major design decision (e.g., "Choosing Postgres over MongoDB", "Using custom event bus over Redis"):
docs/adr/YYYY-MM-DD-<short-title>.md.npx claudepluginhub yeaight7/agent-powerups --plugin documentation-systemsOrchestrates changing an existing working feature to new desired behavior by updating tests first, then implementation, with review and gated commit.