Write A Rubric
Produce a gradeable rubric file from an issue, PRD, or free-form goal — sharpened to the standard required by Anthropic''s Managed Agents user.define_outcome event. Sidecar artifact (issues/NNN-*.rubric.md or rubrics/SLUG.md); does not modify source files. Use when the user wants to define "what done looks like" for grader-checkable success criteria. Triggers: /write-a-rubric, "write a rubric", "…
Grill With Docs
Stress-test a plan, design, or idea against the project''s domain language (CONTEXT.md) and recorded decisions (docs/adr/). One question at a time, walks the decision tree, captures crystallized terminology and decisions inline. THIS IS THE DEFAULT GRILLING SKILL — use for any interrogation in a real project, even if CONTEXT.md or docs/adr/ don''t exist yet (they get created lazily on first term…
Tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Work Issues
Autonomously work one task from an issues/ queue end-to-end — explore, implement (TDD when applicable), run feedback loops, commit, update the issue file. Step 3 of the build pipeline (write-a-prd → prd-to-issues → work-issues). Heavyweight (commits code, modifies the issue queue). Use only when explicitly asked: /work-issues, "work the issue queue", "run an AFK iteration", "do one issue end-to-e…
Write A Spec
Turn an approved story (issues/NNN-*.md) plus an optional research dump into a technical spec sidecar at issues/NNN-*.spec.md — data model, API, file-by-file change list per lane (as fenced ```paths blocks), behavior-list of tests required, and risks. The spec drives /feature''s lane allowlist; lane H3 headings must match labels from CLAUDE.md ## Lane boundaries. Sidecar only — does not modify so…
Prototype
Build a throwaway prototype to flush out a design before committing. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it",…
Agent Loop
Goal-driven loop harness. Subcommands — init (build the 7-file harness in this repo), new (interview → goal spec), run (plan→act→verify iterations; plans await human approval), approve/reject (act on a pending plan), status (loop health), doctor (harness health), watch (live dashboard), canonize (promote memory to vault). Slash-only.
Adversarial Review
Three parallel reviewer agents find contradictions, config gaps, and coverage holes across a project''s docs, config, and tests — then fix what you approve. Heavyweight (dispatches parallel agents, can modify files). Supports env-var automation hooks (ADVERSARIAL_REVIEW_TARGETS, ADVERSARIAL_REVIEW_REPORT_ONLY) so an orchestrator can dispatch a programmatic validator pass without keyboard. Use onl…
Feature
Orchestrate the full agentic-engineering chain on one brief — map → research → story → spec → rubric → backend lane → validator → frontend lane → final validator → PR — with three human checkpoints (story, spec+rubric, PR). Default path is in-conversation: each step runs as a forked Agent subagent so output is visible inline and per-step model selection is possible (Haiku for read-heavy steps, So…
Crap
Rank functions by CRAP score (complexity × lack of real test coverage) on the current branch, then propose either a refactor or missing tests for the worst offender. Use when the user runs /crap or asks to find risky, complex, poorly-tested code.
Map
Generate or update ARCHITECTURE.md — a living map of a project''s structure, dependencies, and high-coupling zones. Polyglot-adaptive. Heavyweight (writes ARCHITECTURE.md, dispatches parallel agents). Use only when explicitly asked: /map, "generate ARCHITECTURE.md", "map this codebase", OR when another orchestrator skill (e.g. /feature step_refresh_map) needs to dispatch it programmatically.
Diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when the user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Forge
Agent orchestration for Claude Code — intelligent routing, pattern learning, memory, and team coordination
Zoom Out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Audit Agent Overhead
Audit an agent setup (global ~/.claude AND project .claude AND plugin scope) for the 9 token-waste patterns that silently inflate cost and burn through usage limits. Outputs a per-pattern score against thresholds and proposes specific fixes — applied only with user approval. Heavyweight (~5KB SKILL.md + audit script); explicit invocation only. Triggers: /audit-agent-overhead, "audit my agent setu…
Grill Me
Pure socratic interrogation with NO project artifacts at all — no codebase, no CONTEXT.md, no ADRs to reference. One question at a time, walk the decision tree, recommend an answer for each branch. Rare edge case — most grilling happens inside a project, so use grill-with-docs by default (it handles the no-CONTEXT.md case by creating one lazily). Use grill-me ONLY when the user is brainstorming e…
Write A Prd
Interview the user and produce issues/prd.md from a client brief, feature idea, or rough request. Step 1 of the build pipeline (write-a-prd → prd-to-issues → work-issues). Use when no PRD exists yet and one is needed. NOT for breaking an existing PRD into tasks (use prd-to-issues), and NOT for tracker-coupled output (this writes local markdown only). Triggers: /write-a-prd, "write a PRD", "draft…
Prd To Issues
Read an existing PRD (typically issues/prd.md, written by write-a-prd) and break it into vertical-slice tracer-bullet issues at issues/NNN-short-title.md, tagged HITL (needs human) or AFK (autonomous). Step 2 of the build pipeline (write-a-prd → prd-to-issues → work-issues). Use when a PRD exists and needs to become work tickets. NOT for writing the PRD itself (use write-a-prd). Triggers: /prd-to…
Evolve
Run an ASI-Evolve style evaluator-driven search workflow for code, algorithms, prompts, or pipelines. Use when Claude needs to align the objective, scoring, evaluator, writable scope, and cognition first, then execute a preflight-gated learn/design/experiment/analyze loop with the bundled Evolve CLI instead of the repository's multi-agent pipeline.