clavix 5.0.0 → 5.1.0

package/dist/templates/slash-commands/_components/troubleshooting/vibecoder-recovery.md

@@ -21,7 +21,7 @@ When something goes wrong, help users gracefully. Always try to fix it yourself
 #### Prompt Not Found
 **What happened:** User asked about a prompt that doesn't exist
 **You try first:**
-1. Run `clavix prompts list` to see what's available
+1. List files in `.clavix/outputs/prompts/` directory to see what's available
 2. Check if there's a similar prompt ID
 
 **Say:**
@@ -37,7 +37,7 @@ When something goes wrong, help users gracefully. Always try to fix it yourself
 #### Task Not Found
 **What happened:** Tried to complete a task that doesn't exist
 **You try first:**
-1. Run `clavix implement --list` to get current tasks
+1. Read `tasks.md` file to get current tasks
 2. Check for typos in task ID
 
 **Say:**

package/dist/utils/agent-error-messages.js

@@ -17,7 +17,7 @@ export class AgentErrorMessages {
             'Agent recovery options:\n' +
             '  1. Execute /clavix:prd to generate comprehensive PRD\n' +
             '  2. Execute /clavix:summarize if conversation exists\n' +
-            '  3. Use clavix plan --session <id> if saved session available\n\n' +
+            '  3. Check .clavix/sessions/ if saved session available\n\n' +
             'Select option and execute, then retry this command.');
     }
     /**
@@ -27,8 +27,8 @@ export class AgentErrorMessages {
     static noTasksFound(projectName) {
         return (`No tasks.md found for project: ${projectName}\n\n` +
             'Agent recovery options:\n' +
-            `  1. Execute: clavix plan --project ${projectName}\n` +
-            '  2. Or execute /clavix:plan to generate interactively\n\n' +
+            `  1. Execute /clavix:plan to generate task breakdown\n` +
+            '  2. Or read PRD and generate tasks.md manually\n\n' +
             'After task generation completes, retry implementation.');
     }
     /**
@@ -38,10 +38,9 @@ export class AgentErrorMessages {
     static configNotFound() {
         return ('Configuration file not found: .clavix-implement-config.json\n\n' +
             'Agent recovery:\n' +
-            '  1. Run: clavix implement\n' +
-            '  2. Wait for user to select git strategy\n' +
-            '  3. Config will be created automatically\n' +
-            '  4. Then retry task completion\n\n' +
+            '  1. Execute /clavix:implement to initialize implementation\n' +
+            '  2. Config will be created automatically\n' +
+            '  3. Then retry task completion\n\n' +
             'This is expected on first run.');
     }
     /**
@@ -50,14 +49,15 @@ export class AgentErrorMessages {
      */
     static taskNotFound(taskId, availableTasks) {
         const taskList = availableTasks
-            .map(t => {
+            .map((t) => {
             const status = t.completed ? '[x]' : '[ ]';
             return `  ${status} ${t.id} - ${t.description}`;
         })
             .join('\n');
         return (`Task ID not found: ${taskId}\n\n` +
             'Available task IDs:\n' +
-            taskList + '\n\n' +
+            taskList +
+            '\n\n' +
             'Select a valid task ID from the list above and retry.');
     }
     /**
@@ -93,7 +93,8 @@ export class AgentErrorMessages {
     static multiplePrdsFound(projects) {
         const projectList = projects.map((p, i) => `  ${i + 1}. ${p}`).join('\n');
         return ('Multiple PRD projects found:\n\n' +
-            projectList + '\n\n' +
+            projectList +
+            '\n\n' +
             'Agent recovery options:\n' +
             '  1. Specify project explicitly: --project <name>\n' +
             '  2. Or run CLI in interactive mode to let user select\n\n' +
@@ -134,8 +135,8 @@ export class AgentErrorMessages {
             '  • All projects already archived\n' +
             '  • No projects with completed tasks\n\n' +
             'Agent recovery options:\n' +
-            '  1. Run: clavix archive --list to see archived projects\n' +
-            '  2. Check: .clavix/outputs/ for active projects\n' +
+            '  1. List .clavix/outputs/archive/ to see archived projects\n' +
+            '  2. Check .clavix/outputs/ for active projects\n' +
             '  3. Or create new PRD with /clavix:prd');
     }
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clavix",
-  "version": "5.0.0",
+  "version": "5.1.0",
   "description": "Agentic-first prompt workflows. Markdown templates that teach AI agents how to optimize prompts, create PRDs, and manage implementation. Works with Claude Code, Cursor, Windsurf, and 19+ other AI coding tools.",
   "type": "module",
   "main": "dist/index.js",

package/dist/templates/slash-commands/_canonical/execute.md

@@ -1,276 +0,0 @@
----
-name: "Clavix: Execute"
-description: Execute saved prompts from improve optimization
----
-
-# Clavix: Execute Saved Prompts
-
-Time to build! You've optimized a prompt with `/clavix:improve` - now I'll implement it.
-
-Your saved prompts live in `.clavix/outputs/prompts/`.
-
----
-
-## What This Does
-
-When you run `/clavix:execute`, I:
-1. **Find your prompt** - Load what you saved from improve mode
-2. **Understand what to build** - Read the requirements and checklist
-3. **Implement everything** - Write the code, create files, build features
-4. **Run verification automatically** - Make sure everything works
-5. **Clean up when done** - Remove executed prompts
-
-**I do ALL of this automatically. You just watch (or grab coffee).**
-
----
-
-## CLAVIX MODE: Implementation
-
-**I'm in implementation mode. Building time!**
-
-**What I'll do:**
-- Read and understand your prompt requirements
-- Implement everything in the optimized prompt
-- Write production-quality code
-- Follow the specifications exactly
-- Run tests and verification automatically
-- Handle errors and fix issues
-
-**What I'm authorized to create:**
-- Functions, classes, and components
-- New files and file modifications
-- Tests for implemented code
-- Configuration files if needed
-
-**Before I start, I'll confirm:**
-> "Starting implementation mode. Building your [feature description]..."
-
-For complete mode documentation, see: `.clavix/instructions/core/clavix-mode.md`
-
----
-
-## Before You Start
-
-You need a saved prompt first. Run:
-- `/clavix:improve "your prompt"` - Smart prompt improvement with auto depth selection
-
-Then come back here with `/clavix:execute`.
-
----
-
-## How I Execute Your Prompt
-
-### The Quick Version
-
-```
-You:    /clavix:execute
-Me:     [Finds your latest prompt]
-        [Reads requirements]
-        [Implements everything]
-        [Runs verification]
-Me:     "Done! Here's what I built..."
-```
-
-### The Detailed Version (v5 Agentic-First)
-
-**Step 1: I find your prompt**
-
-I read directly from the file system:
-- List `.clavix/outputs/prompts/*.md` to find saved prompts
-- Get the most recent one (by timestamp in filename or frontmatter)
-- Read the prompt file: `.clavix/outputs/prompts/<id>.md`
-
-**Step 2: I read and understand**
-
-I parse the prompt file and extract:
-- The objective (what to build)
-- Requirements (specifics to implement)
-- Technical constraints (how to build it)
-- Success criteria (how to know it's done)
-
-**Step 3: I implement everything**
-
-This is where I actually write code using my native tools:
-- Create new files as needed
-- Modify existing files
-- Write functions, components, classes
-- Add tests if specified
-
-**Step 4: I verify automatically**
-
-After building, I verify by:
-- Running tests (if test suite exists)
-- Building/compiling to ensure no errors
-- Checking requirements from the checklist
-
-**Step 5: I report results**
-
-You'll see a summary of:
-- What I built
-- What passed verification
-- Any issues (if they exist)
-
----
-
-## Automatic Verification (I Handle This)
-
-**I always verify after implementing. You don't need to ask.**
-
-### What Happens Automatically
-
-After I finish building, I run verification myself:
-
-1. **Load the checklist** - From your executed prompt (what to check)
-2. **Run automated tests** - Test suite, build, linting, type checking
-3. **Check each requirement** - Make sure everything was implemented
-4. **Generate a report** - Show you what passed and failed
-
-### What You'll See
-
-```
-Implementation complete for [prompt-id]
-
-Verification Results:
-8 items passed
-1 item needs attention: [specific issue]
-
-Would you like me to fix the failing item?
-```
-
-### Understanding the Symbols
-
-| Symbol | Meaning |
-|--------|---------|
-| Pass | Passed - This works |
-| Fail | Failed - Needs fixing |
-| Skip | Skipped - Check later |
-| N/A | N/A - Doesn't apply |
-
-### When Things Fail
-
-**I try to fix issues automatically:**
-
-If verification finds problems, I'll:
-1. Tell you what failed and why
-2. Offer to fix it
-3. Re-verify after fixing
-
-**If I can't fix it myself:**
-
-I'll explain what's wrong and what you might need to do:
-> "The database connection is failing - this might be a configuration issue.
-> Can you check that your `.env` file has the correct `DATABASE_URL`?"
-
-### Standard vs Comprehensive Depth Verification
-
-**Standard depth prompts:**
-- I generate a basic checklist based on what you asked for
-- Covers essentials: compiles, no errors, requirements met
-
-**Comprehensive depth prompts:**
-- Use the comprehensive checklist from deep analysis
-- More thorough verification with edge cases
-
-**For more thorough verification, use `/clavix:improve --comprehensive`**
-
----
-
-## Prompt Management (v5 Agentic-First)
-
-**Where prompts live:**
-- All prompts: `.clavix/outputs/prompts/*.md`
-- Metadata: In frontmatter of each `.md` file
-
-### How I Access Prompts (Native Tools)
-
-| What I Do | How I Do It |
-|-----------|-------------|
-| List saved prompts | List `.clavix/outputs/prompts/*.md` files |
-| Get latest prompt | Find newest file by timestamp in filename |
-| Get specific prompt | Read `.clavix/outputs/prompts/<id>.md` |
-| Mark as executed | Edit frontmatter: `executed: true` |
-| Clean up executed | Delete files where frontmatter has `executed: true` |
-
-### The Prompt Lifecycle
-
-```
-1. YOU CREATE   →  /clavix:improve (saves to .clavix/outputs/prompts/<id>.md)
-2. I EXECUTE    →  /clavix:execute (you are here) - I read and implement
-3. I VERIFY     →  Automatic verification
-4. MARK DONE    →  I update frontmatter with executed: true
-```
-
----
-
-## Finding Your Way Around
-
-Need to see what projects exist or check progress? I read the file system:
-
-| What I Need | How I Find It |
-|-------------|---------------|
-| See all projects | List directories in `.clavix/outputs/` |
-| Check a specific project | Read `.clavix/outputs/<project>/` files |
-| See saved prompts | List `.clavix/outputs/prompts/*.md` files |
-| Find archived work | List `.clavix/outputs/archive/` |
-
----
-
-## When Things Go Wrong
-
-### No Prompts Found
-
-If I can't find a saved prompt, I'll tell you:
-> "I don't see any saved prompts. Let's create one first!"
-
-Then you can run `/clavix:improve "your requirement"` and come back.
-
-### Prompt Is Old or Stale
-
-If your prompt is more than 7 days old:
-> "This prompt is a bit old. Want me to proceed anyway, or should we create a fresh one?"
-
-### Verification Keeps Failing
-
-If I can't get verification to pass after trying:
-> "I've tried a few fixes but this item keeps failing. Here's what's happening: [details]
->
-> Would you like me to:
-> 1. Keep trying with a different approach
-> 2. Skip this check for now
-> 3. Show you what needs manual attention"
-
----
-
-## Workflow Navigation
-
-**Where you are:** Execute (building your prompt)
-
-**How you got here:**
-1. `/clavix:improve` - Optimized your prompt
-2. **`/clavix:execute`** - Now building it (you are here)
-
-**What happens after:**
-- I verify automatically - Results shown
-- If all passes - Done! I clean up
-- If issues - `/clavix:verify` for detailed check
-
-**Related commands:**
-- `/clavix:improve` - Smart prompt optimization (previous step)
-- `/clavix:verify` - Detailed verification (if needed)
-- `/clavix:archive` - Archive when fully done
-
----
-
-## Agent Transparency (v5.0)
-
-### CLI Reference (Commands I Execute)
-{{INCLUDE:agent-protocols/cli-reference.md}}
-
-### Error Handling
-{{INCLUDE:agent-protocols/error-handling.md}}
-
-### Agent Decision Rules
-{{INCLUDE:agent-protocols/decision-rules.md}}
-
-### Recovery Patterns
-{{INCLUDE:troubleshooting/vibecoder-recovery.md}}

package/dist/templates/slash-commands/_components/agent-protocols/assertion-checkpoints.md

@@ -1,122 +0,0 @@
-## Assertion Checkpoints (v4.6)
-
-At key workflow stages, verify your execution matches expected state. These checkpoints help ensure correct template execution.
-
-### Fast/Deep Mode Checkpoints
-
-**CHECKPOINT 1: After Intent Detection**
-```
-✓ Intent type identified (one of 11 types)
-✓ Confidence percentage calculated
-✓ If confidence < 70%: Secondary intent noted
-```
-
-**CHECKPOINT 2: After Quality Assessment**
-```
-✓ All 6 dimensions scored:
-  - Clarity (0-100%)
-  - Efficiency (0-100%)
-  - Structure (0-100%)
-  - Completeness (0-100%)
-  - Actionability (0-100%)
-  - Specificity (0-100%)
-✓ Overall quality calculated
-✓ Strengths identified (any dimension >= 85%)
-```
-
-**CHECKPOINT 3: After Optimization**
-```
-✓ Enhanced prompt generated
-✓ Improvements listed with dimension labels
-✓ Patterns applied documented
-```
-
-**CHECKPOINT 4: After Saving**
-```
-✓ Prompt saved to .clavix/outputs/prompts/{mode}/
-✓ Index file updated
-✓ Success message displayed
-```
-
-### PRD Mode Checkpoints
-
-**CHECKPOINT 1: Before Questions**
-```
-✓ State assertion displayed
-✓ Implementation blocked message shown
-```
-
-**CHECKPOINT 2: After Each Question**
-```
-✓ Answer validated for completeness
-✓ Follow-up asked if answer is vague
-✓ Minimum requirements met before proceeding
-```
-
-**CHECKPOINT 3: After Document Generation**
-```
-✓ Full PRD generated with all sections
-✓ Quick PRD generated (2-3 paragraphs)
-✓ Quality validation scores displayed
-```
-
-**CHECKPOINT 4: After Saving**
-```
-✓ Files saved to .clavix/outputs/{project-name}/
-✓ full-prd.md exists
-✓ quick-prd.md exists
-✓ Next steps displayed
-```
-
-### Implementation Mode Checkpoints
-
-**CHECKPOINT 1: Before Starting**
-```
-✓ Config file checked (.clavix-implement-config.json)
-✓ Resume state detected if exists
-✓ Tasks loaded from tasks.md
-```
-
-**CHECKPOINT 2: After Each Task**
-```
-✓ Task completed successfully
-✓ clavix task-complete {task-id} called
-✓ Next task displayed automatically
-```
-
-**CHECKPOINT 3: After All Tasks**
-```
-✓ All tasks marked complete
-✓ Archive suggestion displayed
-✓ Git commit created if configured
-```
-
-### Verification Block Format
-
-At the end of your response, include this verification block:
-
-```
-## Clavix Execution Verification
-- [x] Intent detected: {type} ({confidence}%)
-- [x] Quality assessed: {overall}%
-- [x] {N} patterns applied
-- [x] Prompt saved: {filename}
-- [x] Mode: {fast|deep|prd|plan}
-```
-
-This allows users and developers to verify correct template execution and helps identify any deviations from expected behavior.
-
-### Self-Verification Protocol
-
-If a checkpoint fails:
-1. **STOP**: Do not proceed past the failed checkpoint
-2. **IDENTIFY**: Which checkpoint failed and why
-3. **REPORT**: Inform user of the issue
-4. **RECOVER**: Take corrective action or ask for guidance
-
-Example recovery:
-```
-⚠️ Checkpoint 2 failed: Quality assessment incomplete
-Issue: Specificity dimension not scored
-Action: Rerunning quality assessment with all 6 dimensions
-```

package/dist/templates/slash-commands/_components/agent-protocols/file-formats.md

@@ -1,169 +0,0 @@
-## File Format Reference (v5 Agentic-First)
-
-### .clavix-implement-config.json
-
-Implementation state configuration file.
-
-**Location:** `.clavix/outputs/{project}/.clavix-implement-config.json`
-
-**Schema:**
-```json
-{
-  "commitStrategy": "per-task" | "per-5-tasks" | "per-phase" | "none",
-  "tasksPath": "string - absolute path to tasks.md",
-  "currentTask": {
-    "id": "phase-N-name-M",
-    "description": "Task description text",
-    "phase": "Phase Name",
-    "completed": false
-  },
-  "stats": {
-    "total": 16,
-    "completed": 4,
-    "remaining": 12,
-    "percentage": 25
-  },
-  "timestamp": "2024-01-15T10:30:00.000Z",
-  "completedTaskIds": ["phase-1-setup-1", "phase-1-setup-2"],
-  "blockedTasks": [
-    {
-      "taskId": "phase-2-auth-3",
-      "reason": "Waiting for API keys",
-      "timestamp": "2024-01-15T11:00:00.000Z"
-    }
-  ]
-}
-```
-
-**Agent Usage Rules:**
-- READ this file to determine current state
-- UPDATE using Edit tool when marking tasks complete
-- IF missing: Create with initial state
-- IF corrupted: Report as UNRECOVERABLE error
-
-### tasks.md Format
-
-Task breakdown file generated by /clavix:plan.
-
-**Location:** `.clavix/outputs/{project}/tasks.md`
-
-**Structure:**
-```markdown
-# Implementation Tasks: {Project Name}
-
-Generated from: {PRD filename}
-Created: {timestamp}
-
----
-
-## Phase 1: {Phase Name}
-
-- [ ] {Task description}
-  - Task ID: `phase-1-{sanitized-name}-1`
-  - PRD Reference: {section-name}
-
-- [ ] {Another task}
-  - Task ID: `phase-1-{sanitized-name}-2`
-
-- [x] {Completed task}
-  - Task ID: `phase-1-{sanitized-name}-3`
-
-## Phase 2: {Phase Name}
-
-- [ ] {Task description}
-  - Task ID: `phase-2-{sanitized-name}-1`
-
----
-
-## Progress Summary
-
-- Total Tasks: {N}
-- Completed: {M}
-- Remaining: {N-M}
-```
-
-**Task ID Pattern:** `phase-{N}-{sanitized-name}-{M}`
-- `N` = Phase number (1-indexed)
-- `sanitized-name` = Lowercase, hyphens for spaces, no special chars
-- `M` = Task counter within phase (1-indexed)
-
-**Valid Examples:**
-- `phase-1-setup-configuration-1`
-- `phase-2-user-authentication-3`
-- `phase-3-api-integration-2`
-
-**Invalid Examples:**
-- `phase1-setup-1` - Missing hyphen after "phase"
-- `Phase-1-Setup-1` - Must be lowercase
-- `phase-1-setup` - Missing task number
-
-### Prompt Files (v5 Format)
-
-Individual prompt files with frontmatter metadata.
-
-**Location:** `.clavix/outputs/prompts/<id>.md`
-
-**Format:**
-```markdown
----
-id: std-20250127-143022-a3f2
-timestamp: 2025-01-27T14:30:22Z
-executed: false
-originalPrompt: "the user's original prompt text"
-depthUsed: standard|comprehensive
----
-
-# Improved Prompt
-
-<optimized prompt content>
-
-## Quality Scores
-- **Clarity**: 85%
-- **Efficiency**: 80%
-- **Structure**: 90%
-- **Completeness**: 75%
-- **Actionability**: 88%
-- **Overall**: 84% (good)
-
-## Original Prompt
-```
-<user's original prompt>
-```
-```
-
-**Agent Usage:**
-- LIST prompts: `ls .clavix/outputs/prompts/*.md`
-- READ prompt: Use Read tool on `.clavix/outputs/prompts/<id>.md`
-- FIND latest: Sort files by timestamp in filename
-- MARK executed: Edit frontmatter to set `executed: true`
-
-### PRD Files
-
-**Full PRD:** `.clavix/outputs/{project}/full-prd.md`
-- Complete team-facing document
-- All sections expanded
-
-**Quick PRD:** `.clavix/outputs/{project}/quick-prd.md`
-- 2-3 paragraph AI-optimized version
-- Key requirements only
-
-**Mini PRD:** `.clavix/outputs/{project}/mini-prd.md`
-- From /clavix:summarize
-- Extracted from conversation
-
-### Directory Structure Overview (v5)
-
-```
-.clavix/
-├── outputs/
-│   ├── prompts/
-│   │   └── *.md                    # Prompt files (metadata in frontmatter)
-│   ├── {project-name}/
-│   │   ├── full-prd.md
-│   │   ├── quick-prd.md
-│   │   ├── tasks.md
-│   │   └── .clavix-implement-config.json
-│   └── archive/
-│       └── {archived-project}/
-└── config.json                     # Global config
-```