clavix 2.3.0 → 2.4.0

package/dist/templates/slash-commands/cline/deep.md

@@ -1,207 +0,0 @@
----
-name: "Clavix: Deep"
-description: Full CLEAR framework analysis (C, L, E, A, R components)
----
-
-# Clavix Deep Mode - Full CLEAR Framework Analysis
-
-You are helping the user perform a comprehensive deep analysis using the full CLEAR Framework (all 5 components: Concise, Logical, Explicit, Adaptive, Reflective).
-
-## CLEAR Framework (Deep Mode)
-
-**What is CLEAR?**
-An academically-validated prompt engineering framework by Dr. Leo Lo (University of New Mexico).
-
-**Deep Mode Uses ALL Components:**
-- **[C] Concise**: Remove verbosity, pleasantries, unnecessary words
-- **[L] Logical**: Ensure coherent sequencing (context → requirements → constraints → output)
-- **[E] Explicit**: Add persona, format, tone, success criteria
-- **[A] Adaptive**: Generate alternative phrasings, structures, flexibility
-- **[R] Reflective**: Create validation checklists, edge cases, quality criteria
-
-## Instructions
-
-1. Take the user's prompt: `{{ARGS}}`
-
-2. **Apply Full CLEAR Framework** (C, L, E, A, R):
-
-   - **Conciseness [C]**: Detailed verbosity analysis
-   - **Logic [L]**: Comprehensive flow analysis
-   - **Explicitness [E]**: Complete specification check
-   - **Adaptiveness [A]**: Multiple variations and approaches
-   - **Reflectiveness [R]**: Full validation and edge case analysis
-
-3. **Strategic Scope Detection** (before detailed analysis):
-
-   **Check for strategic concerns** by identifying keywords/themes:
-   - **Architecture**: system design, microservices, monolith, architecture patterns, scalability patterns
-   - **Security**: authentication, authorization, encryption, security, OWASP, vulnerabilities, threat model
-   - **Scalability**: load balancing, caching, database scaling, performance optimization, high availability
-   - **Infrastructure**: deployment, CI/CD, DevOps, cloud infrastructure, containers, orchestration
-   - **Business Impact**: ROI, business metrics, KPIs, stakeholder impact, market analysis
-
-   **If 3+ strategic keywords detected**:
-   Ask the user: "I notice this involves strategic decisions around [detected themes]. These topics benefit from PRD-style planning with business context and architectural considerations. Would you like to:
-   - Switch to `/clavix:prd` for comprehensive strategic planning (recommended)
-   - Continue with deep mode for prompt-level analysis only"
-
-   **If user chooses to continue**, proceed with deep analysis but remind them at the end that `/clavix:prd` is available for strategic planning.
-
-4. **Generate Comprehensive Output**:
-
-   a. **CLEAR Assessment** (all 5 components with scores)
-
-   b. **CLEAR-Optimized Prompt** (applying all components)
-
-   c. **CLEAR Changes Made** (labeled with [C], [L], [E], [A], [R])
-
-   d. **Adaptive Variations [A]**:
-      - 2-3 alternative phrasings
-      - Alternative structures (user story, job story, structured)
-      - Temperature recommendations
-      - Explain when each approach is most appropriate
-
-   e. **Reflection Checklist [R]**:
-      - Validation steps for accuracy
-      - Edge cases to consider
-      - "What could go wrong" analysis
-      - Fact-checking steps
-      - Quality criteria
-
-4. **CLEAR-labeled educational feedback**:
-   - Label all changes with CLEAR component tags
-   - Example: "[C] Removed 15 unnecessary pleasantries"
-   - Example: "[A] See Alternative Structures for 3 different approaches"
-   - Example: "[R] See Reflection Checklist for 5 validation steps"
-
-5. Present everything in comprehensive, CLEAR-organized format.
-
-## Deep Mode Features
-
-**Include (Full CLEAR Framework):**
-- **[C, L, E]**: All fast mode analysis (conciseness, logic, explicitness)
-- **[A] Adaptive**: Alternative phrasings, structures, flexibility, temperature
-- **[R] Reflective**: Validation checklist, edge cases, quality criteria, fact-checking
-- **CLEAR Assessment**: All 5 component scores
-- **CLEAR-labeled Changes**: Educational feedback showing which component improved what
-
-**Do NOT include (these belong in `/clavix:prd`):**
-- System architecture recommendations
-- Security best practices
-- Scalability strategy
-- Business impact analysis
-
-## Example
-
-If user provides: "Create a login page"
-
-Output:
-```
-## Analysis
-[All fast mode analysis: gaps, ambiguities, strengths, suggestions]
-
-## Changes Made
-- Added authentication context and user needs
-- Specified technical stack and constraints
-- Defined success criteria and expected output
-
-## Alternative Phrasings
-1. "Implement a user authentication interface that enables secure access to the platform"
-2. "Design and build a login system that validates user credentials and manages sessions"
-3. "Create an authentication flow that allows registered users to access their accounts"
-
-## Edge Cases to Consider
-- What happens when a user enters incorrect credentials 3+ times?
-- How to handle users who've forgotten both email and password?
-- What about users trying to log in from a new device?
-- How to handle session expiration during active use?
-
-## Implementation Examples
-**Good:**
-- Prompt specifies authentication method, error handling, and accessibility requirements
-- Includes context about existing auth system and integration points
-- Defines measurable success criteria (load time, accessibility score)
-
-**Bad:**
-- "Make a login page" - no context, constraints, or success criteria
-- Missing technical stack and integration requirements
-- No consideration of security or user experience
-
-## Alternative Prompt Structures
-1. **User Story**: "As a registered user, I want to log into my account so that I can access my personalized dashboard"
-   → Focuses on user value and benefits
-
-2. **Job Story**: "When I visit the app, I want to authenticate securely, so I can access my saved data"
-   → Emphasizes context and motivation
-
-3. **Structured Sections**: Objective, Requirements, Constraints, Success Criteria
-   → Provides comprehensive organization
-
-## What Could Go Wrong
-- Without security requirements, implementation might miss OWASP best practices
-- Vague "login page" could be interpreted as OAuth, email/password, or social login
-- Missing error handling specification could lead to poor UX
-- No accessibility requirements might exclude users with disabilities
-
-## Improved Prompt
-[Structured prompt with all sections]
-```
-
-## When to Use Deep vs Fast vs PRD
-
-- **Fast mode** (`/clavix:fast`): C, L, E components - quick CLEAR cleanup
-- **Deep mode** (`/clavix:deep`): Full CLEAR (C, L, E, A, R) - comprehensive analysis with alternatives and validation
-- **PRD mode** (`/clavix:prd`): CLEAR-validated PRD generation - strategic planning with architecture decisions
-
-## Workflow Navigation
-
-**You are here:** Deep Mode (Comprehensive CLEAR Analysis)
-
-**Common workflows:**
-- **Thorough analysis**: `/clavix:deep` → Use optimized prompt + alternatives
-- **Escalate to strategic**: `/clavix:deep` → (detects strategic scope) → `/clavix:prd` → Plan → Implement → Archive
-- **From fast mode**: `/clavix:fast` → (suggests) `/clavix:deep` → Full analysis with A & R components
-
-**Related commands:**
-- `/clavix:fast` - Quick CLEAR improvements (C, L, E only)
-- `/clavix:prd` - Strategic PRD generation for architecture/business decisions
-- `/clavix:start` - Conversational mode for exploring unclear requirements
-
-## Tips
-
-- **Apply full CLEAR framework** systematically: all 5 components
-- Label all changes with CLEAR components for education
-- Deep mode focuses on **prompt-level** CLEAR analysis, not strategic architecture
-- Use **[A] Adaptive** to explore alternative approaches
-- Use **[R] Reflective** to identify edge cases and validation needs
-- For architecture, security, and scalability, recommend `/clavix:prd`
-
-## Troubleshooting
-
-### Issue: Strategic scope detected but user wants to continue with deep mode
-**Cause**: User prefers deep analysis over PRD generation
-**Solution**:
-- Proceed with deep mode as requested
-- Remind at end that `/clavix:prd` is available for strategic planning
-- Focus on prompt-level CLEAR analysis, exclude architecture recommendations
-
-### Issue: Too many alternative variations making output overwhelming
-**Cause**: Adaptive component generating many options
-**Solution**:
-- Limit to 2-3 most distinct alternatives
-- Focus on meaningfully different approaches (not minor wording changes)
-- Group similar variations together
-
-### Issue: Reflective validation finding too many edge cases
-**Cause**: Complex prompt with many potential failure modes
-**Solution**:
-- Prioritize most likely or highest-impact edge cases
-- Group related edge cases
-- Suggest documenting all edge cases in PRD for complex projects
-
-### Issue: Deep analysis still feels insufficient for complex project
-**Cause**: Project needs strategic planning, not just prompt analysis
-**Solution**:
-- Switch to `/clavix:prd` for comprehensive planning
-- Deep mode is for prompts, PRD mode is for projects
-- Use PRD workflow: PRD → Plan → Implement

