challengePut a plan through an adversarial debate before anyone builds it. The panel
docsWrite the project documents that are missing — requirements, flows, data schema,
featureOpen a piece of feature work and keep its trail. Records the feature where the
fixOpen a defect and keep its trail. Records the bug where the project tracks work
flowDraw the kodflow workflow as an ASCII diagram — the whole map, the nominal path
huntHunt every defect of one topic across one or several repositories until a full pass on a frozen commit finds none: verified issues, one fix commit and one Codex review per issue, nothing pushed before convergence, all resumable from a JSONL ledger. Use when a whole topic needs its defects found and
planEnter Claude Code planning mode with RLM decomposition. Analyzes codebase, designs
projectOpen or create the workspace for a coding project, then turn the conversation into enforceable constraints. Detects whether the current directory is already a git work tree; if not, finds where this user keeps their code (~/Projects, localized Documents off macOS, %USERPROFILE%\Documents, ...) and a
recapOne compact table, in French, of where the session's work stands — open epics and
refineSkills Architecture v1.6 — proof-bearing goal contract generator with three entry
searchResearch a technology, API or practice and write a plan-grade context file to .claude/contexts/<slug>.md. Consults the local knowledge base first — but treats it as dated evidence, not scripture: every document carries a `verified` date, and a stale one is a hypothesis to confirm against the web rat
warmupPre-load a project's context before working on it. Maps the CLAUDE.md hierarchy without re-reading what Claude Code already loaded, loads the constraint ledger written by /project, explores only what the docs leave open, and emits one bounded briefing. `--update` refreshes, creates and splits the CL