Loading...
Loading...
Found 318 Skills
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Execute Preflight phase for /itp:go workflow. TRIGGERS - ADR creation, design spec, MADR format, preflight verification.
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
Create an Architecture Decision Record (ADR) in canonical MADR v4 format capturing the why behind a significant technical choice. Use when user says 'document this decision', 'create an ADR', 'record architecture decision', 'why did we choose X', 'document the rationale', or when adding major dependencies, new frameworks, or changing fundamental patterns. Do NOT use for user-facing feature docs (use document-feature) or syncing existing docs (use update-doc).
Write, edit, or review chapters of an arc42 architecture documentation. Use when user says 'write arc42', 'update the architecture documentation', 'fill out chapter 5', 'arc42 chapter', 'architecture docs', or 'document our building blocks'. Do NOT use for ADRs (use document-decision — ADRs belong inside arc42 chapter 9) or user-facing feature docs (use document-feature).
Revisa de forma adversarial un Technical Design Document y sus ADRs, buscando activamente huecos, riesgos y decisiones débiles en vez de validarlos. Use when the user asks to challenge, stress-test, get a second opinion on, or adversarially review a technical design document, architecture decisions, or ADRs.
System architecture design for Rust/WebAssembly projects. Creates ADRs, designs APIs, plans module structures, and documents architectural decisions. Never writes implementation code - focuses purely on design and documentation.
Documentation-as-code conventions for team repos. Defines a docs/ taxonomy (ADR, RFC, guide, system, incident, audit), naming rules, templates, and boundaries. Use when creating, moving, or organizing documentation files.
Create and manage Architecture Decision Records (ADRs) using MADR 4.0.0 format. Use this skill when evaluating technology choices, documenting design decisions, or reviewing past architectural choices.
Guide for creating effective internal technical documentation (READMEs, ADRs, Contribution Guides). Use this skill when the user asks to write, refactor, or improve internal project documentation.
Principal Solution Architect with 15+ years designing scalable distributed systems. Use when making technology choices, designing system architecture, selecting patterns (Saga, CQRS, Event Sourcing), creating ADRs, planning integrations, or addressing scalability concerns.