Loading...
Loading...
Found 6 Skills
Write Architectural Decision Records following MADR template. Applies Definition of Done criteria, marks gaps for later completion. Use when generating ADR documents from extracted decisions.
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".
Generates Architecture Decision Records (ADRs) capturing context, decision rationale, alternatives considered, and projected consequences. Produces numbered, status-tracked documents following the standard ADR format with proper metadata lifecycle. Triggers on: "write an ADR", "document this decision", "architecture decision record", "why did we choose", "capture this decision", "record the decision", "ADR for", "document the architecture", "decision record", "design decision", "technical decision". Use this skill when an architectural or technical decision needs to be documented.
Use this skill when writing, reviewing, or structuring technical documentation for software projects. Triggers on API documentation, tutorials, architecture decision records (ADRs), runbooks, onboarding guides, README files, or any developer-facing prose. Covers documentation structure, writing style, audience analysis, and doc-as-code workflows for engineering teams.
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.
Document architectural decisions. Use when making significant technical decisions that should be recorded. Covers ADR format and decision documentation.