Wire a shared opt-in rule from /.claude/optionalrules/ into the current project's .claude/rules/ as a symlink. Use when the user says "load the shared rule", "set up shared rule X for this project", "opt in to the skeletons rule", or similar. Takes one argument — the rule name (e.g. skeletons).
Perform a comprehensive code review using multiple specialized sub-agents in parallel. Covers logical correctness, performance, readability, and security. Creates tk tickets if tk is available, otherwise writes a report to .code-review/final-report.md.
Spawn a team of Playwright-driven agents to explore a running web app as simulated users. Supports ad-hoc exploration (routes discovered from source code) and catalog mode (predefined scenarios loaded by name). Uses wave-based execution with agent recycling to prevent context exhaustion. Findings become tk tickets.…
Quick code review using an adversarial sub-agent. Surfaces Critical and High issues first. Creates tk tickets for Critical/High/Medium findings if tk is available.
Execute a tk epic using a DAG-driven agent team with continuous dispatching. Spawns a pool of up to 4 implementers, up to 2 quality reviewers, and 1 AC verifier at startup (sized to the open ticket count, so a single-ticket epic gets 1 + 1 + 1); dispatches tickets as they unblock without wave boundaries. Use when the…
Execute a tk epic using an agent team. Creates implementer, AC verifier, and quality reviewer teammates, dispatches unblocked tickets for parallel implementation, and manages the validation loop. Use when the user says "run epic", "execute epic", "start working on the epic", or similar.
Scaffold a new Go project with a Makefile, golangci-lint, GitHub Actions CI, and two-layer git hooks (pre-commit + pre-push). Use when the user says "set up a new Go project", "scaffold a Go project", "create a new Go CLI", or similar.
Scaffold a new SvelteKit project with Biome, Prettier, Vitest, and GitHub Actions CI. Use when the user says "set up a new JS project", "scaffold a SvelteKit project", "create a new frontend app", or similar.
Scaffold a new Python project with uv, ruff, pytest, and GitHub Actions CI. Use when the user says "set up a new Python project", "scaffold a project", "create a new Python app", or similar.
Turns a rough idea into a structured implementation plan with tk epics and tickets. Asks clarifying questions, produces a phased plan, runs adversarial review via spec-critic, then creates properly-parented and properly-ordered tk epics and task tickets after user approval.
Report a consistent status snapshot for an in-flight /run-epic, /fix-tickets, or DAG variant — the epic/batch progress, every ticket and its state, every agent and what it's doing, and any interesting events from the run so far. Use when the user asks "what's the status", "how's the run going", "what are the agents…
Triage, filter, and sort tk tickets for review. Use when the user asks to review open tickets, sort by priority/type/confidence, triage a backlog, go through P2 bugs, or any similar ticket review workflow. Always use tk triage instead of inline Python/jq for filtering and sorting.
Ship a completed /run-epic or /fix-tickets batch — merge the integration branch to main, prune worktrees, close the epic with a ship note, and report remaining work. Use only when the user types /wrap-epic.