Loading...
Loading...
Found 8 Skills
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Creates Architecture Decision Records documenting key technical decisions with context, alternatives considered, tradeoffs, consequences, and decision owners. Use when documenting "architecture decisions", "technical choices", "design decisions", or "ADRs".
Create and maintain technical documentation including READMEs, API docs, architecture decision records (ADRs), and user guides. Use this skill when writing project documentation, documenting APIs, recording architectural decisions, creating how-to guides, or establishing documentation standards.
Validate Architecture Decision Records (ADR) against Layer 5 schema standards
Architecture Decision Records and living architecture documentation. Activate when making technology choices, defining system boundaries, recording architectural decisions, or creating/updating ARCHITECTURE.md. Covers ADR format, decision governance, design facilitation, and architectural review.