clavix 4.11.2 → 5.0.0

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

@@ -38,25 +38,25 @@ When you run `/clavix:archive`, I:
 
 ---
 
-## How I Archive Projects
+## How I Archive Projects (v5 Agentic-First)
 
-**I handle all the commands - you just tell me what to do.**
+**I use my native tools directly - no CLI commands involved.**
 
-### What I Run (You Don't Need To)
+### What I Do
 
-| What You Want | Command I Execute |
-|---------------|-------------------|
-| Archive completed project | `clavix archive` |
-| Archive specific project | `clavix archive [name]` |
-| Archive incomplete work | `clavix archive [name] --force` |
-| Delete permanently | `clavix archive [name] --delete` |
-| See what's archived | `clavix archive --list` |
-| Restore from archive | `clavix archive --restore [name]` |
+| What You Want | How I Do It |
+|---------------|-------------|
+| Archive completed project | Move directory: `.clavix/outputs/<project>` → `.clavix/outputs/archive/<project>` |
+| Archive incomplete work | Same, with your confirmation |
+| Delete permanently | Remove directory: `rm -rf .clavix/outputs/<project>` |
+| See what's archived | List files in `.clavix/outputs/archive/` |
+| Restore from archive | Move back: `.clavix/outputs/archive/<project>` → `.clavix/outputs/<project>` |
 
 ### Before I Archive
 
 I check:
 - ✓ Projects exist in `.clavix/outputs/`
+- ✓ Task completion status (read tasks.md)
 - ✓ What you want to do (archive, delete, restore)
 - ✓ Project name is correct
 
@@ -69,44 +69,27 @@ I tell you:
 
 ### Part B: Understanding Archive Operations
 
-**Archive Modes**:
+**Archive Operations** (I perform these using my native tools):
 
-1. **Interactive Archive Mode**:
-   ```bash
-   clavix archive
-   ```
-
-   CLI behavior:
-   - Lists all PRD projects with 100% tasks completed
-   - Allows user to select which project to archive
-   - Confirms before archiving
-   - Moves the project to archive directory
+1. **Interactive Archive**:
+   - I list all PRD projects in `.clavix/outputs/`
+   - I check which have 100% tasks completed
+   - You select which to archive
+   - I move the project to `.clavix/outputs/archive/`
 
 2. **Archive Specific Project**:
-   ```bash
-   clavix archive [project-name]
-   ```
-
-   CLI behavior:
-   - Checks task completion status
-   - Warns if tasks are incomplete
-   - Asks for confirmation
-   - Archives the specific project
+   - I check task completion status in `tasks.md`
+   - I warn if tasks are incomplete
+   - You confirm
+   - I move the project directory
 
 3. **Force Archive (Incomplete Tasks)**:
-   ```bash
-   clavix archive [project-name] --force
-   ```
-
    Use when:
    - Project scope changed and some tasks are no longer relevant
    - User wants to archive work-in-progress
    - Tasks are incomplete but project is done
 
 4. **Delete Project (Permanent Removal)**: **DESTRUCTIVE ACTION**
-   ```bash
-   clavix archive [project-name] --delete
-   ```
 
    **WARNING**: This PERMANENTLY deletes the project. Cannot be restored.
 
@@ -124,24 +107,16 @@ I tell you:
    ```
 
    **Safety confirmation required:**
-   - Shows project details and task status
-   - Requires typing project name to confirm
-   - Warns about permanent deletion
-   - Lists what will be permanently deleted
+   - I show project details and task status
+   - I ask you to type project name to confirm
+   - I warn about permanent deletion
+   - I list what will be permanently deleted
 
 5. **List Archived Projects**:
-   ```bash
-   clavix archive --list
-   ```
-
-   Shows all projects currently in archive with their task completion status
+   I read the contents of `.clavix/outputs/archive/` and show you all archived projects.
 
 6. **Restore from Archive**:
-   ```bash
-   clavix archive --restore [project-name]
-   ```
-
-   Moves a project back from archive to active outputs
+   I move a project back: `.clavix/outputs/archive/<project>` → `.clavix/outputs/<project>`
 
 ## When to Archive
 
@@ -180,61 +155,57 @@ Optimized prompts from `/clavix:improve` are stored separately in `.clavix/outpu
 
 **Prompts are NOT archived with PRD projects.**
 
