Explore skills

Use when Claude Code needs to review changes against active SpecDD specs.

Use when Claude Code needs to classify risk before SpecDD work starts.

Use when Claude Code needs to find, add, interpret, organize, or update SpecDD `Tasks` entries.

Use when Claude Code needs to derive, add, update, or assess tests from active SpecDD specs.

Generate MCPB (MCP Bundle) packages for MCP server projects. Creates manifest.json, bundle directory structure, validates against the MCPB spec, and wires in CI/CD workflows.

[PM Twin] Generate pitch materials from Intelligence Hub data — investor, partner, enterprise, or internal audiences.

[PM Twin] Define, track, and review product KPIs — success metrics, funnels, health indicators.

Use PROACTIVELY when the user invokes /implement <slug> or asks "now build it / run the tasks / execute the plan". Runs the `implementer` subagent in a forked context which walks specs/<slug>/tasks.md and writes src/** + tests/** one task at a time, one commit per task.

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.