@intentsolutionsio/sugar 2.0.2 → 2.0.3

package/commands/sugar-run.md

@@ -22,14 +22,12 @@ You are a Sugar autonomous execution specialist. Your role is to safely guide us
 ## Execution Modes
 
 ### 1. Validation Mode (Recommended First)
-
 ```bash
 sugar run --validate
 ```
 
 **Purpose**: Verify configuration and environment before execution
 **Checks**:
-
 - Configuration file validity
 - Claude CLI availability
 - Database accessibility
@@ -39,14 +37,12 @@ sugar run --validate
 **Output**: Comprehensive validation report
 
 ### 2. Dry Run Mode (Recommended for Testing)
-
 ```bash
 sugar run --dry-run --once
 ```
 
 **Purpose**: Simulate execution without making changes
 **Benefits**:
-
 - Safe testing of configuration
 - Preview of what Sugar would do
 - Identify issues before real execution
@@ -55,14 +51,12 @@ sugar run --dry-run --once
 **Output**: Detailed simulation log
 
 ### 3. Single Cycle Mode
-
 ```bash
 sugar run --once
 ```
 
 **Purpose**: Execute one autonomous cycle and exit
 **Use Cases**:
-
 - Testing real execution
 - Processing urgent tasks
 - Controlled development sessions
@@ -71,14 +65,12 @@ sugar run --once
 **Output**: Execution results and summary
 
 ### 4. Continuous Autonomous Mode
-
 ```bash
 sugar run
 ```
 
 **Purpose**: Continuous autonomous development
 **Behavior**:
-
 - Runs indefinitely until stopped
 - Executes tasks based on priority
 - Discovers new work automatically
@@ -91,33 +83,28 @@ sugar run
 Before starting autonomous mode, verify:
 
 ### Configuration
-
 ```bash
 cat .sugar/config.yaml | grep -E "dry_run|claude.command|loop_interval"
 ```
 
 Check:
-
 - [ ] `dry_run: false` (for real execution)
 - [ ] Valid Claude CLI path
 - [ ] Reasonable loop_interval (300 seconds recommended)
 - [ ] Appropriate max_concurrent_work setting
 
 ### Environment
-
 - [ ] Sugar initialized: `.sugar/` directory exists
 - [ ] Claude Code CLI accessible
 - [ ] Project in git repository (recommended)
 - [ ] Proper gitignore configuration
 
 ### Task Queue
-
 ```bash
 sugar list --limit 5
 ```
 
 Verify:
-
 - Tasks are well-defined
 - Priorities are appropriate
 - No duplicate work
@@ -126,7 +113,6 @@ Verify:
 ## Execution Monitoring
 
 ### Log Monitoring
-
 ```bash
 # Real-time log viewing
 tail -f .sugar/sugar.log
@@ -139,7 +125,6 @@ grep "task-123" .sugar/sugar.log
 ```
 
 ### Status Checks
-
 ```bash
 # Check status periodically
 sugar status
@@ -152,9 +137,7 @@ sugar list --status completed --limit 5
 ```
 
 ### Performance Metrics
-
 Monitor:
-
 - Task completion rate
 - Average execution time
 - Failure rate
@@ -165,35 +148,27 @@ Monitor:
 ### Interactive Workflow
 
 1. **Validate Configuration**
-
    ```bash
    sugar run --validate
    ```
-
    Review output, fix any issues
 
 2. **Test with Dry Run**
-
    ```bash
    sugar run --dry-run --once
    ```
-
    Verify task selection and approach
 
 3. **Single Cycle Test**
-
    ```bash
    sugar run --once
    ```
-
    Execute one real task, verify results
 
 4. **Start Continuous Mode**
-
    ```bash
    sugar run
    ```
-
    Monitor actively for first few cycles
 
 ### Background Execution
@@ -237,7 +212,6 @@ kill -9 $(cat .sugar/sugar.pid)
 ### Common Issues
 
 **"Claude CLI not found"**
-
 ```bash
 # Verify installation
 claude --version
@@ -248,13 +222,11 @@ vim .sugar/config.yaml
 ```
 
 **"No tasks to execute"**
-
 - Run `/sugar-status` to check queue
 - Create tasks with `/sugar-task`
 - Run `/sugar-analyze` for work discovery
 
 **"Tasks failing repeatedly"**
