moflo 4.9.21 → 4.9.22

package/.claude/commands/claude-flow-memory.md

@@ -1,107 +0,0 @@
----
-name: claude-flow-memory
-description: Interact with Claude-Flow memory system
----
-
-# 🧠 Claude-Flow Memory System
-
-The memory system provides persistent storage for cross-session and cross-agent collaboration with CRDT-based conflict resolution.
-
-## Store Information
-```bash
-# Store with default namespace
-./claude-flow memory store "key" "value"
-
-# Store with specific namespace
-./claude-flow memory store "architecture_decisions" "microservices with API gateway" --namespace arch
-```
-
-## Query Memory
-```bash
-# Search across all namespaces
-./claude-flow memory query "authentication"
-
-# Search with filters
-./claude-flow memory query "API design" --namespace arch --limit 10
-```
-
-## Memory Statistics
-```bash
-# Show overall statistics
-./claude-flow memory stats
-
-# Show namespace-specific stats
-./claude-flow memory stats --namespace project
-```
-
-## Export/Import
-```bash
-# Export all memory
-./claude-flow memory export full-backup.json
-
-# Export specific namespace
-./claude-flow memory export project-backup.json --namespace project
-
-# Import memory
-./claude-flow memory import backup.json
-```
-
-## Cleanup Operations
-```bash
-# Clean entries older than 30 days
-./claude-flow memory cleanup --days 30
-
-# Clean specific namespace
-./claude-flow memory cleanup --namespace temp --days 7
-```
-
-## 🗂️ Namespaces
-- **default** - General storage
-- **agents** - Agent-specific data and state
-- **tasks** - Task information and results
-- **sessions** - Session history and context
-- **swarm** - Swarm coordination and objectives
-- **project** - Project-specific context
-- **spec** - Requirements and specifications
-- **arch** - Architecture decisions
-- **impl** - Implementation notes
-- **test** - Test results and coverage
-- **debug** - Debug logs and fixes
-
-## 🎯 Best Practices
-
-### Naming Conventions
-- Use descriptive, searchable keys
-- Include timestamp for time-sensitive data
-- Prefix with component name for clarity
-
-### Organization
-- Use namespaces to categorize data
-- Store related data together
-- Keep values concise but complete
-
-### Maintenance
-- Regular backups with export
-- Clean old data periodically
-- Monitor storage statistics
-- Compress large values
-
-## Examples
-
-### Store SPARC context:
-```bash
-./claude-flow memory store "spec_auth_requirements" "OAuth2 + JWT with refresh tokens" --namespace spec
-./claude-flow memory store "arch_api_design" "RESTful microservices with GraphQL gateway" --namespace arch
-./claude-flow memory store "test_coverage_auth" "95% coverage, all tests passing" --namespace test
-```
-
-### Query project decisions:
-```bash
-./claude-flow memory query "authentication" --namespace arch --limit 5
-./claude-flow memory query "test results" --namespace test
-```
-
-### Backup project memory:
-```bash
-./claude-flow memory export project-$(date +%Y%m%d).json --namespace project
-```

package/.claude/commands/claude-flow-swarm.md

