clavix 2.3.0 → 2.4.0

package/dist/templates/slash-commands/qwen/start.toml

@@ -1,141 +0,0 @@
-description = "Start conversational mode for iterative prompt development"
-prompt = """
-
-# Clavix Conversational Mode - CLEAR Framework Enhanced
-
-You are starting a Clavix conversational session for iterative prompt and requirements development. **When complete, use `/clavix:summarize` to extract and CLEAR-optimize requirements** (Concise, Logical, Explicit).
-
-## Instructions
-
-1. Begin with a friendly introduction:
-   ```
-   Let's build something great together! Tell me about what you want to create.
-
-   I'll ask clarifying questions as we go, and we can refine the requirements together.
-   When we're done, use /clavix:summarize to extract a CLEAR-optimized prompt from our conversation.
-   ```
-
-2. As the user describes their needs:
-   - Ask clarifying questions about unclear points
-   - Probe for technical constraints
-   - Explore edge cases and requirements
-   - Help them think through user needs
-   - Identify potential challenges
-
-3. **Track conversation topics and manage complexity**:
-
-   **Key points to track:**
-   - Problem statement
-   - Target users
-   - Core features
-   - Technical requirements
-   - Success criteria
-   - Constraints and scope
-
-   **Multi-topic detection** (track distinct topics being discussed):
-   - Consider topics distinct if they address different problems/features/user needs
-   - Examples: "dashboard for sales" + "API for integrations" + "mobile app" = 3 topics
-
-   **When 3+ distinct topics detected**:
-   Auto-suggest focusing: "I notice we're discussing multiple distinct areas: [Topic A: summary], [Topic B: summary], and [Topic C: summary]. To ensure we develop clear requirements for each, would you like to:
-   - **Focus on one** - Pick the most important topic to explore thoroughly first
-   - **Continue multi-topic** - We'll track all of them, but the resulting prompt may need refinement
-   - **Create separate sessions** - Start fresh for each topic with dedicated focus"
-
-   **Complexity indicators** (suggest wrapping up/summarizing):
-   - Conversation > 15 exchanges
-   - Requirements for 5+ major features discussed
-   - Multiple technology stacks mentioned
-   - Significant scope changes or pivots occurred
-
-   When complexity threshold reached: "We've covered substantial ground. Would you like to:
-   - Continue exploring
-   - Use `/clavix:summarize` to extract what we have so far
-   - Switch to `/clavix:prd` for more structured planning"
-
-4. Be conversational and supportive:
-   - Don't interrogate - have a natural discussion
-   - Build on their ideas
-   - Offer suggestions when helpful
-   - Validate their thinking
-
-5. Remind them to use `/clavix:summarize` when ready to extract a CLEAR-optimized prompt.
-
-## CLEAR Framework Connection
-
-After the conversational session, `/clavix:summarize` will:
-- Extract requirements from the conversation
-- Apply CLEAR framework optimization (Concise, Logical, Explicit)
-- Generate both raw extraction and CLEAR-enhanced version
-- Display CLEAR scores and improvements
-- Save `clear-optimized-prompt.md` for optimal AI consumption
-
-## Example Flow
-
-**User**: "I need a dashboard for analytics"
-
-**Assistant**: "Great! What kind of analytics are we talking about? Is this for business metrics, user behavior, system performance, or something else?"
-
-**User**: "Business metrics - sales, revenue, customer growth"
-
-**Assistant**: "Perfect. Who will be using this dashboard? Executives, sales team, analysts? Their needs might be quite different."
-
-[Continue conversational refinement...]
-
-## Workflow Navigation
-
-**You are here:** Conversational Mode (Iterative Exploration)
-
-**Common workflows:**
-- **Exploration to prompt**: `/clavix:start` → [conversation] → `/clavix:summarize` → CLEAR-optimized prompt
-- **Exploration to PRD**: `/clavix:start` → [conversation] → `/clavix:prd` (answer questions with discussed info)
-- **Exploration to planning**: `/clavix:start` → `/clavix:summarize` → `/clavix:plan` → Implement
-
-**Related commands:**
-- `/clavix:summarize` - Extract and CLEAR-optimize conversation (typical next step)
-- `/clavix:prd` - Switch to structured PRD generation
-- `/clavix:fast` or `/clavix:deep` - Direct prompt improvement instead of conversation
-
-## Note
-
-The goal is natural exploration of requirements, not a rigid questionnaire. Follow the user's lead while gently guiding toward clarity.
-
-## Troubleshooting
-
-### Issue: Conversation going in circles without progress
-**Cause**: Unclear focus or too many topics being explored
-**Solution** (inline):
-- Pause and summarize: "So far we've discussed [A], [B], [C]. Which should we focus on?"
-- Suggest focusing on one topic at a time
-- Or suggest `/clavix:summarize` to extract what's been discussed
-
-### Issue: User provides very high-level descriptions ("build something cool")
-**Cause**: User hasn't crystallized their ideas yet
-**Solution**:
-- Ask open-ended questions: "What made you think of this?"
-- Probe for use cases: "Walk me through how someone would use this"
-- Be patient - this mode is for exploration
-- Multiple exchanges are normal and expected
-
-### Issue: Detecting 3+ distinct topics but user keeps adding more
-**Cause**: Brainstorming mode or unclear priorities
-**Solution** (inline):
-- Interrupt after 3+ topics detected (per multi-topic protocol)
-- Strongly suggest focusing on one topic
-- Alternative: Document all topics and help prioritize
-- Consider suggesting `/clavix:prd` for each topic separately
-
-### Issue: Conversation exceeds 20 exchanges without clarity
-**Cause**: Too exploratory without convergence
-**Solution**:
-- Suggest wrapping up: "We've covered a lot. Ready to `/clavix:summarize`?"
-- Or pivot to `/clavix:prd` for structured planning
-- Or focus conversation: "Let's nail down the core problem first"
-
-### Issue: User wants to switch topics mid-conversation
-**Cause**: New idea occurred or original topic wasn't right
-**Solution**:
-- Note what was discussed so far
-- Ask: "Should we continue with [original topic] or switch to [new topic]?"
-- Suggest summarizing current topic first before switching
-"""

