User Guide
New here? Start with Installation.
Spec — plan and execute complex work
Spec gives you a structured planning layer. You write a plan with AI assistance, then execute it step-by-step or hand it off to a background agent.
Typical flow:
/spec new my-feature # Explores requirements and creates plan + implementation files
/spec go my-feature # Execute interactively, with review stops between phases
/spec done my-feature # Archive the plan and optionally commitFor long or routine tasks, run in the background instead:
/spec new my-feature
/spec bg my-feature # Background agent works while you do other things
/spec list # Check progress across all plans
/spec done my-featureYou can have multiple plans active at once — /spec list shows all of them. Plans live in .codevoyant/plans/{name}/ with a high-level plan.md and per-phase implementation/ files.
See the Spec skills reference for all skills.
Git — commits, CI, and rebase
Git handles the mechanical parts of the commit loop.
Committing:
/git commitRuns formatters, analyzes staged changes, generates a conventional commit message for your review, then commits, pushes, and starts CI monitoring in the background. Use --atomic to split logical change groups into separate commits.
Rebasing safely:
/git rebase main # handles conflict marker sides correctlyWatching CI:
/git ci # runs in background, notifies you when done
/git ci --autofix # automatically fixes failures and re-pushesSee the Git skills reference for all skills.
Dev — architecture, exploration, and PR/MR
Dev handles the higher-level parts of the development loop.
Open a PR or MR:
/dev pr # creates PR/MR into main, auto-detects GitHub vs GitLab
/dev pr staging # target a different base branch
/dev pr --draft # create as draftFix review comments on an existing PR/MR:
/dev pr-fix # fetches open review threads and proposes fixes (doesn't apply them)Architecture planning:
/dev plan "auth system" --mode arch # draft architecture plan with task breakdown + LOE
/dev approve my-plan --push # promote to docs/architecture/ and create Linear tasksSee the Dev skills reference for all skills.
EM — engineering project planning (Experimental)
EM structures engineering planning: milestone-grouped task plans, capacity and dependency review, and sync with your team's Linear workspace.
Plan a project:
/em plan "migrate auth to OAuth2" # draft plan to .codevoyant/plans/
/em review my-plan # review for capacity, risks, and dependency gaps
/em approve my-plan --push # promote to docs/ and push to LinearSeed from an existing Linear project:
/em plan https://linear.app/team/project/PRJ-123See the EM skills reference for all skills.
PM — product roadmaps and PRDs (Experimental)
PM covers product planning: phased roadmaps with market context and feature prioritization, per-feature PRDs, coverage and feasibility review, and Linear integration.
Research first, then plan:
/pm explore "mobile onboarding" # research a topic, deposit artifact for /pm plan
/pm plan quarter # draft quarterly roadmap
/pm review my-roadmap --bg # background review
/pm approve my-roadmap --push # promote to docs/ and push to Linear initiativeSingle feature:
/pm prd "user authentication" # standalone PRDSee the PM skills reference for all skills.
UX — prototyping and style research (Experimental)
UX supports frontend design exploration: full SvelteKit prototypes with feature-slice architecture, lightweight single-file wireframes, and automated style extraction from live sites.
Scaffold a prototype:
/ux prototype "admin dashboard" # full SvelteKit + shadcn-svelte prototypeAsks whether to scaffold in-repo (single package or monorepo) or out-of-repo. Builds feature-slice structure, implements a layout first, then generates each feature with view-models, factories, and fake data.
Quick wireframe or approach comparison:
/ux explore "checkout flow" # single HTML wireframe, no build step
/ux explore "nav layouts" --slideshow # compare multiple approaches in one fileOutputs a self-contained .html file using Tailwind CDN — open directly in a browser.
Extract styles from a live site:
/ux style-synthesize https://example.comScreenshots the site at mobile/tablet/desktop breakpoints, analyzes typography, color, and layout patterns, and writes docs/ux/style-research/{source}/style-report.md + theme.css.
See the UX skills reference for all skills.
Skill — build and maintain skills
Skill gives you a structured workflow for building your own Claude Code / Agent Skills compatible skills: research what already exists, scaffold from a template, iterate, and run quality reviews before shipping.
Typical workflow:
/skill explore "linear integration" # research existing skills first
/skill new linear-push # scaffold from template
/skill update linear-push # refine any steps
/skill review linear-push # audit spec compliance + effectivenessSee the Skill skills reference for all skills.
Mem — team knowledge (CLI only)
Mem lets you capture team conventions, decisions, and procedures as indexed markdown docs. Knowledge loads into AI context at session start so the agent always knows your team's rules.
The /mem * slash commands have been removed — use the npx @codevoyant/agent-kit mem CLI directly.
Index and load knowledge:
npx @codevoyant/agent-kit mem list # Load all indexed docs into context
npx @codevoyant/agent-kit mem index # Re-index after manual edits
npx @codevoyant/agent-kit mem find --tag deploymentAdd npx @codevoyant/agent-kit mem list to your CLAUDE.md to load knowledge automatically at session start.
See the Mem reference for the full CLI.