@monoes/monomindcli 1.6.0

package/.claude/commands/verify/start.md

@@ -0,0 +1,128 @@
+# 🔍 Verification Commands
+
+Truth verification system for ensuring code quality and correctness with a 0.95 accuracy threshold.
+
+## Overview
+
+The verification system provides real-time truth checking and validation for all agent tasks, ensuring high-quality outputs and automatic rollback on failures.
+
+## Subcommands
+
+### `verify check`
+Run verification checks on current code or agent outputs.
+
+```bash
+monomind verify check --file src/app.js
+monomind verify check --task "task-123"
+monomind verify check --threshold 0.98
+```
+
+### `verify rollback`
+Automatically rollback changes that fail verification.
+
+```bash
+monomind verify rollback --to-commit abc123
+monomind verify rollback --last-good
+monomind verify rollback --interactive
+```
+
+### `verify report`
+Generate verification reports and metrics.
+
+```bash
+monomind verify report --format json
+monomind verify report --export metrics.html
+monomind verify report --period 7d
+```
+
+### `verify dashboard`
+Launch interactive verification dashboard.
+
+```bash
+monomind verify dashboard
+monomind verify dashboard --port 3000
+monomind verify dashboard --export
+```
+
+## Configuration
+
+Default threshold: **0.95** (95% accuracy required)
+
+Configure in `.monomind/config.json`:
+```json
+{
+  "verification": {
+    "threshold": 0.95,
+    "autoRollback": true,
+    "gitIntegration": true,
+    "hooks": {
+      "preCommit": true,
+      "preTask": true,
+      "postEdit": true
+    }
+  }
+}
+```
+
+## Integration
+
+### With Swarm Commands
+```bash
+monomind swarm --verify --threshold 0.98
+monomind hive-mind --verify
+```
+
+### With Training Pipeline
+```bash
+monomind train --verify --rollback-on-fail
+```
+
+### With Pair Programming
+```bash
+monomind pair --verify --real-time
+```
+
+## Metrics
+
+- **Truth Score**: 0.0 to 1.0 (higher is better)
+- **Confidence Level**: Statistical confidence in verification
+- **Rollback Rate**: Percentage of changes rolled back
+- **Quality Improvement**: Trend over time
+
+## Examples
+
+### Basic Verification
+```bash
+# Verify current directory
+monomind verify check
+
+# Verify with custom threshold
+monomind verify check --threshold 0.99
+
+# Verify and auto-fix
+monomind verify check --auto-fix
+```
+
+### Advanced Workflows
+```bash
+# Continuous verification during development
+monomind verify watch --directory src/
+
+# Batch verification
+monomind verify batch --files "*.js" --parallel
+
+# Integration testing
+monomind verify integration --test-suite full
+```
+
+## Performance
+
+- Verification latency: <100ms for most checks
+- Rollback time: <1s for git-based rollback
+- Dashboard refresh: Real-time via WebSocket
+
+## Related Commands
+
+- `truth` - View truth scores and metrics
+- `pair` - Collaborative development with verification
+- `train` - Training with verification feedback

package/.claude/commands/workflows/README.md

@@ -0,0 +1,9 @@
+# Workflows Commands
+
+Commands for workflows operations in Monomind.
+
+## Available Commands
+
+- [workflow-create](./workflow-create.md)
+- [workflow-execute](./workflow-execute.md)
+- [workflow-export](./workflow-export.md)

package/.claude/commands/workflows/development.md

