sdlc

Record architecture decisions by updating ARCHITECTURE.md directly and creating PRs whose descriptions serve as the ADR.

Mark a task as complete. Closes the task and commits .dots/ changes on the current branch.

Design event model workflows following Martin Dilger's "Understanding Eventsourcing" methodology and Adam Dymitruk's Event Modeling approach. Event modeling is about **understanding the business domain**, not documentation. The AI facilitates by asking probing questions, challenging assumptions, and keeping focus on business behavior - not technical implementation.

INVOKE to review domain types for primitive obsession, invalid state representability, or safety gaps

INVOKE when event model slices are ready. Creates dot tasks from slices

INVOKE when ready to create PR. Runs three-stage code review and mutation testing

INVOKE before ANY task to check for existing solutions in auto memory

INVOKE after solving problems or learning conventions. Stores in auto memory

INVOKE when PR has review comments to address. Fetches and responds to feedback

INVOKE once per project to configure SDLC workflow and install gh extensions

INVOKE for ALL file operations. Orchestrator delegates to agents, never writes directly

INVOKE to begin work. Auto-detects project state and routes to appropriate phase

INVOKE to start or continue work on an issue. Shows ready items, creates branch

INVOKE to record architecture decisions. Updates ARCHITECTURE.md and creates ADR PRs

INVOKE when reviewing technical complexity, risks, or architectural alignment

INVOKE before PRs and after major implementation. Three-stage review (spec, quality, domain)

INVOKE after event modeling to guide architecture decisions. Creates ADRs and ARCHITECTURE.md

INVOKE at project start for broad domain understanding. Identifies workflows to model

INVOKE for type definitions. TYPE DEFINITIONS ONLY. Has VETO POWER over domain violations

INVOKE for config, docs, or scripts. Handles files outside TDD agent scope

INVOKE for ALL production code changes. PRODUCTION CODE ONLY. Minimal implementation

INVOKE to generate GWT scenarios for event model slices. Creates acceptance criteria

INVOKE to validate event model completeness. Checks information flow and GWT coverage

INVOKE before PR creation. Enforces 100% mutation score, reports surviving mutants

INVOKE for ALL test file changes. TEST CODE ONLY. One assertion per test

INVOKE when reviewing story value and slice independence. Business perspective reviewer

INVOKE when reviewing user journey coherence, accessibility, or interaction design

INVOKE to design a workflow using 9-step event modeling. Creates wireframes and slices

One-line description of what this skill teaches

Brad Frost's Atomic Design methodology for building UI component hierarchies

Systematic 4-phase debugging methodology for finding and fixing root causes

Event Modeling facilitation methodology for event-sourced system design

Knowledge accumulation and retrieval patterns for file-based agent memory

Multi-agent orchestration patterns for delegation, coordination, and conflict resolution

Local task management using the dot CLI with file-based markdown storage, parent-child hierarchies, and blocking dependencies. Use when managing tasks, creating stories or epics, tracking work items, breaking down features, writing acceptance criteria, or querying task status. Triggers on: "create a task", "add a story", "break down this feature", "what's ready to work on", "show task status", "dot add", "dot ls", "dot ready", "dot tree", or any reference to the dot CLI or .dots/ directory.

Red-green-domain TDD cycle with strict phase boundaries and domain modeling review

Pattern for subagents to request user input when AskUserQuestion is unavailable

7 hooks across 5 events