technical-design
dirkkok101Bridge from PRD or brainstorm to implementation plan. Produces architecture diagrams, sequence diagrams, data models, API specifications with .NET/C# patterns (MediatR CQRS, EF Core, AutoMapper, FluentValidation), UI wireframes, and integration patterns. Use when user says "design the system", "create technical spec", "API design", "architecture", or after PRD approval. Always use this before /plan for anything beyond simple changes.
prd
dirkkok101Generate a formal Product Requirements Document from brainstorm output or from scratch. Produces user personas, use cases, functional requirements as user stories with acceptance criteria, non-functional requirements, and MoSCoW prioritization. Use when starting a business feature that needs requirements documentation, when user says "write requirements", "create PRD", "define user stories", or after brainstorm approval for business features.
beads
dirkkok101Convert approved plans into intent-based beads with self-assessment gate. Each bead is a work package for a sub-agent that loads surgical context to implement. No source code in beads.
execute
dirkkok101Execute approved beads using sub-agent model. Each bead is a work package - agent loads surgical context, designs, implements, and verifies. Continues until feature complete.
diagnose
dirkkok101Systematic root cause analysis for bugs and unexpected behavior. Investigates, isolates, and either fixes simple issues directly or escalates to appropriate workflow.
docs-write
dirkkok101Generate and update documentation using templates for any Diataxis type (tutorial, howto, reference, explanation), AI files (CLAUDE.md, AGENTS.md, llms.txt), architecture docs (C4 context/container, system overview, Mermaid diagrams), and project files (README, CONTRIBUTING, glossary). Template-driven with idempotent updates that preserve custom sections. Use when creating or updating documentation. Triggers on "write docs for", "create a tutorial", "document the API", "generate README", "create AGENTS.md", "write architecture overview".
docs-audit
dirkkok101Analyze documentation health for existing codebases. Detects structure, applies Diataxis gap analysis, checks AI-friendliness (CLAUDE.md, AGENTS.md, llms.txt), and scans for staleness. Use when joining a project, assessing documentation quality, or before a major documentation effort. Triggers on "review my docs", "what docs are missing", "audit documentation", "check doc health".
compound
dirkkok101Capture learnings from feature development to make future work easier. Called after review cycles during execute phase. Each call captures one focused learning.
research
dirkkok101Deep research phase that produces a structured research brief before brainstorming or PRD creation. Use this skill when starting a new feature that needs competitive analysis, technical landscape review, or stakeholder research before designing. Trigger when user says "research this", "what's out there for", "investigate options for", or before any major new initiative.
docs-adr
dirkkok101Record architectural decisions using MADR templates with full lifecycle support (Proposed, Accepted, Deprecated, Superseded). Supports full, minimal, and bare template variants. Use when making or recording architectural decisions, documenting technology choices, or capturing decision rationale. Triggers on "record this decision", "create an ADR", "document why we chose", "capture rationale".
brainstorm
dirkkok101Transform rough ideas into validated designs through deep understanding, research, and documentation synthesis. Designs become permanent project documentation.
plan
dirkkok101Transform validated designs into hierarchical implementation plans that serve as permanent documentation. Plans contain intent, pseudocode, and diagrams - never source code. Requires design approval.
review
dirkkok101Multi-perspective code review using parallel agents. Consolidates findings by severity for user approval. Use when implementation is complete (/execute finished), user says "review", "code review", or "check the code", before creating a PR, or after significant changes.