@intentsolutionsio/sugar 2.0.0 → 2.0.2

package/commands/sugar-run.md

@@ -22,12 +22,14 @@ 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
@@ -37,12 +39,14 @@ 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
@@ -51,12 +55,14 @@ 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
@@ -65,12 +71,14 @@ 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
@@ -83,28 +91,33 @@ 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
@@ -113,6 +126,7 @@ Verify:
 ## Execution Monitoring
 
 ### Log Monitoring
+
 ```bash
 # Real-time log viewing
 tail -f .sugar/sugar.log
@@ -125,6 +139,7 @@ grep "task-123" .sugar/sugar.log
 ```
 
 ### Status Checks
+
 ```bash
 # Check status periodically
 sugar status
@@ -137,7 +152,9 @@ sugar list --status completed --limit 5
 ```
 
 ### Performance Metrics
+
 Monitor:
+
 - Task completion rate
 - Average execution time
 - Failure rate
@@ -148,27 +165,35 @@ 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
@@ -212,6 +237,7 @@ kill -9 $(cat .sugar/sugar.pid)
 ### Common Issues
 
 **"Claude CLI not found"**
+
 ```bash
 # Verify installation
 claude --version
@@ -222,11 +248,13 @@ 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
@@ -239,6 +267,7 @@ 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
@@ -246,18 +275,21 @@ 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
@@ -266,6 +298,7 @@ grep -A 10 "task-123" .sugar/sugar.log
 ## Integration with Development Workflow
 
 ### Development Sessions
+
 ```bash
 # Morning startup
 sugar run --once    # Process overnight discoveries
@@ -279,6 +312,7 @@ git commit -am "Day's work"
 ```
 
 ### CI/CD Integration
+
 ```bash
 # Single task execution
 sugar run --once --validate
@@ -291,6 +325,7 @@ sugar run --once
 ## Expected Behavior
 
 ### Normal Operation
+
 - Tasks selected by priority
 - Execution respects timeout settings
 - Progress logged to `.sugar/sugar.log`
@@ -298,6 +333,7 @@ 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
@@ -306,14 +342,17 @@ 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,11 +15,13 @@ 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
@@ -27,17 +29,20 @@ 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
@@ -46,6 +51,7 @@ Shows:
 ## Presentation Format
 
 ### Standard Status View
+
 Present information in a clear, scannable format:
 
 ```
@@ -71,6 +77,7 @@ Present information in a clear, scannable format:
 ```
 
 ### Detailed Status View
+
 When `--detailed` is requested:
 
 ```bash
@@ -80,6 +87,7 @@ sugar list --status failed
 ```
 
 Include:
+
 - Configuration summary (loop interval, concurrency)
 - Failed tasks with error details
 - Active tasks with progress indicators
@@ -91,24 +99,28 @@ 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`
@@ -132,14 +144,17 @@ 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
 
@@ -164,6 +179,7 @@ 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,18 +15,22 @@ 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
@@ -45,11 +49,13 @@ 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,
@@ -65,6 +71,7 @@ sugar add "Task Title" --json --description '{
 ```
 
 ### Urgent Task
+
 ```bash
 sugar add "Critical task" --type bug_fix --urgent
 ```
@@ -79,14 +86,17 @@ 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

