claude-evolve

Start a guided build flow for a new project, feature, or substantial task. Invokes the build-project skill for structured requirements gathering. Triggers: "/build"

Manage claude-evolve toolkit. Initialize, release, migrate, and switch toolkits. Subcommands: init, help, learn, audit, migrate, prepare, release, switch, context, status, consolidate, understanding Triggers: "/evolve", "toolkit", "setup toolkit", "initialize toolkit", "release toolkit"

Show claude-evolve help and available commands. Triggers: "/evolve help", "evolve commands", "how do I use evolve"

Extract learnings from current conversation. Use after debugging sessions, problem-solving, or when valuable insights emerge. Triggers: "extract learnings", "save what we learned", "capture insights", "remember this", "document this pattern", "/learn"

Trigger deep reflection on recent observations to update understanding

Alias for `/evolve audit`. Audit and optimize Claude Code configuration. Triggers: "audit my setup", "review configuration", "check my config", "is my setup secure", "optimize setup", "/evolve audit"

Track progress through multi-phase development workflows. Shows current phase, enables phase transitions (next/skip/done), and coordinates multiple concurrent workflows. Uses native Claude Code tasks - no state files. <example> Context: User wants to check current workflow context user: "/workflow" assistant: "Shows current task and suggested next phase" </example> <example> Context: User wants to skip the planning phase user: "/workflow skip" assistant: "Skipping current phase, moving to next" </example> <example> Context: User wants to advance to next phase user: "/workflow next" assistant: "Advancing to next phase" </example> <example> Context: User wants to complete the workflow user: "/workflow done" assistant: "Asks for confirmation before completing" </example> Subcommands: status, skip, next, done, switch, expand Triggers: "/workflow", "workflow status", "skip phase", "next phase", "workflow done"