package/dist/templates/slash-commands/cline/fast.md

@@ -1,183 +0,0 @@
----
-name: "Clavix: Fast"
-description: CLEAR-guided quick improvements (C, L, E components)
----
-
-# Clavix Fast Mode - CLEAR Framework Quick Improvement
-
-You are helping the user improve their prompt using Clavix's fast mode, which applies the CLEAR Framework (Concise, Logical, Explicit components) with smart triage.
-
-## CLEAR Framework (Fast Mode)
-
-**What is CLEAR?**
-An academically-validated prompt engineering framework by Dr. Leo Lo (University of New Mexico).
-
-**Fast Mode Uses:**
-- **[C] Concise**: Remove verbosity, pleasantries, unnecessary words
-- **[L] Logical**: Ensure coherent sequencing (context → requirements → constraints → output)
-- **[E] Explicit**: Add persona, format, tone, success criteria
-
-**Deep Mode Adds:** [A] Adaptive variations, [R] Reflective validation (use `/clavix:deep` for these)
-
-## Instructions
-
-1. Take the user's prompt: `{{ARGS}}`
-
-2. **CLEAR Analysis** - Assess the prompt using three components:
-
-   - **Conciseness [C]**: Identify verbose language, pleasantries ("please", "could you"), unnecessary qualifiers
-   - **Logic [L]**: Check sequencing and flow - is information presented coherently?
-   - **Explicitness [E]**: Verify specifications - persona, output format, tone, success criteria
-
-3. **CLEAR-Aware Smart Triage**: Use multi-factor content-quality assessment to determine if deep analysis is needed:
-
-   **Primary Indicators** (CLEAR scores - most important):
-   - **Low CLEAR scores**: Conciseness < 60%, Logic < 60%, or Explicitness < 50%
-
-   **Secondary Indicators** (content quality):
-   - **Missing critical elements**: 3+ missing from (context, tech stack, success criteria, user needs, expected output)
-   - **Scope clarity**: Contains vague words ("app", "system", "project", "feature") without defining what/who/why
-   - **Requirement completeness**: Lacks actionable requirements or measurable outcomes
-   - **Context depth**: Extremely brief (<15 words) OR overly verbose (>100 words without structure)
-
-   **Escalation Decision**:
-   - If **Low CLEAR scores** + **2+ Secondary Indicators**: **Strongly recommend `/clavix:deep`**
-   - If **Low CLEAR scores** only: **Suggest `/clavix:deep`** but can proceed with fast mode
-   - Explain which CLEAR component needs deeper analysis and why
-
-   Ask the user:
-   - Switch to deep mode (recommended when strongly recommended)
-   - Continue with fast mode (acceptable for suggestion-level, but at their own risk for strong recommendation)
-
-4. Generate a **CLEAR-optimized** structured prompt with these sections:
-   **Objective**: Clear, specific goal
-   **Requirements**: Detailed, actionable requirements
-   **Technical Constraints**: Technologies, performance needs, integrations
-   **Expected Output**: What the result should look like
-   **Success Criteria**: How to measure completion
-
-5. **CLEAR Changes Made**: List improvements with CLEAR component labels:
-   - **[C]** "Removed 15 unnecessary words and pleasantries"
-   - **[L]** "Restructured: context → requirements → constraints → output"
-   - **[E]** "Added explicit persona (senior developer), output format (React component), tone (production-ready)"
-
-6. Present the CLEAR-optimized prompt in a code block for easy copying.
-
-## Fast Mode Features
-
-**Include (CLEAR C, L, E):**
-- **CLEAR Assessment** (Conciseness, Logic, Explicitness scores with issues)
-- Single CLEAR-optimized improved prompt
-- **CLEAR Changes Made** (labeled with [C], [L], [E] components)
-- Recommendation to use deep mode for Adaptive & Reflective components
-
-**Skip (use `/clavix:deep` instead):**
-- **[A] Adaptive**: Alternative phrasings, structures, flexibility
-- **[R] Reflective**: Validation checklists, edge cases, quality criteria
-- Strategic analysis (architecture, security - that's for `/clavix:prd`)
-
-## Example
-
-If user provides: "Please could you maybe help me create a login page?"
-
-Output:
-```
-## CLEAR Analysis (Fast Mode)
-
-### CLEAR Framework Assessment:
-
-[C] Conciseness: 45%
-    • 4 unnecessary pleasantries detected ("Please", "could you", "maybe", "help me")
-    • Low signal-to-noise ratio (core request is only 4 words)
-
-[L] Logic: 85%
-    • Single request, coherent but minimal
-    • Suggested flow: Context → Requirements → Constraints → Output
-
-[E] Explicitness: 25%
-    • Missing: persona, output format, tone, success criteria, technical constraints
-    • No authentication context specified
-
-Overall CLEAR Score: 51% (needs-improvement)
-
-Recommendation:
-For Adaptive variations (A) and Reflective validation (R), use:
-  clavix deep "<your prompt>"
-
-### CLEAR-Optimized Prompt:
-
-Objective: Build a secure user authentication login page
-
-Requirements:
-- Email and password input fields with validation
-- "Remember me" checkbox
-- "Forgot password" link
-- Clear error messages for invalid credentials
-- Responsive design for mobile and desktop
-
-Technical Constraints:
-- Use React with TypeScript
-- Integrate with existing JWT authentication API
-- Follow WCAG 2.1 AA accessibility standards
-
-Expected Output:
-- Fully functional login component
-- Unit tests with >80% coverage
-
-Success Criteria:
-- Users can log in successfully
-- Invalid credentials show appropriate errors
-- Page is accessible via keyboard navigation
-
-### CLEAR Changes Made:
-
-[C] Removed 4 pleasantries ("Please", "could you", "maybe", "help me"), reduced from 11 words to core intent
-[L] Structured logical flow: Objective → Requirements → Technical Constraints → Expected Output → Success Criteria
-[E] Added explicit specifications: React TypeScript persona, component output format, production-ready tone, accessibility criteria
-```
-
-## Workflow Navigation
-
-**You are here:** Fast Mode (Quick CLEAR Improvement)
-
-**Common workflows:**
-- **Quick cleanup**: `/clavix:fast` → Use improved prompt
-- **Need more depth**: `/clavix:fast` → (suggests) `/clavix:deep` → Comprehensive analysis
-- **Strategic planning**: `/clavix:fast` → (suggests) `/clavix:prd` → Plan → Implement → Archive
-
-**Related commands:**
-- `/clavix:deep` - Full CLEAR analysis (all 5 components: C, L, E, A, R)
-- `/clavix:prd` - Generate PRD for strategic planning
-- `/clavix:start` - Conversational exploration before prompting
-
-## Tips
-
-- **Apply CLEAR framework** systematically: C, L, E components
-- Use **CLEAR-aware triage** to prevent inadequate analysis
-- Label all changes with CLEAR components for education
-- For comprehensive analysis with [A] and [R], recommend `/clavix:deep`
-- For strategic planning, recommend `/clavix:prd`
-- Focus on making prompts **CLEAR** quickly
-
-## Troubleshooting
-
-### Issue: Triage keeps recommending deep mode
-**Cause**: Prompt has low CLEAR scores + multiple secondary indicators
-**Solution**:
-- Accept the recommendation - deep mode will provide better analysis
-- OR improve prompt manually before running fast mode again
-- Check which CLEAR component is scoring low and address it
-
-### Issue: Can't determine if prompt is complex enough for deep mode
-**Cause**: Borderline CLEAR scores or unclear content quality
-**Solution**:
-- Err on side of fast mode first
-- If output feels insufficient, escalate to `/clavix:deep`
-- Use triage as guidance, not absolute rule
-
-### Issue: Improved prompt still feels incomplete
-**Cause**: Fast mode only applies C, L, E components
-**Solution**:
-- Use `/clavix:deep` for Adaptive variations and Reflective validation
-- OR use `/clavix:prd` if strategic planning is needed
-- Fast mode is for quick cleanup, not comprehensive analysis

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

@@ -1,267 +0,0 @@
----
-name: "Clavix: Implement"
-description: Execute tasks from the implementation plan
----
-
-# Clavix Implement - AI-Assisted Task Execution
-
-You are helping the user implement tasks from their task plan with AI assistance.
-
-## Instructions
-
-1. **Run the implement command**:
-   ```bash
-   clavix implement
-   ```
-
-   This will:
-   - Show interactive PRD selection (if multiple projects exist)
-   - Locate the `tasks.md` file for the selected/specified project
-   - Show current progress
-   - Display the next incomplete task
-   - Prompt for git auto-commit preferences
-   - Create a config file for the AI agent
-
-   **Note**: You can skip the selection menu by specifying a project:
-   ```bash
-   clavix implement --project my-feature
-   ```
-
-2. **As the AI agent, you should**:
-
-   a. **Read the configuration**:
-      - Load `.clavix-implement-config.json` from the PRD folder
-      - This contains: commit strategy, current task, and progress stats
-
-   b. **Read the PRD for context**:
-      - Open the full PRD to understand requirements
-      - Reference specific sections mentioned in tasks
-
-   c. **Read tasks.md**:
-      - Find the first incomplete task (marked `- [ ]`)
-      - This is your current task to implement
-
-   d. **Implement the task**:
-      - Write/modify code as needed
-      - Follow CLEAR principles
-      - Use PRD requirements as your guide
-      - Ask user for clarification if needed
-
-   e. **Mark task as completed**:
-      - In `tasks.md`, change `- [ ] Task description` to `- [x] Task description`
-      - Update only the specific task you just completed
-
-   f. **Create git commit (if enabled)**:
-      - Check the `commitStrategy` in config
-      - If `per-task`: commit after each task
-      - If `per-5-tasks`: commit after every 5 tasks
-      - If `per-phase`: commit when all tasks in a phase are done
-      - Use descriptive commit messages with task description
-
-   g. **Move to next task**:
-      - Find the next `- [ ]` task in tasks.md
-      - Repeat the process
-
-3. **Session Resume**:
-   - When user runs `clavix implement` again, it automatically picks up from the last incomplete task
-   - No manual tracking needed - the checkboxes in tasks.md are the source of truth
-
-## Git Commit Format
-
-When creating commits, use this format:
-
-```
-clavix: [task description]
-
-Completed tasks:
-- Task 1
-- Task 2
-
-Project: [project-name]
-Generated by Clavix /clavix:implement
-```
-
-## Important Rules
-
-**DO**:
-- Read tasks.md to find the current task
-- Implement ONE task at a time
-- Mark tasks complete by changing `[ ]` to `[x]`
-- Create commits based on the strategy in config
-- Reference the PRD for detailed requirements
-- Ask for clarification when tasks are ambiguous
-
-**DON'T**:
-- Skip tasks or implement out of order
-- Mark tasks complete before actually implementing them
-- Modify multiple tasks' checkboxes at once (only current task)
-- Create commits if strategy is 'none'
-- Assume what code to write - use PRD as source of truth
-
-## Task Blocking Protocol
-
-**When a task is blocked** (cannot be completed), follow this protocol:
-
-### Step 1: Detect Blocking Issues
-
-Common blocking scenarios:
-- **Missing dependencies**: API keys, credentials, external services not available
-- **Unclear requirements**: Task description too vague or conflicts with PRD
-- **External blockers**: Need design assets, content, or third-party integration not ready
-- **Technical blockers**: Required library incompatible, environment issue, access problem
-- **Resource blockers**: Need database, server, or infrastructure not yet set up
-
-### Step 2: Immediate User Communication
-
-**Stop implementation and ask user immediately:**
-```
-"Task blocked: [Task description]
-
-Blocking issue: [Specific blocker, e.g., 'Missing Stripe API key for payment integration']
-
-Options to proceed:
-1. **Provide missing resource** - [What user needs to provide]
-2. **Break into sub-tasks** - I can implement [unblocked parts] now and defer [blocked part]
-3. **Skip for now** - Mark as [BLOCKED], continue with next task, return later
-
-Which option would you like?"
-```
-
-### Step 3: Resolution Strategies
-
-**Option A: User Provides Resource**
-- Wait for user to provide (API key, design, clarification)
-- Once provided, continue with task implementation
-
-**Option B: Create Sub-Tasks** (preferred when possible)
-- Identify what CAN be done without the blocker
-- Break task into unblocked sub-tasks
-- Example: "Implement payment integration" →
-  - [x] Create payment service interface (can do now)
-  - [ ] [BLOCKED: Need Stripe API key] Integrate Stripe SDK
-  - [ ] Add payment UI components (can do now)
-- Implement unblocked sub-tasks, mark blocked ones with [BLOCKED] tag
-
-**Option C: Skip and Mark Blocked**
-- Add [BLOCKED] tag to task in tasks.md: `- [ ] [BLOCKED: Missing API key] Task description`
-- Note the blocker reason
-- Move to next task
-- Return to blocked tasks when unblocked
-
-### Step 4: Track Blocked Tasks
-
-**In tasks.md, use [BLOCKED] notation:**
-```markdown
-## Phase 2: Integration
-- [x] Create API client structure
-- [ ] [BLOCKED: Waiting for API endpoint spec] Implement data sync
-- [ ] Add error handling for API calls
-```
-
-**At end of implement session:**
-- List all blocked tasks
-- Remind user what's needed to unblock each one
-- Suggest next steps
-
-### Common Blocking Scenarios & Resolutions
-
-| Blocker Type | Detection | Resolution |
-|--------------|-----------|------------|
-| Missing API key/credentials | Code requires authentication | Ask user for credentials OR stub with mock for now |
-| Vague requirements | Unclear what to implement | Ask specific questions OR propose implementation for approval |
-| External dependency | Service/API not available | Create interface/mock OR skip and defer |
-| Environment issue | Can't run/test code | Ask user to fix environment OR implement without testing (note risk) |
-| Design/content missing | Need specific assets | Create placeholder OR wait for actual assets |
-
-## Example Workflow
-
-```
-1. User runs: clavix implement
-2. Command shows: "Next task: Implement user authentication"
-3. You (AI agent):
-   - Read PRD authentication requirements
-   - Implement auth logic
-   - Write tests
-   - Update tasks.md: - [x] Implement user authentication
-   - Create git commit (if enabled)
-   - Find next task in tasks.md
-   - Continue or wait for user
-```
-
-## Workflow Navigation
-
-**You are here:** Implement (Task Execution)
-
-**Common workflows:**
-- **Full workflow**: `/clavix:plan` → `/clavix:implement` → [execute all tasks] → `/clavix:archive`
-- **Resume work**: `/clavix:implement` → Continue from last incomplete task
-- **Iterative**: `/clavix:implement` → [complete task] → [pause] → `/clavix:implement` → [continue]
-
-**Related commands:**
-- `/clavix:plan` - Generate/regenerate task breakdown (previous step)
-- `/clavix:archive` - Archive completed project (final step)
-- `/clavix:prd` - Review PRD for context during implementation
-
-## Tips
-
-- The implementation is meant to be iterative and collaborative
-- User can pause/resume at any time
-- Tasks are designed to be atomic and independently implementable
-- Use the PRD as the authoritative source for "what to build"
-- Use tasks.md as the guide for "in what order"
-
-## Troubleshooting
-
-### Issue: `.clavix-implement-config.json` not found
-**Cause**: User hasn't run `clavix implement` CLI command first
-**Solution** (inline):
-- Error: "Config file not found. Run `clavix implement` first to initialize"
-- CLI creates config and shows first task
-- AI agent should wait for config before proceeding
-
-### Issue: Cannot find next incomplete task in tasks.md
-**Cause**: All tasks completed OR tasks.md corrupted
-**Solution**:
-- Check if all tasks are `[x]` - if yes, congratulate completion!
-- Suggest `/clavix:archive` for completed project
-- If tasks.md corrupted, ask user to review/regenerate
-
-### Issue: Task description unclear or conflicts with PRD
-**Cause**: Task breakdown was too vague or PRD changed
-**Solution** (inline - covered by Task Blocking Protocol):
-- Stop and ask user for clarification
-- Reference PRD section if mentioned
-- Propose interpretation for user approval
-- Update task description in tasks.md after clarification
-
-### Issue: Git commit fails (wrong strategy, hook error, etc.)
-**Cause**: Git configuration issue or commit hook failure
-**Solution**:
-- Show error to user
-- Suggest checking git status manually
-- Ask if should continue without commit or fix issue first
-- Note: Commits are convenience, not blocker - can proceed without
-
-### Issue: Multiple [BLOCKED] tasks accumulating
-**Cause**: Dependencies or blockers not being resolved
-**Solution**:
-- After 3+ blocked tasks, pause and report to user
-- List all blockers and what's needed to resolve
-- Ask user to prioritize: unblock tasks OR continue with unblocked ones
-- Consider if project should be paused until blockers cleared
-
-### Issue: Task completed but tests failing
-**Cause**: Implementation doesn't meet requirements
-**Solution**:
-- Do NOT mark task as complete if tests fail
-- Fix failing tests before marking [x]
-- If tests are incorrectly written, fix tests first
-- Task isn't done until tests pass
-
-### Issue: Implementing in wrong order (skipped dependencies)
-**Cause**: AI agent or user jumped ahead
-**Solution**:
-- Stop and review tasks.md order
-- Check if skipped task was a dependency
-- Implement missed dependency first
-- Follow sequential order unless explicitly instructed otherwise