Loading...
Loading...
Found 387 Skills
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.
Specializes in generating Action-Domain-Responder (ADR) boilerplate for Gravito projects. Trigger this when adding new features or modules using the ADR pattern.
Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or `spec-loop-plan-task` routes ADR writing.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision. Follows the standard ADR format with context, decision, and consequences. Invoked when the user says "write an ADR", "document this decision", or "create an architecture record".
Create, update, review, and reference architecture decision records (ADRs) in the current git repository. Use when the user asks messy design questions, wants a design doc turned into ADR draft(s), needs existing decisions checked before implementation, wants gaps surfaced before writing an ADR, or wants future sessions to reuse decisions consistently. Inspect repository code and docs first, ask only for missing decision-critical information, then produce or update ADR files using the repo’s ADR conventions or the defaults in references/.
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 new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
Format, numbering, and when-to-write criteria for Architecture Decision Records in docs/adr/. Use when recording an architectural decision, when another skill flags a decision as ADR-worthy, or when the user asks to write or review an ADR.
Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.
Build or rebuild the ADR index and dependency graph in AgentDB
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.