-**Manage prompts separately (CLI commands):**
-```bash
-clavix prompts list           # View all prompts
-clavix prompts clear          # Interactive cleanup
-clavix prompts clear --executed  # Remove executed only
-clavix prompts clear --stale     # Remove >30 day old
-```
-
-**Before archiving, consider cleanup:**
-```bash
-clavix prompts clear --executed
-```
+**To manage prompts:**
+- **View all prompts**: List `.clavix/outputs/prompts/*.md` files
+- **View a prompt**: Read `.clavix/outputs/prompts/<id>.md`
+- **Delete executed prompts**: Remove files where frontmatter has `executed: true`
+- **Delete stale prompts**: Remove files older than 30 days (check timestamp in frontmatter)
 
 **Prompts lifecycle:**
 - Independent from PRD lifecycle
-- Managed via CLI commands
-- Clear manually when project complete
+- Managed by reading/writing files directly
+- Clean up manually when project complete
 
 ## Example Workflows
 
 ### Workflow 1: Complete Project
 ```
 User: "I've finished implementing the user authentication feature"
-You: "Great! Let me help you archive it."
+You: "Great! Let me check the task status and help you archive it."
 
-     Run: clavix archive
+I read: .clavix/outputs/user-authentication-system/tasks.md
+Result: All 15 tasks completed (100%)
 
-User selects: user-authentication-system
-System shows: All 15 tasks completed (100%)
-User confirms: Yes, archive it
+You confirm: Yes, archive it
 
-Result: Project moved to .clavix/outputs/archive/user-authentication-system/
+I execute: mv .clavix/outputs/user-authentication-system .clavix/outputs/archive/
+
+Result: Project archived to .clavix/outputs/archive/user-authentication-system/
 ```
 
 ### Workflow 2: Force Archive WIP
 ```
 User: "We're pivoting, I want to archive the old API design even though tasks aren't done"
-You: "I'll archive it with --force"
+You: "I'll check the status and archive it if you confirm."
 
-     Run: clavix archive old-api-design --force
+I read: .clavix/outputs/old-api-design/tasks.md
+Result: 8 incomplete tasks
 
-System shows: 8 incomplete tasks
 User confirms: Yes, archive anyway
 
+I execute: mv .clavix/outputs/old-api-design .clavix/outputs/archive/
+
 Result: Project archived despite incomplete tasks
 ```
 
 ### Workflow 3: Restore Archived Project
 ```
 User: "Actually, we need to revisit that authentication feature"
-You: "I'll restore it from the archive"
+You: "I'll restore it from the archive."
 
-     Run: clavix archive --restore user-authentication-system
+I execute: mv .clavix/outputs/archive/user-authentication-system .clavix/outputs/
 
-Result: Project moved back to .clavix/outputs/user-authentication-system/
+Result: Project restored to .clavix/outputs/user-authentication-system/
 ```
 
 ### Workflow 4: Delete Failed Experiment
@@ -243,26 +214,25 @@ User: "I have a test project 'api-experiment-1' that I don't need anymore"
 You: "Is this something you might reference later, or can it be permanently deleted?"
 
 User: "It was just a quick test, no value. Delete it."
-You: "This will permanently delete the project. I'll run the delete command."
+You: "This will permanently delete the project. Please confirm by typing the project name."
 
-     Run: clavix archive api-experiment-1 --delete
-
-System shows:
+I show:
   Project: api-experiment-1
   Tasks: 3/5 completed
   Files: full-prd.md, quick-prd.md, tasks.md
 
   WARNING: This action is PERMANENT and CANNOT be undone.
-  Type the project name to confirm deletion: _
 
 User types: api-experiment-1
 
