skills

Bootstrap software repositories from live evidence. Use for initial setup, inherited-codebase rehabilitation, repository mapping, conventions, documentation architecture, safe restructuring, or agent-ready tooling.

Solve ambiguous, high-stakes, or multi-variable questions with a labelled problem tree. Use for open-ended life, business, product, strategy, and root-cause reasoning; route concrete feature briefs to $grill-me and specific failures to $debugging.

Diagnose software failures through evidence-based root-cause analysis. Use for bugs, failing tests, runtime errors, data anomalies, stuck jobs, environment failures, and intermittent or expensive-to-reproduce incidents.

Create, edit, and run persistent Codex workflow graphs with optional GitHub delivery.

Turn a rough software feature request into one codebase-grounded implementation brief. Use for feature pitches, vague product requirements, solution exploration, or explicit “grill me” requests before coding; use $brainstorming for non-implementation questions.

Implement an agreed story, plan, or failing-test target and prove the resulting behavior. Use when an accepted contract authorizes production changes; route diagnosis-only work to $debugging and test design to $tdd.

Land finished work in a Git repository through Gate, Record, Commit, and Publish. Use when the user asks to close completed work, commit and push it, or open a pull request; use repository review workflows for reviewing an existing PR.

Slice an agreed plan into an epic and behavior-focused stories with observable acceptance criteria, reconciled against repository-owned domain rules.

Reconcile durable documentation with implemented behavior. Use for read-only code-versus-doc audits, completed-plan folding, or authorized post-implementation documentation updates; report descriptive drift and escalate binding-rule contradictions.

Test-first an agreed behavior by enumerating its contract and producing meaningful failing tests; hand a proved red contract to $implement.

Coordinate multiple Git worktrees with explicit ownership and isolated runtime state. Use when concurrent agents or tasks create, inspect, test, debug, compare, integrate, or clean worktrees whose branches, ports, databases, containers, caches, or logs could collide.

Audit and improve skills for predictable invocation and execution.