jwilger
@jwilger
Public Skills
architecture-decisions
by jwilger
Architecture Decision Records with a four-phase lifecycle (RESEARCH → DRAFT → HOLD → MERGE). Activate when making technology choices, defining system boundaries, recording architectural decisions, or creating/updating ARCHITECTURE.md. Enforces research-before-writing and explicit merge authorization.
code-review
by jwilger
Three-stage code review protocol: spec compliance, code quality, and domain integrity. Activate when reviewing code, preparing PRs, assessing implementation quality, or checking that code matches requirements. Triggers on: "review this code", "prepare PR", "check implementation", "code quality", "does this match the spec".
tdd
by jwilger
Adaptive test-driven development cycle. Detects harness capabilities and routes to guided (manual phase control) or automated (orchestrated) mode. Invoke with /tdd for automated or /tdd red domain green commit for guided.
ensemble-team
by jwilger
Set up a full AI ensemble/mob programming team for any software project. Creates team member profiles (.team/), coordinator instructions (.team/coordinator-instructions.md), project owner constraints (PROJECT.md), team conventions (AGENTS.md), architectural decisions (docs/ARCHITECTURE.md), domain glossary, and supporting docs. Use when: (1) starting a new project and wanting a full expert agent team, (2) the user asks to "set up a team", "create a mob team", "set up ensemble programming", or "create agent profiles", (3) converting an existing project to the driver-reviewer mob model, (4) the user wants AI agents to work as a coordinated product team with retrospectives and consensus-based decisions.
design-system
by jwilger
Collaborative design system creation using Atomic Design methodology. Produces a specification artifact with philosophy, tokens, and component hierarchy. Activate when creating a design system, defining visual language, specifying UI tokens, or planning component architecture before implementation begins.
atomic-design
by jwilger
Brad Frost's Atomic Design for UI component hierarchy: atoms, molecules, organisms, templates. Activate when building user interfaces, creating design systems, organizing components, or structuring frontend code. Applies to any UI framework (React, Vue, SwiftUI, etc.).
domain-modeling
by jwilger
Domain modeling principles: parse-don't-validate, make invalid states unrepresentable, primitive obsession detection, semantic types, and domain veto authority. Activate when designing types, reviewing code for domain integrity, or when domain review is needed in a TDD cycle.
pipeline
by jwilger
Autonomous build-phase orchestrator. Manages slice queue, TDD pair dispatch, full-team code review, mutation testing, CI integration, and auto-merge with quality gates. Replaces manual coordinator overhead during build phase. Activate when running factory mode with ensemble-team.
bootstrap
by jwilger
Zero-config SDLC onboarding. Detects project environment, harness capabilities, and harness type. Configures TDD mode, generates AGENTS.md, offers optional enforcement hooks, and recommends skills by phase. Single entry point for all harnesses.
ci-integration
by jwilger
Deterministic CI/CD interaction patterns. Push-and-wait discipline, failure triage, self-healing for lint/format/infra failures, structured output for pipeline consumption. Activate when interacting with CI/CD systems.
task-management
by jwilger
Work decomposition, dependency ordering, and status tracking for software tasks. Activate when breaking down features into tasks, managing work items, tracking dependencies, creating stories or epics, or asking what to work on next. Works with any task tool: harness-native todos, dot CLI, GitHub Issues, or file-based tracking.
memory-protocol
by jwilger
File-based knowledge persistence patterns: when to store discoveries, when to recall past solutions, and how to organize project memory. Activate when starting tasks, encountering errors, making decisions, or when context may be lost between sessions.
user-input-protocol
by jwilger
Structured checkpoint format for requesting human input. When an agent needs a decision, it must stop, present context, show options, and wait. Activate when delegating to subagents, running background tasks, or hitting any decision point that requires human judgment.
mutation-testing
by jwilger
Mutation testing to validate test quality before PR creation. Runs mutation tools, enforces 100% kill rate, reports surviving mutants with recommended fixes. Activate when validating test coverage, preparing pull requests, checking test quality, or when asked about mutation testing.
factory-review
by jwilger
Structures the human review experience for factory-mode builds. Audit trail summaries, PR digests, retrospective synthesis, quality trend tracking, and autonomy tuning interface. Activate during Phase 3 human review.
ticket-triage
by jwilger
Evaluate whether a development ticket (user story, feature request, bug report, etc.) is ready for development, and provide specific, actionable feedback if it is not. Use this skill whenever the user asks to triage, evaluate, assess, review, or check the readiness of a ticket, story, issue, or work item. The ticket can come from anywhere: pasted inline, read from a file, fetched from Jira or another tracker via MCP, or any other source. Also use this when a user asks "is this ticket ready?" or "what's wrong with this ticket?" or wants to improve a ticket's specification.
debugging-protocol
by jwilger
Systematic 4-phase debugging: understand the failure, form hypotheses, test one change at a time, fix with confidence. Activate when tests fail unexpectedly, errors occur, behavior is wrong, or something that worked before is now broken. Triggers on: "debug", "why is this failing", "test failure", "unexpected error", "bug", "broken".
event-modeling
by jwilger
Event modeling facilitation for discovering and designing event-sourced systems. Four phases: domain discovery, workflow design (9-step process), GWT scenario generation, and model validation. Activate when starting a new project, designing features, modeling domains, writing Given/When/Then scenarios, or discussing event sourcing and domain-driven design.