@@ -0,0 +1,78 @@
+# Development Workflow Coordination
+
+## Purpose
+Structure Claude Code's approach to complex development tasks for maximum efficiency.
+
+## Step-by-Step Coordination
+
+### 1. Initialize Development Framework
+```
+Tool: mcp__monomind__swarm_init
+Parameters: {"topology": "hierarchical", "maxAgents": 8, "strategy": "specialized"}
+```
+Creates hierarchical structure for organized, top-down development.
+
+### 2. Define Development Perspectives
+```
+Tool: mcp__monomind__agent_spawn
+Parameters: {
+  "type": "architect",
+  "name": "System Design",
+  "capabilities": ["api-design", "database-schema"]
+}
+```
+```
+Tool: mcp__monomind__agent_spawn
+Parameters: {
+  "type": "coder",
+  "name": "Implementation Focus",
+  "capabilities": ["nodejs", "typescript", "express"]
+}
+```
+```
+Tool: mcp__monomind__agent_spawn
+Parameters: {
+  "type": "tester",
+  "name": "Quality Assurance",
+  "capabilities": ["unit-testing", "integration-testing"]
+}
+```
+Sets up architectural and implementation thinking patterns.
+
+### 3. Coordinate Implementation
+```
+Tool: mcp__monomind__task_orchestrate
+Parameters: {
+  "task": "Build REST API with authentication",
+  "strategy": "parallel",
+  "priority": "high",
+  "dependencies": ["database setup", "auth system"]
+}
+```
+
+### 4. Monitor Progress
+```
+Tool: mcp__monomind__task_status
+Parameters: {"taskId": "api-build-task-123"}
+```
+
+## What Claude Code Actually Does
+1. Uses **Write** tool to create new files
+2. Uses **Edit/MultiEdit** tools for code modifications
+3. Uses **Bash** tool for testing and building
+4. Uses **TodoWrite** tool for task tracking
+5. Follows coordination patterns for systematic implementation
+
+Remember: All code is written by Claude Code using its native tools!
+
+## CLI Usage
+```bash
+# Start development workflow via CLI
+npx monomind workflow dev "REST API with auth"
+
+# Create custom workflow
+npx monomind workflow create --name "api-dev" --steps "design,implement,test,deploy"
+
+# Execute saved workflow
+npx monomind workflow execute api-dev
+```

package/.claude/commands/workflows/research.md

@@ -0,0 +1,63 @@
+# Research Workflow Coordination
+
+## Purpose
+Coordinate Claude Code's research activities for comprehensive, systematic exploration.
+
+## Step-by-Step Coordination
+
+### 1. Initialize Research Framework
+```
+Tool: mcp__monomind__swarm_init
+Parameters: {"topology": "mesh", "maxAgents": 5, "strategy": "balanced"}
+```
+Creates a mesh topology for comprehensive exploration from multiple angles.
+
+### 2. Define Research Perspectives
+```
+Tool: mcp__monomind__agent_spawn
+Parameters: {"type": "researcher", "name": "Literature Review"}
+```
+```
+Tool: mcp__monomind__agent_spawn  
+Parameters: {"type": "analyst", "name": "Data Analysis"}
+```
+Sets up different analytical approaches for Claude Code to use.
+
+### 3. Execute Coordinated Research
+```
+Tool: mcp__monomind__task_orchestrate
+Parameters: {
+  "task": "Research modern web frameworks performance",
+  "strategy": "adaptive",
+  "priority": "medium"
+}
+```
+
+### 4. Store Research Findings
+```
+Tool: mcp__monomind__memory_usage
+Parameters: {
+  "action": "store",
+  "key": "research_findings",
+  "value": "framework performance analysis results",
+  "namespace": "research"
+}
+```
+
+## What Claude Code Actually Does
+1. Uses **WebSearch** tool for finding resources
+2. Uses **Read** tool for analyzing documentation
+3. Uses **Task** tool for parallel exploration
+4. Synthesizes findings using coordination patterns
+5. Stores insights in memory for future reference
+
+Remember: The swarm coordinates HOW Claude Code researches, not WHAT it finds.
+
+## CLI Usage
+```bash
+# Start research workflow via CLI
+npx monomind workflow research "modern web frameworks"
+
+# Export research workflow
+npx monomind workflow export research --format json
+```

package/.claude/commands/workflows/workflow-create.md

@@ -0,0 +1,25 @@
+# workflow-create
+
+Create reusable workflow templates.
+
+## Usage
+```bash
+npx monomind workflow create [options]
+```
+
+## Options
+- `--name <name>` - Workflow name
+- `--from-history` - Create from history
+- `--interactive` - Interactive creation
+
+## Examples
+```bash
+# Create workflow
+npx monomind workflow create --name "deploy-api"
+
+# From history
+npx monomind workflow create --name "test-suite" --from-history
+
+# Interactive mode
+npx monomind workflow create --interactive
+```

package/.claude/commands/workflows/workflow-execute.md

@@ -0,0 +1,25 @@
+# workflow-execute
+
+Execute saved workflows.
+
+## Usage
+```bash
+npx monomind workflow execute [options]
+```
+
+## Options
+- `--name <name>` - Workflow name
+- `--params <json>` - Workflow parameters
+- `--dry-run` - Preview execution
+
+## Examples
+```bash
+# Execute workflow
+npx monomind workflow execute --name "deploy-api"
+
+# With parameters
+npx monomind workflow execute --name "test-suite" --params '{"env": "staging"}'
+
+# Dry run
+npx monomind workflow execute --name "deploy-api" --dry-run
+```

