Loading...
Loading...
Found 122 Skills
Create and maintain Architecture Decision Records (ADRs) in git repos. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; or enforce ADR conventions (status, dates, links, and filenames) for markdown decision logs.
Review code changes against accepted ADRs for compliance violations
Build or rebuild the ADR index and dependency graph in AgentDB
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Technical specification and design document expert. Use when writing design docs, RFCs, ADRs, or evaluating technology choices. Covers C4 model, system design, and architecture documentation.
Crea documentos técnicos organizados en /docs (specs, planes, ADRs, referencias). Usa cuando el usuario diga "crear documento", "escribir spec", "documentar esto", "creame una spec", "escribime documentación", "hacer documentación", o quiera agregar documentación al proyecto.
Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.
Execute Preflight phase for /itp:go workflow. TRIGGERS - ADR creation, design spec, MADR format, preflight verification.
Session log provenance tracking. TRIGGERS - who created, trace origin, session archaeology, ADR reference.
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
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.