Explore skills

Use PROACTIVELY when the user invokes /plan <slug> or asks "how should we build this". Runs the `planner` subagent in a forked context which writes specs/<slug>/plan.md from a clarified spec. Refuses to plan if spec.md is still `draft`.

Use PROACTIVELY after /plan, /tasks, or /implement completes — and any time the user invokes /review <slug> [artefact]. Runs both the `verifier` subagent (forked context, Claude-native) and codex (via `codex exec`) on the named artefact. Writes specs/<slug>/reviews/{verifier,codex}-<artefact>-<date>.md. Never edits the implementation.

Use PROACTIVELY when the user invokes /clarify <slug> or when a spec has Open questions and the user wants to resolve them. Reads specs/<slug>/spec.md §6, asks targeted questions, integrates answers, bumps Status to `clarified`.

Use PROACTIVELY when the user wants to author, amend, or revise memory/constitution.md (the supreme project contract). Triggers on /constitution and on phrases like "set the project principles", "redéfinis les principes", "what are our invariants". Never use during a feature flow (specify/plan/...) — pause the flow and explain.

Use PROACTIVELY when the user invokes /specify <slug> or asks to "write the spec", "define the feature", "what should we build". Runs the `specifier` subagent in a forked context which writes specs/<slug>/spec.md. Refuses to write code or plan.

Use PROACTIVELY when the user invokes /tasks <slug> or asks "break this plan into tasks". Runs the `decomposer` subagent in a forked context which writes specs/<slug>/tasks.md. Refuses if plan.md is still `draft`.

Legal templates and compliance checklists for startups. Use when user needs terms of service, privacy policy, contractor agreements, or compliance guidance. Triggers on "terms of service", "privacy policy", "ToS", "GDPR", "SOC2", "compliance", "legal", "contractor agreement", "NDA", or /legal commands. NOT legal advice — templates and checklists that point founders to the right conversations with

Customer retention and lifecycle skill. Use when user needs lifecycle email sequences, NPS/CSAT survey design, cohort analysis, or churn reduction strategies. Triggers on "retention", "lifecycle email", "NPS", "CSAT", "customer success", "onboarding emails", "win-back", or /retain commands.

Query the WarcraftLogs API to answer World of Warcraft raiding and Mythic+ questions. Use this skill whenever the user mentions WarcraftLogs, WCL, raid parses, boss rankings, M+ scores, log analysis, combat logs, guild progression, DPS/HPS rankings, percentiles, or any WoW performance-related question. Also use when the user pastes a warcraftlogs.com URL, mentions a character name + server in a Wo

Smart router for all WoW questions — routes to the right data source automatically. Use for any general WoW question that could involve multiple data sources, for full character audits, or when the user says "check me", "audit my character", "wow check", or asks a broad WoW question without specifying a data source. Also catches questions that could go to raiderio, archon, murlok, sim, or warcraft

[PM Twin] Load pm-kit context — reads PRD, arch, skill catalog, sibling-kit availability, and any new upstream commits since your last session.

[PM Twin] Full productize suite — Intelligence Hub, production features, hero page, help docs, sales toolkit.