@@ -0,0 +1,140 @@
+---
+name: sugar-thinking
+description: View Claude's thinking logs for task execution
+usage: /sugar-thinking [TASK_ID] [OPTIONS]
+examples:
+  - /sugar-thinking task-abc123
+  - /sugar-thinking --list
+  - /sugar-thinking task-abc123 --stats
+---
+
+# Sugar Thinking Command
+
+View Claude's thinking logs for task execution, providing visibility into Claude's reasoning process during autonomous task execution.
+
+## Usage
+
+```
+/sugar-thinking [TASK_ID] [OPTIONS]
+```
+
+## Description
+
+The `sugar-thinking` command allows you to view the captured thinking blocks from Claude's execution of tasks. This provides critical visibility into how Claude approaches problems and makes decisions during autonomous development.
+
+## Arguments
+
+- `TASK_ID` - Task ID to view thinking for (required unless using `--list`)
+
+## Options
+
+- `--list, -l` - List all available thinking logs
+- `--stats, -s` - Show thinking statistics only (blocks count, characters, tools considered)
+
+## Examples
+
+### View Full Thinking Log
+
+```
+/sugar-thinking task-abc123
+```
+
+Shows the complete thinking log with timestamped thinking blocks.
+
+### View Statistics Only
+
+```
+/sugar-thinking task-abc123 --stats
+```
+
+Shows summary statistics including:
+
+- Total thinking blocks captured
+- Total characters
+- Average thinking block length
+- Tools considered during thinking
+- Timing information
+
+### List All Thinking Logs
+
+```
+/sugar-thinking --list
+```
+
+Lists all available thinking logs sorted by modification time (newest first).
+
+## Output Format
+
+### Full Log
+
+```markdown
+# Thinking Log: Implement user authentication
+
+**Task ID:** abc123
+**Started:** 2026-01-07T10:30:00
+
+---
+
+## 10:30:05
+
+First, I need to understand the current authentication system...
+
+---
+
+## 10:30:12
+
+*Considering tool: `Read`*
+
+I should read the existing auth module to see what's already implemented...
+
+---
+
+## Summary
+
+- **Total thinking blocks:** 15
+- **Total characters:** 3,247
+- **Average length:** 216 chars
+- **Tools considered:** Read, Write, Bash
+
+**Completed:** 2026-01-07T10:35:42
+```
+
+### Statistics
+
+```
+📊 Thinking Statistics for: Implement user authentication
+Task ID: abc123
+============================================================
+
+  Thinking Blocks: 15
+  Total Characters: 3,247
+  Average Length: 216 chars
+  Tools Considered: Read, Write, Bash
+  First Thinking: 2026-01-07T10:30:05
+  Last Thinking: 2026-01-07T10:35:40
+
+  Full log: .sugar/thinking/abc123.md
+```
+
+## Use Cases
+
+1. **Debugging Failed Tasks**: Understand why a task succeeded or failed by reviewing Claude's reasoning
+2. **Learning from Claude**: Study how Claude approaches different types of problems
+3. **Verification**: Confirm Claude is following expected strategies and approaches
+4. **Pattern Analysis**: Track thinking patterns across tasks to improve prompts
+
+## Configuration
+
+Thinking capture is enabled by default. To disable, add to `.sugar/config.yaml`:
+
+```yaml
+sugar:
+  executor:
+    thinking_capture: false
+```
+
+## Related Commands
+
+- `/sugar-status` - View overall system status
+- `/sugar-view` - View task details
+- `/sugar-task-type` - Manage task type configurations

package/hooks/hooks.json

@@ -1,4 +1,47 @@
 {
-  "description": "Sugar task management - hooks disabled pending schema migration. Original hooks used unsupported features (filters, conditions, throttling). Plugin skills and MCP server still functional.",
-  "hooks": {}
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "echo '{\"decision\": \"approve\"}'"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Bash",
+        "description": "Suggest task creation when errors are detected",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "if echo \"$CLAUDE_TOOL_OUTPUT\" | grep -qiE 'error|exception|fail|bug|crash'; then echo 'Error detected! Consider creating a Sugar task to fix this with /sugar-task' >&2; fi; exit 0"
+          }
+        ]
+      },
+      {
+        "matcher": "Bash",
+        "description": "Suggest task update after git commits",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "if echo \"$CLAUDE_TOOL_INPUT\" | grep -q 'git commit'; then echo 'Code committed! If this completes a Sugar task, use: sugar update TASK_ID --status completed' >&2; fi; exit 0"
+          }
+        ]
+      }
+    ],
+    "Notification": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "echo 'Sugar notification hook'"
+          }
+        ]
+      }
+    ]
+  }
 }

package/package.json

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

package/skills/managing-autonomous-development/SKILL.md

@@ -6,7 +6,7 @@ allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*)
 version: 1.0.0
 author: Steven Leggett <contact@roboticforce.io>
 license: MIT
-compatible-with: claude-code, codex, openclaw
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 tags: [devops, workflow, autonomous-development]
 ---
 # Managing Autonomous Development
@@ -61,5 +61,5 @@ Manage Sugar's autonomous development workflows: create development tasks, check
 ## Resources
 
 - Sugar plugin documentation: https://github.com/roboticforce/sugar
-- Task automation patterns: https://roboticforce.io/docs/sugar/
-- Autonomous development best practices: https://roboticforce.io/docs/sugar/best-practices/
+- Task automation patterns:
+- Autonomous development best practices: best-practices/

package/skills/managing-autonomous-development/assets/README.md

@@ -5,6 +5,7 @@ This directory contains static assets used by this skill.
 ## Purpose
 
 Assets can include:
+
 - Configuration files (JSON, YAML)
 - Data files
 - Templates

package/skills/managing-autonomous-development/references/README.md

@@ -5,6 +5,7 @@ This directory contains reference materials that enhance this skill's capabiliti
 ## Purpose
 
 References can include:
+
 - Code examples
 - Style guides
 - Best practices documentation

package/skills/managing-autonomous-development/scripts/README.md

@@ -5,6 +5,7 @@ This directory contains optional helper scripts that support this skill's functi
 ## Purpose
 
 Scripts here can be:
+
 - Referenced by the skill for automation
 - Used as examples for users
 - Executed during skill activation