spec:help
Print the following text exactly as written. Do not reformat, create tables, add headers, or add any commentary.
spec — Specification-driven development commands for Claude Code
/spec:new [plan-name|url] [--branch branch-name] [--blank] [--bg] [--silent] Create a new spec plan by exploring requirements and building a structured implementation plan
/spec:bg [plan-name] [--yes|-y] [--commit|-c] [--silent] Launch a plan hands-free — the agent executes every task autonomously and updates progress in real-time
/spec:go [plan-name] [--bg] [--silent] [--commit|-c] Execute or continue a spec plan interactively with configurable breakpoints
/spec:list [plan-name] List all spec plans with status and progress, or show detailed status for one plan
/spec:review [plan-name] [--bg] [--silent] Review a spec plan before execution — checks for ambiguous tasks, missing validation, and dependency gaps
/spec:update [plan-name] [change description] [--bg] [--silent] Update a spec plan by applying inline annotations or describing changes conversationally
/spec:refresh [plan-name] [--bg] [--silent] Review an existing spec plan and update checklist status and phase markers
/spec:done [plan-name] Mark a spec plan as complete, optionally commit changes, and archive it
/spec:stop [plan-name] Stop a running background agent or pause a plan and capture session insights
/spec:delete [plan-name] Permanently delete a spec plan and all its files
/spec:rename [old-name] [new-name] Rename a spec plan and update all references
/spec:doctor Diagnose and fix spec setup issues — detects old path layouts and migrates them
/spec:allow [--global] Pre-approve spec plugin permissions for uninterrupted background agent execution
More from cloudvoyant/codevoyant
mem:help
Use when the user asks about available mem commands or needs help choosing a skill. Triggers on: \"mem help\", \"help mem\", \"what can mem do\", \"mem commands\", \"list mem skills\", \"mem reference\". Lists all mem commands with descriptions, arguments, and usage guidance.
14dev:plan
Use when planning architecture for a project or feature. Triggers on: "dev plan", "architecture plan", "plan architecture", "design architecture", "technical design", "system design for". Produces draft plan artifacts in .codevoyant/plans/{slug}/. Use /dev:approve to promote to docs/architecture/.
14em:review
Use when reviewing an engineering roadmap for quality and realism. Triggers on: "em review", "review roadmap", "sanity check roadmap", "em check", "review this plan". Checks capacity realism, dependency gaps, missing risks, and phasing quality. Auto-launched after em:plan.
13dev:explore
Use when researching technical approaches before building. Triggers on: "explore options", "what are my options for", "research approaches", "compare solutions", "dev explore", "generate proposals", "help me decide between". Runs parallel proposal generation via subagents and outputs to .codevoyant/explore/.
13em:plan
Use when planning a project (epic) or initiative with Linear as tracker.
13pm:plan
Plan a product roadmap for a quarter, half-year, or year. Writes a draft roadmap to .codevoyant/roadmaps/ using capability tiers. Triggers on: "pm plan", "product roadmap", "plan a roadmap", "quarterly roadmap", "annual plan".
13