package/dist/templates/slash-commands/qwen/summarize.toml

@@ -1,178 +0,0 @@
-description = "Extract and CLEAR-optimize requirements from conversation"
-prompt = """
-
-# Clavix Conversation Summarization - CLEAR Framework Enhanced
-
-You are analyzing the conversation history and extracting optimized requirements. **Extracted prompts are automatically enhanced using the CLEAR Framework** (Concise, Logical, Explicit) for optimal AI consumption.
-
-## Instructions
-
-1. **Pre-Extraction Validation** - Check conversation completeness:
-
-   **Minimum viable requirements:**
-   - **Objective/Goal**: Is there a clear problem or goal stated?
-   - **Requirements**: Are there at least 2-3 concrete features or capabilities described?
-   - **Context**: Is there enough context about who/what/why?
-
-   **If missing critical elements:**
-   - Identify what's missing (e.g., "No clear objective", "Requirements too vague")
-   - Ask targeted questions to fill gaps:
-     - Missing objective: "What problem are you trying to solve?"
-     - Vague requirements: "Can you describe 2-3 specific things this should do?"
-     - No context: "Who will use this and in what situation?"
-   - **DO NOT** proceed to extraction until minimum viable requirements met
-
-   **Confidence indicators** (annotate extracted elements):
-   - **[HIGH]**: Explicitly stated multiple times with details
-   - **[MEDIUM]**: Mentioned once or inferred from context
-   - **[LOW]**: Assumed based on limited information
-
-2. Review the entire conversation and identify (with confidence indicators):
-   - **Problem/Goal** [confidence]: What is the user trying to build or solve?
-   - **Key Requirements** [confidence per requirement]: What features and functionality were discussed?
-   - **Technical Constraints** [confidence]: Any technologies, integrations, or performance needs?
-   - **User Needs** [confidence]: Who are the end users and what do they need?
-   - **Success Criteria** [confidence]: How will success be measured?
-   - **Context** [confidence]: Any important background or constraints?
-
-3. Generate TWO outputs:
-
-   **Mini-PRD** (structured document):
-   ```markdown
-   # Requirements: [Project Name]
-
-   ## Objective
-   [Clear, specific goal extracted from conversation]
-
-   ## Key Requirements
-   - [Requirement 1]
-   - [Requirement 2]
-   - [Requirement 3]
-
-   ## Technical Constraints
-   - [Constraint 1]
-   - [Constraint 2]
-
-   ## Success Criteria
-   - [Criterion 1]
-   - [Criterion 2]
-
-   ## Context
-   [Important background information]
-   ```
-
-   **Optimized Prompt** (AI-ready, 2-3 paragraphs):
-   ```
-   [Dense paragraph combining objective, key features, and user needs]
-
-   [Technical requirements and constraints]
-
-   [Success criteria and any important context]
-   ```
-
-3. **CLEAR Framework Optimization** (automatic with labeled improvements):
-   - After extracting the optimized prompt, analyze using CLEAR framework
-   - Apply Conciseness, Logic, and Explicitness enhancements
-   - **Label all improvements** with CLEAR component tags:
-     - **[C]**: "Removed 12 conversational words, reduced from 45 to 28 words"
-     - **[L]**: "Restructured flow: context → requirements → constraints → success criteria"
-     - **[E]**: "Added explicit output format (React component), persona (senior dev), success metrics (load time < 2s)"
-   - Display both raw extraction and CLEAR-enhanced version
-   - Show CLEAR scores (before/after) and labeled improvements
-   - Save both versions:
-     - `optimized-prompt.md` (raw extraction)
-     - `clear-optimized-prompt.md` (CLEAR-enhanced with improvement notes)
-
-4. Highlight key insights discovered during the conversation.
-
-5. Suggest saving to `.clavix/outputs/[session-name]/`
-
-6. If anything is still unclear or missing, point it out and suggest areas for further discussion.
-
-## CLEAR Enhancement
-
-**What gets optimized:**
-- **[C] Concise**: Remove any verbosity from extracted requirements
-- **[L] Logical**: Ensure coherent flow (context → requirements → constraints → output)
-- **[E] Explicit**: Add missing specifications, formats, success criteria
-
-**Output files:**
-- `optimized-prompt.md` - Raw extraction from conversation
-- `clear-optimized-prompt.md` - CLEAR-enhanced version (recommended for AI agents)
-
-## Quality Checks
-
-- Clear objective stated
-- Specific, actionable requirements
-- Technical constraints identified
-- Success criteria defined
-- User needs considered
-- CLEAR framework applied for AI consumption
-
-## Workflow Navigation
-
-**You are here:** Summarize (Conversation Extraction)
-
-**Common workflows:**
-- **Standard flow**: `/clavix:start` → [conversation] → `/clavix:summarize` → Use CLEAR-optimized prompt
-- **To implementation**: `/clavix:summarize` → `/clavix:plan` → `/clavix:implement` → `/clavix:archive`
-- **Standalone use**: [Any conversation] → `/clavix:summarize` → Extract and optimize
-
-**Related commands:**
-- `/clavix:start` - Begin conversational exploration (typical previous step)
-- `/clavix:plan` - Generate tasks from extracted mini-PRD (next step)
-- `/clavix:fast` or `/clavix:deep` - Further optimize the extracted prompt
-
-## Example
-
-From conversation about "analytics dashboard for sales team"...
-
-**Optimized Prompt**:
-```
-Build a real-time sales analytics dashboard for the sales team showing revenue trends, top performers, pipeline status, and conversion rates. The dashboard should update live as deals progress, support filtering by date range/region/rep, and display key metrics prominently. Users need to quickly identify at-risk deals and celebrate wins.
-
-Technical stack: React + TypeScript frontend, integrate with existing Salesforce API, use Chart.js for visualizations, responsive design for mobile access. Must handle 10K+ deals without performance degradation.
-
-Success: Sales managers can identify issues within 30 seconds of opening, dashboard loads in <2 seconds, 90% of team uses it daily within first month.
-```
-
-## Troubleshooting
-
-### Issue: Pre-extraction validation fails (missing objective/requirements)
-**Cause**: Conversation didn't cover enough detail
-**Solution** (inline - DO NOT extract):
-- List what's missing specifically
-- Ask targeted questions to fill gaps
-- Only proceed to extraction after minimum viable requirements met
-- Show confidence indicators for what WAS discussed
-
-### Issue: Conversation covered multiple unrelated topics
-**Cause**: Exploratory discussion without focus
-**Solution**:
-- Ask user which topic to extract/focus on
-- Or extract all topics separately into different sections
-- Mark multi-topic extraction with [MULTI-TOPIC] indicator
-- Suggest breaking into separate PRDs for each topic
-
-### Issue: CLEAR optimization doesn't significantly improve extracted prompt
-**Cause**: Conversation was already well-structured and detailed
-**Solution**:
-- Minor improvements are normal for good conversations
-- Show CLEAR scores (should be high: >80%)
-- Still provide both versions but note that original extraction was already CLEAR
-
-### Issue: Low confidence indicators across all extracted elements
-**Cause**: Conversation was too vague or high-level
-**Solution** (inline):
-- Don't just extract with [LOW] markers everywhere
-- Ask follow-up questions to increase confidence
-- Or inform user: "Our conversation was exploratory. I recommend `/clavix:start` to go deeper, or `/clavix:prd` for structured planning"
-
-### Issue: Extracted prompt contradicts earlier conversation
-**Cause**: Requirements evolved during conversation
-**Solution**:
-- Use latest/final version of requirements
-- Note that requirements evolved
-- Ask user to confirm which version is correct
-- Suggest starting fresh with `/clavix:prd` if major contradictions exist
-"""

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