package/.claude/commands/workflows/workflow-export.md

@@ -0,0 +1,25 @@
+# workflow-export
+
+Export workflows for sharing.
+
+## Usage
+```bash
+npx monomind workflow export [options]
+```
+
+## Options
+- `--name <name>` - Workflow to export
+- `--format <type>` - Export format
+- `--include-history` - Include execution history
+
+## Examples
+```bash
+# Export workflow
+npx monomind workflow export --name "deploy-api"
+
+# As YAML
+npx monomind workflow export --name "test-suite" --format yaml
+
+# With history
+npx monomind workflow export --name "deploy-api" --include-history
+```

package/.claude/helpers/README.md

@@ -0,0 +1,105 @@
+# MonoMind v1 Helpers
+
+This directory contains helper scripts and utilities for v1 development.
+
+## 🚀 Quick Start
+
+```bash
+# Initialize v1 development environment
+.claude/helpers/v1.sh init
+
+# Quick status check
+.claude/helpers/v1.sh status
+
+# Update progress metrics
+.claude/helpers/v1.sh update domain 3
+.claude/helpers/v1.sh update agent 8
+.claude/helpers/v1.sh update security 2
+```
+
+## Available Helpers
+
+### 🎛️ v1 Master Tool
+
+- **`v1.sh`** - Main command-line interface for all v1 operations
+  ```bash
+  .claude/helpers/v1.sh help           # Show all commands
+  .claude/helpers/v1.sh status         # Quick development status
+  .claude/helpers/v1.sh update domain 3 # Update specific metrics
+  .claude/helpers/v1.sh validate       # Validate configuration
+  .claude/helpers/v1.sh full-status    # Complete status overview
+  ```
+
+### 📊 v1 Progress Management
+
+- **`update-v1-progress.sh`** - Update v1 development metrics
+  ```bash
+  # Usage examples:
+  .claude/helpers/update-v1-progress.sh domain 3      # Mark 3 domains complete
+  .claude/helpers/update-v1-progress.sh agent 8       # 8 agents active
+  .claude/helpers/update-v1-progress.sh security 2    # 2 CVEs fixed
+  .claude/helpers/update-v1-progress.sh performance 2.5x # Performance boost
+  .claude/helpers/update-v1-progress.sh status        # Show current status
+  ```
+
+### 🔍 Configuration Validation
+
+- **`validate-v1-config.sh`** - Comprehensive environment validation
+  - Checks all required directories and files
+  - Validates JSON configuration files
+  - Verifies Node.js and development tools
+  - Confirms Git repository status
+  - Validates file permissions
+
+### ⚡ Quick Status
+
+- **`v1-quick-status.sh`** - Compact development progress overview
+  - Shows domain, agent, and DDD progress
+  - Displays security and performance metrics
+  - Color-coded status indicators
+  - Current Git branch information
+
+## Helper Script Standards
+
+### File Naming
+
+- Use kebab-case: `update-v1-progress.sh`
+- Include version prefix: `v1-*` for v1-specific helpers
+- Use descriptive names that indicate purpose
+
+### Script Requirements
+
+- Must be executable (`chmod +x`)
+- Include proper error handling (`set -e`)
+- Provide usage help when called without arguments
+- Use consistent exit codes (0 = success, non-zero = error)
+
+### Configuration Integration
+
+Helpers are configured in `.claude/settings.json`:
+
+```json
+{
+  "helpers": {
+    "directory": ".claude/helpers",
+    "enabled": true,
+    "v1ProgressUpdater": ".claude/helpers/update-v1-progress.sh"
+  }
+}
+```
+
+## Development Guidelines
+
+1. **Security First**: All helpers must validate inputs
+2. **Idempotent**: Scripts should be safe to run multiple times
+3. **Fast Execution**: Keep helper execution under 1 second when possible
+4. **Clear Output**: Provide clear success/error messages
+5. **JSON Safe**: When updating JSON files, use `jq` for safety
+
+## Adding New Helpers
+
+1. Create script in `.claude/helpers/`
+2. Make executable: `chmod +x script-name.sh`
+3. Add to settings.json helpers section
+4. Test thoroughly before committing
+5. Update this README with usage documentation