-
 ```bash
 # Review failed tasks
 sugar list --status failed
@@ -267,7 +239,6 @@ grep -A 10 "task-123" .sugar/sugar.log
 ```
 
 **"Performance issues"**
-
 - Reduce `max_concurrent_work` in config
 - Increase `loop_interval` for less frequent cycles
 - Check Claude API rate limits
@@ -275,21 +246,18 @@ grep -A 10 "task-123" .sugar/sugar.log
 ## Safety Reminders
 
 ### Before Starting
-
 - ✅ Test with `--dry-run` first
 - ✅ Start with `--once` for validation
 - ✅ Monitor logs actively
 - ✅ Have backups (git commits)
 
 ### During Execution
-
 - ✅ Regular status checks
 - ✅ Review completed tasks
 - ✅ Monitor for failures
 - ✅ Watch resource usage
 
 ### After Starting
-
 - ✅ Verify task completions
 - ✅ Review generated code
 - ✅ Run tests
@@ -298,7 +266,6 @@ grep -A 10 "task-123" .sugar/sugar.log
 ## Integration with Development Workflow
 
 ### Development Sessions
-
 ```bash
 # Morning startup
 sugar run --once    # Process overnight discoveries
@@ -312,7 +279,6 @@ git commit -am "Day's work"
 ```
 
 ### CI/CD Integration
-
 ```bash
 # Single task execution
 sugar run --once --validate
@@ -325,7 +291,6 @@ sugar run --once
 ## Expected Behavior
 
 ### Normal Operation
-
 - Tasks selected by priority
 - Execution respects timeout settings
 - Progress logged to `.sugar/sugar.log`
@@ -333,7 +298,6 @@ sugar run --once
 - Graceful handling of failures
 
 ### Resource Usage
-
 - Moderate CPU during execution
 - Memory usage scales with task complexity
 - Disk I/O for logging and database
@@ -342,17 +306,14 @@ sugar run --once
 ## Example Interactions
 
 ### Example 1: First Time Setup
-
 User: "/sugar-run"
 Response: Guides through validation → dry-run → single cycle → continuous mode, with safety checks at each step
 
 ### Example 2: Quick Execution
-
 User: "/sugar-run --once"
 Response: Executes one cycle, reports results, suggests monitoring commands
 
 ### Example 3: Production Deployment
-
 User: "/sugar-run --validate"
 Response: Validates config, then guides through background execution setup with proper monitoring
 

package/commands/sugar-status.md

@@ -15,13 +15,11 @@ You are a Sugar status reporting specialist. Your role is to provide clear, acti
 When a user invokes `/sugar-status`, collect and present:
 
 ### 1. System Status
-
 ```bash
 sugar status
 ```
 
 This provides:
-
 - Total tasks in the system
 - Task breakdown by status (pending, active, completed, failed)
 - Active execution status
@@ -29,20 +27,17 @@ This provides:
 - Configuration summary
 
 ### 2. Recent Task Queue
-
 ```bash
 sugar list --limit 10
 ```
 
 Shows:
-
 - Recent tasks with their status
 - Task IDs for reference
 - Execution times and agent assignments
 - Priority indicators
 
 ### 3. Execution Metrics (if available)
-
 - Average task completion time
 - Success rate
 - Active autonomous execution status
@@ -51,7 +46,6 @@ Shows:
 ## Presentation Format
 
 ### Standard Status View
-
 Present information in a clear, scannable format:
 
 ```
@@ -77,7 +71,6 @@ Present information in a clear, scannable format:
 ```
 
 ### Detailed Status View
-
 When `--detailed` is requested:
 
 ```bash
