Explore skills

Analyze the current conversation or mine historical chat sessions for correction patterns, wrong conclusions, or unnecessary user intervention. Use when the user wants to improve prompts, skills, workflows, or guardrails based on repeated mistakes.

Guide for working through a Jira story efficiently by separating context gathering, immutable evidence collection, codebase exploration, human-in-the-loop specification refinement, execution planning, and implementation. Use when turning a ticket into a reliable engineering workflow instead of jumping straight to code.

Break down any concept, code, technology, or idea into a clear, layered explanation for adults who want the "aha moment" without the jargon. Produces a single self-contained HTML page with a concrete analogy, embedded CSS visual diagrams, layered detail, and curated links — then opens it in the browser. Use this skill whenever the user says "ELI5", "explain like I'm 5", "explain this simply", "bre

Use when comparing two versions of agent output to determine which is better, or when evaluating whether a skill produces higher quality results than baseline

Structured feedback session analyzing Claude Code usage over a configurable time window. Gathers evidence from git history, memory files, and project state, then delivers an honest 5/5/5 report (going well, not going well, what to improve) with specific evidence and trend tracking against previous sessions. Use when asked to "run feedback", "how am I doing", "feedback session", "usage review", "se

Run multiple skills on the same task in parallel and compare outputs side by side. A creative pitch room -- give it a brief, and it finds skills (local + trusted community repos) to work on it independently, then presents all outputs for comparison. Use when asked to "skill battle", "compare skills", "run multiple skills", "pitch room", "get different takes", "split test this", "give me options",

Customer discovery skill for founders. Use when user wants to design user interviews, build surveys, run Jobs-to-be-Done analysis, or synthesize customer research. Triggers on "customer discovery", "user interviews", "Mom Test", "JTBD", "jobs to be done", "customer research", "user research", "survey design", or /discovery commands.

End-of-context-window session transition that saves memory, writes a handoff doc, posts a GitHub progress comment, and instructs the user to /compact for a clean next session. Use when context usage approaches 80%, when remaining tokens are insufficient for the current phase's remaining work, or when user says "handover", "context is full", "save progress", "end session". Distinct from /handoff (l

Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices with enforced AC templates, creation gates, and dual output to GitHub Issues + PLAN.md. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Briefs the current session by reading session state, handoff doc, and memory to determine the active phase, task, and context budget. Outputs a structured briefing and detects whether the phase should be skipped or reverted based on observable artifacts. Use at the start of every long-running agent session, or when user says "start session", "what are we working on", "resume", "pick up where we le

Creates CLAUDE.md/AGENTS.md from the harness template (if absent) and configures docs/agents/ so harness skills know the issue tracker, triage labels, domain docs, GitHub Project board, and session state location. Run before first use of triage, to-prd, to-issues, context-handover, or session-start — or if those skills appear to be missing context. Typically consumes <30% of a context window.

Audit and remove stale, renamed, or duplicate skills across all installed agent platforms (Claude Code, Kiro, Codex, Windsurf, Gemini, Pi, and more). Handles symlink and copy installs, detects artifacts, and generates OS-correct removal commands. Use when skills list feels cluttered, after renaming a skill, after uninstalling a plugin, or when user says "clean up skills", "remove old skill", "prun