skills

Bootstrap AI-ready repo governance, traceability, cascade, catalog audits, validation. Deprecated compatibility aliases: init-ai-repo, ai-sdlc-init. Use when setting up AI SDLC.

Deprecated compatibility alias for ai-catapult-init. Use only when legacy prompts invoke "ai-sdlc-init"; otherwise use "ai-catapult-init".

Ship a northstar handoff's goals in an ai-catapult-init repo — ultragoal one-PR-per-goal, deterministic engine-pick, peer review, CI gate, fail-closed merge, cascade closure.

Scaffold a structurally valid eval triplet for a target skill under .ai/evals/. CI checks structure only; the LM-judge runs out-of-band, never in CI.

Deprecated compatibility alias for ai-catapult-init. Use only when legacy prompts invoke "init-ai-repo"; otherwise use "ai-catapult-init".

Intake intent into a tracked, sliced plan in an ai-catapult-init repo — deep-interview + skippable grill-me, always raise an issue, ralplan, write the A→B handoff.

Configure AGENTS/CLAUDE and docs/agents for tracker, triage labels, and domain docs. Use before issue, PRD, triage, TDD, or diagnosis skills.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

Design APIs/interfaces with Design It Twice: create alternatives, compare tradeoffs, choose one. Use when designing an API, module, class, or boundary.

Run a reproduce-minimize-hypothesize-instrument-fix loop. Use when debugging bugs, failures, thrown errors, or performance regressions.

Interview the user to stress-test a plan or design until decisions are clear. Use when the user wants to be grilled or challenge a plan.

Stress-test a plan against repo docs and update decisions inline. Use when challenging a design against documented language, ADRs, or CONTEXT.md.

Find deepening opportunities from CONTEXT.md and ADRs. Use when refactoring shallow modules, boundaries, coupling, or testability.

Build a throwaway terminal or UI prototype to test state, logic, or design options. Use when the user wants a playable prototype or design trial.

Set up semantic or calendar versioning and package publishing across supported ecosystems. Use when configuring release automation or changelogs.

Run red-green-refactor with one failing test, one implementation, then cleanup. Use when building features or fixes test-first.

Break a plan, spec, or PRD into traceable implementation issues. Use when converting requirements into tickets or agent-ready work.

Triage issues through canonical state labels and ownership roles. Use when creating, reviewing, prioritizing, or preparing issues for agents.

Extract and save a DDD glossary, flag ambiguities, and propose canonical terms. Use when defining domain language or a shared vocabulary.

Create isolated git worktrees with safety checks and setup guidance. Use when starting feature work that needs separation from the main checkout.

Write or audit agent-facing Markdown with progressive disclosure. Use when editing SKILL.md, AGENTS.md, README.md, or other agent docs.

Explain broader code or product context around a focused area. Use when the user needs a higher-level perspective before local changes.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Enforce Karpathy software engineering principles: think before coding, prefer simplicity, make surgical changes, stay goal-driven. Use when reviewing code quality, planning implementation approach, or auditing for over-engineering.

Edit and improve articles by restructuring sections, improving clarity, and tightening prose