@@ -1,205 +0,0 @@
----
-name: claude-flow-swarm
-description: Coordinate multi-agent swarms for complex tasks
----
-
-# 🐝 Claude-Flow Swarm Coordination
-
-Advanced multi-agent coordination system with timeout-free execution, distributed memory sharing, and intelligent load balancing.
-
-## Basic Usage
-```bash
-./claude-flow swarm "your complex task" --strategy <type> [options]
-```
-
-## 🎯 Swarm Strategies
-- **auto** - Automatic strategy selection based on task analysis
-- **development** - Code implementation with review and testing
-- **research** - Information gathering and synthesis
-- **analysis** - Data processing and pattern identification
-- **testing** - Comprehensive quality assurance
-- **optimization** - Performance tuning and refactoring
-- **maintenance** - System updates and bug fixes
-
-## 🤖 Agent Types
-- **coordinator** - Plans and delegates tasks to other agents
-- **developer** - Writes code and implements solutions
-- **researcher** - Gathers and analyzes information
-- **analyzer** - Identifies patterns and generates insights
-- **tester** - Creates and runs tests for quality assurance
-- **reviewer** - Performs code and design reviews
-- **documenter** - Creates documentation and guides
-- **monitor** - Tracks performance and system health
-- **specialist** - Domain-specific expert agents
-
-## 🔄 Coordination Modes
-- **centralized** - Single coordinator manages all agents (default)
-- **distributed** - Multiple coordinators share management
-- **hierarchical** - Tree structure with nested coordination
-- **mesh** - Peer-to-peer agent collaboration
-- **hybrid** - Mixed coordination strategies
-
-## ⚙️ Common Options
-- `--strategy <type>` - Execution strategy
-- `--mode <type>` - Coordination mode
-- `--max-agents <n>` - Maximum concurrent agents (default: 5)
-- `--timeout <minutes>` - Timeout in minutes (default: 60)
-- `--background` - Run in background for tasks > 30 minutes
-- `--monitor` - Enable real-time monitoring
-- `--ui` - Launch terminal UI interface
-- `--parallel` - Enable parallel execution
-- `--distributed` - Enable distributed coordination
-- `--review` - Enable peer review process
-- `--testing` - Include automated testing
-- `--encryption` - Enable data encryption
-- `--verbose` - Detailed logging output
-- `--dry-run` - Show configuration without executing
-
-## 🌟 Examples
-
-### Development Swarm with Review
-```bash
-./claude-flow swarm "Build e-commerce REST API" \
-  --strategy development \
-  --monitor \
-  --review \
-  --testing
-```
-
-### Long-Running Research Swarm
-```bash
-./claude-flow swarm "Analyze AI market trends 2024-2025" \
-  --strategy research \
-  --background \
-  --distributed \
-  --max-agents 8
-```
-
-### Performance Optimization Swarm
-```bash
-./claude-flow swarm "Optimize database queries and API performance" \
-  --strategy optimization \
-  --testing \
-  --parallel \
-  --monitor
-```
-
-### Enterprise Development Swarm
-```bash
-./claude-flow swarm "Implement secure payment processing system" \
-  --strategy development \
-  --mode distributed \
-  --max-agents 10 \
-  --parallel \
-  --monitor \
-  --review \
-  --testing \
-  --encryption \
-  --verbose
-```
-
-### Testing and QA Swarm
-```bash
-./claude-flow swarm "Comprehensive security audit and testing" \
-  --strategy testing \
-  --review \
-  --verbose \
-  --max-agents 6
-```
-
-## 📊 Monitoring and Control
-
-### Real-time monitoring:
-```bash
-# Monitor swarm activity
-./claude-flow monitor
-
-# Monitor specific component
-./claude-flow monitor --focus swarm
-```
-
-### Check swarm status:
-```bash
-# Overall system status
-./claude-flow status
-
-# Detailed swarm status
-./claude-flow status --verbose
-```
-
-### View agent activity:
-```bash
-# List all agents
-./claude-flow agent list
-
-# Agent details
-./claude-flow agent info <agent-id>
-```
-
-## 💾 Memory Integration
-
-Swarms automatically use distributed memory for collaboration:
-
-```bash
-# Store swarm objectives
-./claude-flow memory store "swarm_objective" "Build scalable API" --namespace swarm
-
-# Query swarm progress
-./claude-flow memory query "swarm_progress" --namespace swarm
-
-# Export swarm memory
-./claude-flow memory export swarm-results.json --namespace swarm
-```
-
-## 🎯 Key Features
-
-### Timeout-Free Execution
-- Background mode for long-running tasks
-- State persistence across sessions
-- Automatic checkpoint recovery
-
-### Work Stealing & Load Balancing
-- Dynamic task redistribution
-- Automatic agent scaling
-- Resource-aware scheduling
-
-### Circuit Breakers & Fault Tolerance
-- Automatic retry with exponential backoff
-- Graceful degradation
-- Health monitoring and recovery
-
-### Real-Time Collaboration
-- Cross-agent communication
-- Shared memory access
-- Event-driven coordination
-
-### Enterprise Security
-- Role-based access control
-- Audit logging
-- Data encryption
-- Input validation
-
-## 🔧 Advanced Configuration
-
-### Dry run to preview:
-```bash
-./claude-flow swarm "Test task" --dry-run --strategy development
-```
-
-### Custom quality thresholds:
-```bash
-./claude-flow swarm "High quality API" \
-  --strategy development \
-  --quality-threshold 0.95
-```
-
-### Scheduling algorithms:
-- FIFO (First In, First Out)
-- Priority-based
-- Deadline-driven
-- Shortest Job First
-- Critical Path
-- Resource-aware
-- Adaptive
-
-For detailed documentation, see: https://github.com/ruvnet/claude-code-flow/docs/swarm-system.md