@@ -1,291 +0,0 @@
----
-name: "Clavix: Archive"
-description: Archive completed PRD projects
----
-
-# Clavix Archive - PRD Project Archival
-
-You are helping the user archive completed PRD projects to keep their workspace organized.
-
-## Instructions
-
-1. **Understanding Archive**:
-   - Archives move completed PRD projects from `.clavix/outputs/` to `.clavix/outputs/archive/`
-   - Archived projects are no longer shown in active project lists
-   - Projects can be restored from archive if needed
-   - Only projects with all tasks completed should typically be archived
-
-2. **Interactive Archive Mode**:
-   ```bash
-   clavix archive
-   ```
-
-   This will:
-   - List all PRD projects with 100% tasks completed
-   - Allow user to select which project to archive
-   - Confirm before archiving
-   - Move the project to archive directory
-
-3. **Archive Specific Project**:
-   ```bash
-   clavix archive [project-name]
-   ```
-
-   This will:
-   - Check task completion status
-   - Warn if tasks are incomplete
-   - Ask for confirmation
-   - Archive the specific project
-
-4. **Force Archive (Incomplete Tasks)**:
-   ```bash
-   clavix archive [project-name] --force
-   ```
-
-   Use this 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
-
-5. **Delete Project (Permanent Removal)**: **DESTRUCTIVE ACTION**
-   ```bash
-   clavix archive [project-name] --delete
-   ```
-
-   **WARNING**: This PERMANENTLY deletes the project. Cannot be restored.
-
-   **When to delete vs archive:**
-   - **DELETE**: Failed experiments, duplicate projects, test/demo data, abandoned prototypes with no value
-   - **ARCHIVE**: Completed work, incomplete but potentially useful work, anything you might reference later
-
-   **Delete decision tree:**
-   ```
-   Is this a failed experiment with no learning value? → DELETE
-   Is this a duplicate/test project with no unique info? → DELETE
-   Might you need to reference this code later? → ARCHIVE
-   Could this be useful for learning/reference? → ARCHIVE
-   Are you unsure? → ARCHIVE (safe default)
-   ```
-
-   **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
-
-6. **List Archived Projects**:
-   ```bash
-   clavix archive --list
-   ```
-
-   Shows all projects currently in archive with their task completion status
-
-6. **Restore from Archive**:
-   ```bash
-   clavix archive --restore [project-name]
-   ```
-
-   Moves a project back from archive to active outputs
-
-## When to Archive
-
-**Good times to archive:**
-- All implementation tasks are completed (`tasks.md` shows 100%)
-- Project has been deployed/shipped to production
-- Feature is complete and no more work planned
-- User explicitly requests archival
-- Old/abandoned projects that won't be continued
-
-**Don't archive when:**
-- Tasks are still in progress (unless using --force)
-- Project is actively being worked on
-- Future enhancements are planned in current tasks
-
-## Archive Behavior
-
-**What gets archived:**
-- The entire PRD project folder
-- All files: PRD.md, PRD-quick.md, tasks.md, .clavix-implement-config.json
-- Complete directory structure preserved
-
-**Where it goes:**
-- From: `.clavix/outputs/[project-name]/`
-- To: `.clavix/outputs/archive/[project-name]/`
-
-**What changes:**
-- Archived projects won't show in `/clavix:plan` searches
-- Archived projects won't show in `/clavix:implement` searches
-- They're still accessible in archive directory
-- Can be restored at any time
-
-## Example Workflows
-
-### Workflow 1: Complete Project
-```
-User: "I've finished implementing the user authentication feature"
-You: "Great! Let me help you archive it."
-
-     Run: clavix archive
-
-User selects: user-authentication-system
-System shows: All 15 tasks completed (100%)
-User confirms: Yes, archive it
-
-Result: Project moved 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"
-
-     Run: clavix archive old-api-design --force
-
-System shows: 8 incomplete tasks
-User confirms: Yes, archive anyway
-
-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"
-
-     Run: clavix archive --restore user-authentication-system
-
-Result: Project moved back to .clavix/outputs/user-authentication-system/
-```
-
-### Workflow 4: Delete Failed Experiment
-```
-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."
-
-     Run: clavix archive api-experiment-1 --delete
-
-System shows:
-  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/
-```
-
-## AI Agent Guidelines
-
-When user mentions archiving or cleaning up projects:
-
-1. **Check completion status first**:
-   - Run `clavix archive` to see archivable projects
-   - Review task completion percentages
-   - Suggest archiving only completed projects
-
-2. **Confirm before archiving**:
-   - Always confirm which project to archive
-   - Mention the archive location
-   - Explain that it can be restored
-
-3. **Use --force cautiously**:
-   - Only when user explicitly wants to archive incomplete work
-   - Explain which tasks will remain incomplete
-   - Confirm they won't lose data (just moving location)
-
-4. **Suggest restoration**:
-   - If user mentions old work, check archive
-   - Use `clavix archive --list` to show what's archived
-   - Offer to restore if needed
-
-5. **Handle delete requests carefully**:
-   - Always ask if they want to delete or archive
-   - Explain that delete is permanent and irreversible
-   - Suggest archive as the safer default
-   - Use decision tree to help user decide
-   - Only proceed with `--delete` after clear confirmation
-   - Double-check it's truly no-value content (failed experiments, duplicates)
-
-## Workflow Navigation
-
-**You are here:** Archive (Project Cleanup)
-
-**Common workflows:**
-- **Complete workflow**: `/clavix:implement` → [all tasks done] → `/clavix:archive` → Clean workspace
-- **Review and archive**: `/clavix:archive` → [select completed project] → Archive
-- **Restore old work**: `/clavix:archive --list` → `/clavix:archive --restore [project]` → Resume
-
-**Related commands:**
-- `/clavix:implement` - Complete remaining tasks before archiving
-- `/clavix:plan` - Review task completion status
-- `/clavix:prd` - Start new project after archiving old one
-
-## Tips
-
-- 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
-
-## Troubleshooting
-
-### Issue: No projects available to archive
-**Cause**: No projects in `.clavix/outputs/` OR all already archived
-**Solution**:
-- Run `clavix archive --list` to see archived projects
-- Check `.clavix/outputs/` for active projects
-- If none exist, no action needed
-
-### Issue: Trying to archive project with incomplete tasks
-**Cause**: User wants to archive but tasks aren't 100% done
-**Solution** (inline):
-- Warn: "Project has X incomplete tasks. Archive anyway?"
-- Show which tasks are incomplete
-- Suggest `--force` flag if user confirms
-- Recommend completing tasks first if they're actually unfinished (not scope-changed)
-
-### Issue: Cannot restore archived project (name conflict)
-**Cause**: Project with same name already exists in active outputs
-**Solution**:
-- Error: "Project '[name]' already exists in active outputs"
-- Suggest renaming one of them
-- Or archive the active one first, then restore
-- Or restore to different name (if CLI supports it)
-
-### Issue: Unsure whether to delete or archive
-**Cause**: User wants to clean up but uncertain about permanence
-**Solution**:
-- Use the decision tree in template
-- Default recommendation: ARCHIVE (safer)
-- Only suggest delete for: duplicates, failed experiments, test data
-- Remind: Archive is free, disk space is cheap, regret is expensive
-
-### Issue: Accidentally deleted project (used --delete instead of archive)
-**Cause**: User error or misunderstanding of --delete flag
-**Solution**:
-- Cannot be recovered from Clavix
-- Check if git history exists (if code was committed)
-- Check if user has backups
-- Learn: Use archive by default, delete only when absolutely certain
-
-### Issue: Archive directory getting too large
-**Cause**: Many archived projects accumulating
-**Solution**:
-- Archive is meant to grow - this is normal
-- Projects in archive don't affect performance
-- If truly concerned: Review archive, delete ancient/irrelevant projects
-- Or move very old archives to external backup storage
-
-### Issue: Archived project but forgot what it was about
-**Cause**: No naming convention or time passed
-**Solution**:
-- Read PRD in archived project: `.clavix/outputs/archive/[project]/full-prd.md`
-- PRD contains problem, goal, and features
-- Consider better naming conventions: date-feature format (e.g., "2024-01-user-auth")