-Result: Project permanently deleted from .clavix/outputs/api-experiment-1/
+I execute: rm -rf .clavix/outputs/api-experiment-1
+
+Result: Project permanently deleted
 ```
 
 ---
 
-## Agent Transparency (v4.9)
+## Agent Transparency (v5.0)
 
 ### CLI Reference (Commands I Execute)
 {{INCLUDE:agent-protocols/cli-reference.md}}
@@ -295,37 +265,37 @@ Result: Project permanently deleted from .clavix/outputs/api-experiment-1/
 - Archive keeps your active projects list clean and focused
 - Archived projects maintain all their data (nothing is deleted)
 - Archive is searchable - you can still `grep` or find files in archive/
-- Regular archiving improves `/clavix:plan` and `/clavix:implement` performance
-- Use `--list` regularly to know what's been archived
+- Regular archiving keeps `.clavix/outputs/` organized
+- Check `.clavix/outputs/archive/` to see what's been archived
 
 ## Troubleshooting
 
 ### Issue: No projects available to archive
 **Cause**: No projects in `.clavix/outputs/` OR all already archived
 
-**Agent recovery**:
-1. Check if `.clavix/outputs/` exists: `ls .clavix/outputs/`
+**How I handle it**:
+1. Read `.clavix/outputs/` directory
 2. If directory doesn't exist: "No PRD projects found. Create one with `/clavix:prd`"
-3. If empty: Run `clavix archive --list` to show archived projects
+3. If empty: Check `.clavix/outputs/archive/` for archived projects
 4. Communicate: "All projects are already archived" or "No projects exist yet"
 
 ### Issue: Trying to archive project with incomplete tasks
 **Cause**: User wants to archive but tasks aren't 100% done
 
-**Agent recovery**:
-1. CLI will warn about incomplete tasks
+**How I handle it**:
+1. I read tasks.md and count incomplete tasks
 2. Ask user: "Project has X incomplete tasks. Do you want to:
    - Complete tasks first with `/clavix:implement`
-   - Archive anyway with `--force` (tasks remain incomplete but archived)
+   - Archive anyway (tasks remain incomplete but archived)
    - Cancel archival"
-3. If user confirms force: Run `clavix archive [project] --force`
-4. If scope changed: Explain `--force` is appropriate
+3. If user confirms: I move the directory
+4. If scope changed: Explain force archive is appropriate
 
 ### Issue: Cannot restore archived project (name conflict)
 **Cause**: Project with same name already exists in active outputs
 
-**Agent recovery**:
-1. CLI will show error: "Project '[name]' already exists in active outputs"
+**How I handle it**:
+1. I detect the conflict when checking the target directory
 2. Ask user which option:
    - Archive the active project first, then restore old one
    - Keep both (manual rename required)
@@ -335,62 +305,54 @@ Result: Project permanently deleted from .clavix/outputs/api-experiment-1/
 ### Issue: Unsure whether to delete or archive
 **Cause**: User wants to clean up but uncertain about permanence
 
-**Agent recovery**:
+**How I handle it**:
 1. Use decision tree to guide user:
-   ```
-   Ask user questions:
    - "Is this a failed experiment with no learning value?"
    - "Might you need to reference this code later?"
    - "Are you unsure if it's valuable?"
-   ```
 2. Default recommendation: **ARCHIVE** (safer, reversible)
 3. Only suggest DELETE for: duplicates, failed experiments, test data with zero value
 4. Remind: "Archive is free, disk space is cheap, regret is expensive"
 
-### Issue: CLI command fails or hangs
+### Issue: File operation fails
 **Cause**: File system permissions, missing directory, or process error
 
-**Agent recovery**:
-1. Check error output from CLI
+**How I handle it**:
+1. Check error output
 2. Common fixes:
    - Check `.clavix/outputs/` exists and is writable
    - Verify project name is correct (no typos)
    - Check if another process is accessing the files
-3. Suggest: Run with full project path or retry
-4. If persistent: Inform user to check file permissions
+3. Retry the operation or inform user about permissions
 
-### Issue: Accidentally deleted project (used --delete instead of archive)
-**Cause**: User error or misunderstanding of --delete flag
+### Issue: Accidentally deleted project
+**Cause**: User error
 
-**Agent recovery**:
-1. Acknowledge: "Project was permanently deleted via `--delete` flag"
+**How I handle it**:
+1. Acknowledge: "Project was permanently deleted"
 2. Check recovery options:
    - "If code was committed to git, we can recover from git history"
    - "Check if you have local backups"
    - "Check if IDE has local history (VS Code, JetBrains)"
 3. Prevention: "Going forward, use ARCHIVE by default. Only DELETE when absolutely certain."
-4. No recovery possible from Clavix itself
 
 ### Issue: Archive directory getting too large
 **Cause**: Many archived projects accumulating
 
-**Agent response**:
+**How I handle it**:
 1. Explain: "Archive is designed to grow - this is normal behavior"
-2. Archived projects don't affect active command performance
-3. If user truly concerned:
-   - Review archive: `clavix archive --list`
+2. Archived projects don't affect workflow performance
+3. If user concerned:
+   - List archive contents
    - Identify ancient/irrelevant projects
-   - Delete only truly obsolete ones: `clavix archive [old-project] --delete`
+   - Delete only truly obsolete ones
    - Or suggest external backup for very old projects
 
 ### Issue: Archived project but forgot what it was about
 **Cause**: No naming convention or time passed
 
-**Agent recovery**:
-1. Read the PRD to remind user:
-   ```bash
-   cat .clavix/outputs/archive/[project-name]/full-prd.md
-   ```
+**How I handle it**:
+1. Read the PRD: `.clavix/outputs/archive/[project-name]/full-prd.md`
 2. Summarize: Problem, Goal, Features from PRD
 3. Suggest: Better naming conventions going forward
    - Example: `2024-01-user-auth` (date-feature format)

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

@@ -71,19 +71,18 @@ Me:     [Finds your latest prompt]
 Me:     "Done! Here's what I built..."
 ```
 