package/.claude/commands/flo-simplify.md

@@ -1,101 +0,0 @@
----
-description: Review changed code for reuse, quality, and efficiency, then fix any issues found. Sizes review effort to the diff and routes the cheapest model that fits.
----
-
-# /flo-simplify — Adaptive Gate-Compliant Code Review
-
-Review changed code for reuse, quality, and efficiency. **Effort scales with diff size; model is routed for cost.** A 5-line comment trim does not get 3 Opus agents.
-
-## Phase 0: Gate prerequisites
-
-These satisfy the memory-first and task-create-first gates. Always do them before any Agent spawn.
-
-1. **Memory search** — `mcp__moflo__memory_search — query: "code quality patterns", namespace: "patterns"`
-2. **Task create** — `TaskCreate — subject: "🔍 [Reviewer] Simplify changed code"`
-
-## Phase 1: Identify the diff
-
-```bash
-git diff HEAD          # working tree
-git diff main...HEAD   # committed since branch base
-```
-
-Treat the union as the diff. Note whether `/flo-simplify` already ran on this branch in this session — if so, you are in a **validation pass** (Phase 4 below).
-
-## Phase 2: Classify the diff
-
-Pick the smallest tier the diff genuinely fits.
-
-| Tier | Trigger | Action |
-|------|---------|--------|
-| **TRIVIAL** | ≤10 net LOC, single file, comments/formatting/local renames only | Self-review, zero agents |
-| **SMALL** | ≤200 net LOC, ≤2 files, no API/dependency change | **One agent** (default for most diffs, including critical surface) |
-| **NORMAL** | ≥3 files, OR >200 LOC, OR public API change, OR new/removed dependency, OR cross-cutting refactor | Three parallel agents |
-
-Critical-surface files (launcher, hooks, MCP wiring) raise the *care* of the agent prompt — sharper checklist, blast-radius framing — they do **not** automatically escalate to NORMAL. Risk-weighted ≠ headcount-weighted.
-
-## Phase 3: Use the classifier's model (skip for TRIVIAL)
-
-The classifier returns the right model for the tier — no separate router call needed:
-
-- `sonnet` (default) — real logic edits, single agent or 3-agent fan-out.
-- `haiku` — mostly-relocation diffs (mechanical moves; pattern-matching beats deep reasoning).
-- `opus` — never returned. Code review is breadth-bound, not depth-bound; sonnet 3-way IS the high-effort tier.
-
-Pass the classifier's `model` field verbatim to Agent's `model` parameter. If you fell back to prose rules in Phase 2 (no classifier), default to `sonnet`.
-
-## Phase 4: Validation pass (re-run after fixes from a prior simplify)
-
-If `/flo-simplify` already ran on this branch in this session AND the only edits since are fixes the prior pass surfaced, **default to TRIVIAL self-review** regardless of LOC count. The fan-out happened; the fix is small relative to the already-reviewed diff.
-
-Escalate one tier (self-review → SMALL agent) only if the fix introduced a new file, a new exported symbol, a new dependency, or a control-flow change not covered by the original findings. Never escalate a validation pass to NORMAL.
-
-## Phase 5: Run the appropriate review
-
-### TRIVIAL
-Print one confirmation line (`simplify: TRIVIAL — N LOC, 1 file — stamped`) and exit. **Do not** walk the three-category check; the classifier already concluded the diff is below the review-value threshold. Budget: <5 seconds, no Agent.
-
-### Validation pass
-Run the three category checks against the post-fix diff in one pass. Most are clean — confirm and exit. Budget: ~30 seconds, no Agent.
-
-### SMALL — one agent
-```
-Agent — {
-  subagent_type: "reviewer",
-  model: "<sonnet (or haiku for trivial-formatting tier from router)>",
-  prompt: "FIRST ACTION: Run mcp__moflo__memory_search with query 'code review patterns' and namespace 'patterns' to satisfy the memory-first gate. THEN review this diff for reuse, quality, and efficiency. <diff inline>. Flag specific issues as file:line + 1-line description. Max 5 file reads. Under 200 words. Skip cosmetic style. Don't suggest cross-cutting refactors of code outside this diff."
-}
-```
-
-For critical-surface files, prepend a 1-line risk note (e.g., "This is `bin/session-start-launcher.mjs` — runs in every consumer's session-start hot path; cross-platform + blast-radius matter."). One careful agent, not three.
-
-### NORMAL — three parallel agents
-Launch three agents in a single message, each at the routed model (typically sonnet). Each agent gets the SMALL-tier tool-budget cap.
-
-- **Agent 1 (Reuse):** existing helpers/utilities that should be used; duplicated patterns; functions re-implementing something already in the codebase.
-- **Agent 2 (Quality):** redundant state, parameter sprawl, copy-paste with variation, leaky abstractions, stringly-typed code, nested conditionals 3+ levels, unnecessary comments.
-- **Agent 3 (Efficiency):** unnecessary work, missed concurrency, hot-path bloat, recurring no-op updates, TOCTOU existence checks, unbounded structures, over-broad reads.
-
-Each agent prompt must start with `FIRST ACTION: mcp__moflo__memory_search ... namespace: "patterns"` — subagents must satisfy the memory-first gate independently before Glob/Grep/Read.
-
-## Phase 6: Fix or skip
-
-Aggregate findings. Fix each issue directly that's worth fixing. False positives or out-of-scope: note and skip without arguing.
-
-If fixes were made, re-run tests to confirm nothing broke. If tests fail after a fix, revert it.
-
-After fixes: the next `/flo-simplify` invocation is a **validation pass** (Phase 4). Bundle related fixes into one batch so a single validation pass covers them — don't re-fan-out for cosmetic micro-corrections.
-
-## Phase 7: Optional — record routing outcome
-
-If you spawned an agent, feed back the outcome so the router learns:
-
-```
-mcp__moflo__hooks_model-outcome — { task: "...", model: "<chosen>", outcome: "success" | "failure" | "escalated" }
-```
-
-`escalated` only when a real miss happened that a higher tier would have caught — never used to retroactively justify opus.
-
-## Briefly summarize
-
-End with one or two sentences: which tier ran, which model, what was fixed (or "clean — no changes"). No headers, no bullets.

package/.claude/commands/github/README.md

@@ -1,11 +0,0 @@
-# Github Commands
-
-Commands for github operations in Claude Flow.
-
-## Available Commands
-
-- [github-swarm](./github-swarm.md)
-- [repo-analyze](./repo-analyze.md)
-- [pr-enhance](./pr-enhance.md)
-- [issue-triage](./issue-triage.md)
-- [code-review](./code-review.md)