Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. Manual: when the user wants to create, modify, evaluate, or optimize a skill.
Build and sharpen a project's domain model during design: map bounded contexts, test precise concept boundaries with edge cases, compare stated behavior with code, surface contradictions, and write the glossary as terms crystallize. This is the write-side counterpart to /decision-mapping; use it when the model changes, a ubiquitous language needs definition, a bounded context needs naming, or an architectural decision needs an ADR. Triggers on: 'domain model', 'ubiquitous language', 'bounded context', 'context map', 'glossary', 'name this concept', 'model the domain', 'is this term right', and 'write an ADR'. Also triggers when a design reuses a fuzzy term, a subsystem needs a context boundary, or stated behavior and code disagree about a concept. Pairs with /decision-mapping, /spec, and /recon. Manual: /domain-modeling [topic].
Run an adversarial generator-evaluator loop for high-stakes implementation tasks. A generator produces output and a different-model-family evaluator tests it against criteria using adversarial framings. Continue until Stage A passes and Stage B has no CRITICAL findings, or a convergence signal fires twice and escalates. Rework failures with evaluator feedback; use --competitive N for multiple candidates. MANDATORY when an active spec phase has `Harness: yes` and implementation is about to begin; run /harness --from-spec. Triggers on: 'run the harness', 'gen-eval loop', 'adversarial loop', 'iterative review', 'harness this', 'competitive mode', 'run N candidates', 'evaluator feedback', and 'cross-model implementation review'. Also triggers when /verify Deep finds second-pass failures, high-stakes work needs iterative review, /codex-review reports BLOCKING findings, or the user invokes the harness. Pairs with /codex-review, /spec, /verify, and /best-of-n. Manual invocation supports ad-hoc use.
Make a repository presentable for public release: restructure files to ecosystem conventions, generate a first-person README with progressive disclosure, add missing root files such as LICENSE, .gitignore, and CONTRIBUTING, and run a privacy sweep with history scrubbing. Complete one audit-then-fix pass and humanize generated prose at the end. Triggers on: 'polish', 'make presentable', 'clean up this repo', 'prepare for open source', 'make the README better', 'repo restructure', 'README generation', 'open source readiness', 'public repo cleanup', and 'professionalize this repo'. Also triggers when a user wants a repo to look professional, requests README/LICENSE/.gitignore generation, or prepares to publish or open-source a repo. Pairs with /humanizer, /review, and /commit. Manual: invoke with /polish or /polish [path-to-repo].
Create and manage implementation spec files that preserve plan and execution state on disk at $SPECS_DIR/. Record phases (~30 min each, max 6 steps), acceptance criteria, Decisions, a Current Step pointer, and a Completed log; after compaction, read the spec, trust Decisions, and continue from Current Step. MANDATORY when using EnterPlanMode or exiting plan mode; every plan-mode session produces a spec. Triggers on: 'write a spec', 'create a spec', 'spec this out', 'multi-file work', 'multi-phase implementation', 'plan this', 'turn this into a spec', 'persist the plan', 'spec status', 'list active specs', 'close the spec', 'update the spec', 'where did we leave off', 'continue the spec', and 'execute the plan'. Also triggers when a 3+ file implementation is about to start or a non-trivial design must survive future sessions. Pairs with /recon, /codex-review --plan, /harness, /best-of-n, and /verify. Manual: /spec [feature-name] (create), /spec update (checkpoint), /spec status (list), /spec close (finalize).
Three-wave reconnaissance protocol that builds a verified knowledge brief before non-trivial planning, design, debugging, or architecture work. Run this when planning quality is bounded by information quality — before /spec, /hammock, a debugging hypothesis, an architecture decision, or a non-obvious multi-file refactor. Wave 1 fans wide for breadth, Wave 2 verifies load-bearing claims and tests seams, Wave 3 synthesizes the merged corpus from two complementary framings. Output is one merged brief written to a known path, ready for the next planner or skill to consume. Auto-trigger when the user is about to design, plan, refactor, or debug something non-trivial and the codebase isn't already in working memory; also trigger when the user says "recon", "scout", "let me understand X first", "investigate before deciding", "research the codebase for", or asks to verify load-bearing claims about repo state. Skip for trivially-scoped work (1-2 files, obvious path) — direct Glob/Grep/Read is faster.
Expert conversion copywriter for marketing pages. Write, rewrite, or improve marketing copy for homepages, landing pages, pricing pages, feature pages, about pages, or product pages. Applies concrete rules: benefits over features, specific over vague, active over passive, banned buzzwords list, CTA formulas. Auto-trigger: when the user wants to write or improve marketing copy, website copy, landing pages, CTAs, or any external-facing sales text.
Pre-compaction context preservation. Saves session state to files including spec file progress. Manual: PreCompact hook handles basic saves automatically. Invoke /context-save for thorough manual save at milestones.