@@ -87,7 +80,6 @@ sugar list --status failed
 ```
 
 Include:
-
 - Configuration summary (loop interval, concurrency)
 - Failed tasks with error details
 - Active tasks with progress indicators
@@ -99,28 +91,24 @@ Include:
 Based on the status, provide contextual recommendations:
 
 ### If No Tasks
-
 - "No tasks in queue. Consider:"
   - Creating manual tasks with `/sugar-task`
   - Running code analysis with `/sugar-analyze`
   - Checking error logs for issues
 
 ### If Many Pending Tasks
-
 - "Large task backlog detected. Consider:"
   - Starting autonomous mode: `sugar run`
   - Reviewing priorities: `sugar list --priority 5`
   - Adjusting concurrency in `.sugar/config.yaml`
 
 ### If Failed Tasks
-
 - "Failed tasks detected. Recommend:"
   - Review failures: `sugar view TASK_ID`
   - Check logs: `.sugar/sugar.log`
   - Retry or remove failed tasks
 
 ### If Autonomous Mode Stopped
-
 - "Autonomous mode not running. To start:"
   - Test with: `sugar run --dry-run --once`
   - Start: `sugar run`
@@ -144,17 +132,14 @@ Assess system health and flag issues:
 ## Example Interactions
 
 ### Example 1: Healthy System
-
 User: "/sugar-status"
 Response: Shows balanced task distribution, recent completions, autonomous mode running
 
 ### Example 2: Needs Attention
-
 User: "/sugar-status"
 Response: Highlights 15 pending tasks, suggests starting autonomous mode, shows last execution was 2 hours ago
 
 ### Example 3: Troubleshooting
-
 User: "/sugar-status --detailed"
 Response: Deep dive into failed tasks, configuration review, log file locations, specific remediation steps
 
@@ -179,7 +164,6 @@ sugar view TASK_ID
 ## Follow-up Actions
 
 After presenting status, suggest relevant next steps:
-
 - View specific tasks: `/sugar-review`
 - Create new tasks: `/sugar-task`
 - Analyze codebase: `/sugar-analyze`

package/commands/sugar-task.md

@@ -15,22 +15,18 @@ You are a Sugar task creation specialist. Your role is to help users create comp
 When a user invokes `/sugar-task`, guide them through creating a detailed task specification:
 
 ### 1. Basic Information (Required)
-
 - **Title**: Clear, actionable task description
 - **Type**: bug_fix, feature, test, refactor, documentation, or custom types
 - **Priority**: 1 (low) to 5 (urgent)
 
 ### 2. Rich Context (Recommended for complex tasks)
-
 - **Context**: Detailed description of what needs to be done and why
 - **Business Context**: Strategic importance and business value
 - **Technical Requirements**: Specific technical constraints or requirements
 - **Success Criteria**: Measurable outcomes that define completion
 
 ### 3. Agent Assignments (Optional for multi-faceted work)
-
 Suggest appropriate specialized agents:
-
 - `ux_design_specialist`: UI/UX design and customer experience
 - `backend_developer`: Server architecture and database design
 - `frontend_developer`: User-facing applications and interfaces
@@ -49,13 +45,11 @@ Suggest appropriate specialized agents:
 ## Command Formats
 
 ### Simple Task
-
 ```bash
 sugar add "Task title" --type TYPE --priority N
 ```
 
 ### Rich Task with JSON Context
-
 ```bash
 sugar add "Task Title" --json --description '{
   "priority": 1-5,
@@ -71,7 +65,6 @@ sugar add "Task Title" --json --description '{
 ```
 
 ### Urgent Task
-
 ```bash
 sugar add "Critical task" --type bug_fix --urgent
 ```
@@ -86,17 +79,14 @@ sugar add "Critical task" --type bug_fix --urgent
 ## Examples
 
 ### Example 1: Simple Bug Fix
-
 User: "/sugar-task Fix login timeout issue"
 Response: Creates task with type=bug_fix, priority=4, suggests checking error logs
 
 ### Example 2: Complex Feature
-
 User: "/sugar-task Build customer dashboard"
 Response: Asks clarifying questions, builds rich JSON context with UX designer and frontend developer assignments, success criteria for responsive design
 
 ### Example 3: Urgent Security Issue
-
 User: "/sugar-task Critical auth vulnerability --urgent"
 Response: Creates high-priority task with type=bug_fix, assigns tech-lead agent, emphasizes immediate attention
 

package/commands/sugar-thinking.md

@@ -48,7 +48,6 @@ Shows the complete thinking log with timestamped thinking blocks.
 ```
 
 Shows summary statistics including:
-
 - Total thinking blocks captured
 - Total characters
 - Average thinking block length

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intentsolutionsio/sugar",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "description": "Sugar 🍰 - AI-powered autonomous development system for complex, multi-step development tasks",
   "keywords": [
     "autonomous",