Clavix is a workflow system that enforces structured building: requirements first, then plan, then build, then verify. No skipping steps. Each command is a slash command you type in Claude Code.
When to use: You have a vague idea but aren't sure exactly what to build yet.
Starts a back-and-forth conversation where Claude asks questions to help clarify your idea. No pressure to have it figured out — just describe what you're thinking and it'll help you shape it. When the conversation is done, use /clavix-summarize to capture what you discussed.
When to use: You know what you want to build and need to document it before coding starts.
Walks you through creating a Product Requirements Document (PRD) by asking one question at a time. Covers what you're building, why, what it needs to do, and what success looks like. The output is a structured document that becomes the blueprint for everything that follows.
When to use: You have a PRD and need to turn it into a step-by-step build plan.
Reads the PRD and your existing codebase, then creates a detailed task list — what files to create/modify, in what order, with technical specifics. This is the actual implementation roadmap.
When to use: You have a plan (from /clavix-plan) and you're ready to code.
Executes the tasks from the plan one by one, tracking progress as it goes. Each task is built, tested, and checked off before moving to the next.
When to use: After building, to make sure what was built matches what was planned.
Acts as a senior code reviewer. Compares the actual code against the PRD and the plan — did we build what we said we'd build? Are there gaps, bugs, or things that don't match the requirements? Generates actionable review comments.
When to use: You have a prompt (for any AI) that you want to make better.
Analyzes your prompt across 6 dimensions (clarity, efficiency, structure, completeness, actionability, specificity), then rewrites it using proven optimization techniques. Good for refining instructions you give to Edge or other AI tools.
When to use: You have a PRD or prompt that needs tweaking, not a full rewrite.
Finds your existing PRDs and saved prompts, then lets you update them through conversation without starting from scratch.
When to use: After a /clavix-start conversation, to turn the discussion into structured requirements.
Reads the conversation, extracts key requirements, decisions, and constraints, and creates clear documentation from it.
When to use: A project is 100% done and you want to tidy up your workspace.
Moves completed PRD projects to an archive folder. They can be restored later if needed.
Without Clavix, the typical workflow is: boss says "build X" → Claude starts coding immediately → things get missed, scope creeps, nobody remembers what was agreed on.
With Clavix: boss says "build X" → PRD documents exactly what "X" means → plan breaks it into steps → build follows the plan → verify confirms it's right. Every decision is documented. Any AI can pick up where the last one left off.
| Command | One-liner |
|---|---|
/clavix-start |
Talk through a vague idea |
/clavix-prd |
Document requirements |
/clavix-plan |
Create task breakdown |
/clavix-implement |
Build from the plan |
/clavix-verify |
Audit the build |
/clavix-improve |
Optimize a prompt |
/clavix-refine |
Update existing PRD/prompt |
/clavix-summarize |
Convert conversation to requirements |
/clavix-archive |
Archive completed projects |
Installed: 2026-04-08