-### The Detailed Version
+### The Detailed Version (v5 Agentic-First)
 
 **Step 1: I find your prompt**
 
-I automatically run these commands (you don't need to):
-- `clavix execute --latest` - Get most recent prompt
-- Or `clavix execute --latest --standard` - Get latest standard depth prompt
-- Or `clavix execute --latest --comprehensive` - Get latest comprehensive depth prompt
-- Or `clavix execute --id <id>` - Get specific 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'll parse the prompt file, extract:
+I parse the prompt file and extract:
 - The objective (what to build)
 - Requirements (specifics to implement)
 - Technical constraints (how to build it)
@@ -91,7 +90,7 @@ I'll parse the prompt file, extract:
 
 **Step 3: I implement everything**
 
-This is where I actually write code:
+This is where I actually write code using my native tools:
 - Create new files as needed
 - Modify existing files
 - Write functions, components, classes
@@ -99,10 +98,10 @@ This is where I actually write code:
 
 **Step 4: I verify automatically**
 
-After building, I run verification myself:
-- `clavix verify --latest` - Check the implementation
-- Run any automated tests
-- Build/compile to ensure no errors
+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**
 
@@ -176,52 +175,43 @@ I'll explain what's wrong and what you might need to do:
 
 ---
 
-## Prompt Management (Commands I Run)
-
-These are commands I execute automatically - you don't need to run them.
+## Prompt Management (v5 Agentic-First)
 
 **Where prompts live:**
-- All prompts: `.clavix/outputs/prompts/`
-
-### Commands I Use (Reference)
-
-| What I Do | Command I Run |
-|-----------|---------------|
-| List saved prompts | `clavix prompts list` |
-| Get latest prompt | `clavix execute --latest` |
-| Get specific prompt | `clavix execute --id <id>` |
-| Run verification | `clavix verify --latest` |
-| Clean up executed | `clavix prompts clear --executed` |
-| Clean up stale (>30d) | `clavix prompts clear --stale` |
+- All prompts: `.clavix/outputs/prompts/*.md`
+- Metadata: In frontmatter of each `.md` file
 
-### Automatic Cleanup
+### How I Access Prompts (Native Tools)
 
-After I finish implementing and verification passes:
-- I clean up executed prompts automatically
-- Old prompts (>30 days) get flagged as stale for removal
-- I keep your storage tidy
+| 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
-2. I EXECUTE    →  /clavix:execute (you are here)
+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. I CLEANUP    →  Remove executed prompts
+4. MARK DONE    →  I update frontmatter with executed: true
 ```
 
 ---
 
 ## Finding Your Way Around
 
-Need to see what projects exist or check progress? I use these commands:
+Need to see what projects exist or check progress? I read the file system:
 
-| What I Need | Command I Run |
+| What I Need | How I Find It |
 |-------------|---------------|
-| See all projects | `clavix list` |
-| Check a specific project | `clavix show --output <project>` |
-| See active sessions | `clavix list --sessions` |
-| Find archived work | `clavix list --archived` |
+| 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/` |
 
 ---
 
@@ -271,7 +261,7 @@ If I can't get verification to pass after trying:
 
 ---
 
-## Agent Transparency (v4.11)
+## Agent Transparency (v5.0)
 
 ### CLI Reference (Commands I Execute)
 {{INCLUDE:agent-protocols/cli-reference.md}}

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

@@ -65,9 +65,9 @@ Me:     "All tasks complete! Your project is built."
 
 ### The Detailed Version
 
-**First time I run:**
+**First time I run (v5 Agentic-First):**
 
-1. **I check for your task list** - Load tasks.md from your PRD folder
+1. **I find your task list** - Read `tasks.md` from your PRD folder (`.clavix/outputs/<project>/tasks.md`)
 2. **I ask about git commits** (only if you have lots of tasks):
    > "You've got 12 tasks. Want me to create git commits as I go?
    >
@@ -78,36 +78,32 @@ Me:     "All tasks complete! Your project is built."
    >
    > Which do you prefer? (I'll default to 'none' if you don't care)"
 
-3. **I initialize tracking** - Run `clavix implement` to set up progress tracking
-4. **I start building** - First incomplete task
+3. **I start building** - First incomplete task
 
 **Each task I work on:**
 
 1. **Read the task** - Understand what needs to be built
 2. **Check the PRD** - Make sure I understand the requirements
-3. **Implement it** - Write code, create files, build features
-4. **Mark it complete** - Run `clavix task-complete {task-id}` automatically
-5. **Move to next** - The command shows me what's next
+3. **Implement it** - Write code, create files, build features using my native tools
+4. **Mark it complete** - Use Edit tool to change `- [ ]` to `- [x]` in tasks.md
+5. **Move to next** - Find the next incomplete task
 
 **If we get interrupted:**
 
 No problem! Just run `/clavix:implement` again and I pick up where we left off.
 The checkboxes in tasks.md track exactly what's done.
 
-## ⚠️ Critical Command: task-complete
+## ⚠️ How I Mark Tasks Complete (v5 Agentic-First)
 
-**After finishing EACH task, I MUST run:**
-```bash
-clavix task-complete <task-id>
-```
+**After finishing EACH task, I use my Edit tool to update tasks.md:**
 
-**Why this matters:**
-- Updates tasks.md automatically (checkboxes)
-- Tracks progress correctly in config
-- Triggers git commits (if enabled)
-- Shows me the next task
+Change: `- [ ] Task description` → `- [x] Task description`
 
-**NEVER manually edit tasks.md checkboxes** - always use this command.
+**Why this matters:**
+- Updates tasks.md directly (checkboxes)
+- Progress is tracked by counting checkboxes
+- Git commits (if enabled) are created with my Bash tool
+- I read tasks.md to find the next incomplete task
 
 ---
 
@@ -115,27 +111,19 @@ clavix task-complete <task-id>
 
 **I handle this automatically - you don't need to do anything.**
 
-### What Happens Behind the Scenes
-
-After I finish implementing a task, I run:
-```bash
-clavix task-complete {task-id}
-```
-
-This does several things:
-- Updates the checkbox in tasks.md ([ ] → [x])
-- Tracks progress in the config file
-- Creates a git commit (if you enabled that)
-- Shows me the next task
+### What Happens (v5 Agentic-First)
 
-### Why I Don't Edit Checkboxes Manually
+After I finish implementing a task:
 
-The command keeps everything in sync. If I edited the file directly, the progress tracking could get confused. Trust the system!
+1. **I use Edit tool** to change `- [ ]` to `- [x]` in tasks.md
+2. **I count progress** by reading tasks.md and counting checkboxes
+3. **I commit** (if you enabled that) using git commands
+4. **I find next task** by scanning for the next `- [ ]` in tasks.md
 
 ### What You'll See
 
 ```
-✓ Task complete: "Set up project structure" (phase-1-setup-1)
+✓ Task complete: "Set up project structure"
 
 Progress: 2/8 tasks (25%)
 
@@ -160,14 +148,14 @@ Starting now...
 
 ## Finding Your Way Around
 
-Need to see what projects exist or check progress? I use these commands:
+Need to see what projects exist or check progress? I read the file system:
 
-| What I Need | Command I Run |
+| What I Need | How I Find It |
 |-------------|---------------|
-| See all projects | `clavix list` |
-| Check a specific project | `clavix show --output <project>` |
-| See active sessions | `clavix list --sessions` |
-| Find archived work | `clavix list --archived` |
+| See all projects | List directories in `.clavix/outputs/` |
+| Check a specific project | Read `.clavix/outputs/<project>/` files |
+| See task progress | Read `.clavix/outputs/<project>/tasks.md` |
+| Find archived work | List `.clavix/outputs/archive/` |
 
 ## When I Can't Continue (Blocked Tasks)
 
@@ -314,7 +302,7 @@ You don't need to remember these - I handle all the tracking.
 
 ---
 
-## Agent Transparency (v4.9)
+## Agent Transparency (v5.0)
 
 ### Workflow State Detection
 {{INCLUDE:agent-protocols/state-awareness.md}}
@@ -348,14 +336,14 @@ You don't need to remember these - I handle all the tracking.
 > - Did you run `/clavix:plan` first?
 > - Is there a PRD folder in .clavix/outputs/?"
 
-### "Task command not working"
+### "Can't update tasks.md"
 
-**What happened:** The `clavix task-complete` command isn't recognized.
+**What happened:** I couldn't edit the tasks.md file to mark tasks complete.
 
 **What I'll do:**
-> "Having trouble with the task command. Let me check your Clavix version..."
+> "Having trouble updating tasks.md. Let me check permissions..."
 >
-> If it's outdated, I'll suggest: "Try `npm install -g clavix@latest` to update"
+> Common fixes: Check file permissions, ensure .clavix/outputs/ is writable
 
 ### "Can't find that task ID"