Loading...
Loading...
Found 18 Skills
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. 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 types: 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 push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
Guide architectural design decisions for software systems. Use this skill when designing new systems, evaluating architecture trade-offs, or creating technical design documents. Helps produce clear, well-structured design artifacts including component diagrams, data flow, and decision records.
Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.
Create a new Architecture Decision Record in doc/adr/
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.
Creates agent-optimized technical design documents with context-layer-aware progressive disclosure for architecture decisions, component design, and data models. Use when writing technical designs, architecture docs, defining system components, or making technology choices for spec-driven development.