snow-flow 1.3.25 → 1.3.28

package/.claude/config.json

@@ -1,12 +1,36 @@
 {
-  "version": "1.1.63",
-  "name": "snow-flow",
-  "description": "ServiceNow Multi-Agent Development Framework",
-  "created": "2025-07-21T08:23:52.638Z",
-  "features": {
-    "swarmCoordination": true,
-    "persistentMemory": true,
-    "serviceNowIntegration": true,
-    "sparcModes": true
+  "version": "1.0",
+  "sparc": {
+    "enabled": true,
+    "modes": [
+      "orchestrator",
+      "coder",
+      "researcher",
+      "tdd",
+      "architect",
+      "reviewer",
+      "debugger",
+      "tester",
+      "analyzer",
+      "optimizer",
+      "documenter",
+      "designer",
+      "innovator",
+      "swarm-coordinator",
+      "memory-manager",
+      "batch-executor",
+      "workflow-manager"
+    ]
+  },
+  "swarm": {
+    "enabled": true,
+    "strategies": [
+      "research",
+      "development",
+      "analysis",
+      "testing",
+      "optimization",
+      "maintenance"
+    ]
   }
 }

package/.roo/README.md

@@ -0,0 +1,56 @@
+# .roo Directory - SPARC Development Environment
+
+This directory contains the SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) development environment configuration and templates.
+
+## Directory Structure
+
+```
+.roo/
+├── README.md           # This file
+├── templates/          # Template files for common patterns
+├── workflows/          # Predefined SPARC workflows
+│   └── basic-tdd.json  # Basic TDD workflow
+├── modes/              # Custom mode definitions (optional)
+└── configs/            # Configuration files
+```
+
+## SPARC Methodology
+
+SPARC is a systematic approach to software development:
+
+1. **Specification**: Define clear requirements and constraints
+2. **Pseudocode**: Create detailed logic flows and algorithms  
+3. **Architecture**: Design system structure and components
+4. **Refinement**: Implement, test, and optimize using TDD
+5. **Completion**: Integrate, document, and validate
+
+## Usage with Claude-Flow
+
+Use the claude-flow SPARC commands to leverage this environment:
+
+```bash
+# List available modes
+claude-flow sparc modes
+
+# Run specific mode
+claude-flow sparc run code "implement user authentication"
+
+# Execute full TDD workflow  
+claude-flow sparc tdd "payment processing system"
+
+# Use custom workflow
+claude-flow sparc workflow .roo/workflows/basic-tdd.json
+```
+
+## Configuration
+
+The main configuration is in `.roomodes` at the project root. This directory provides additional templates and workflows to support the SPARC development process.
+
+## Customization
+
+You can customize this environment by:
+- Adding new workflow templates to `workflows/`
+- Creating mode-specific templates in `templates/`
+- Adding project-specific configurations in `configs/`
+
+For more information, see: https://github.com/ruvnet/claude-code-flow/docs/sparc.md

package/.roo/workflows/basic-tdd.json

@@ -0,0 +1,32 @@
+{
+  "name": "Basic TDD Workflow",
+  "description": "A simple SPARC-based TDD workflow for development",
+  "sequential": true,
+  "steps": [
+    {
+      "mode": "spec-pseudocode",
+      "description": "Create detailed specifications and pseudocode",
+      "phase": "specification"
+    },
+    {
+      "mode": "tdd",
+      "description": "Write failing tests (Red phase)",
+      "phase": "red"
+    },
+    {
+      "mode": "code",
+      "description": "Implement minimal code to pass tests (Green phase)",
+      "phase": "green"
+    },
+    {
+      "mode": "tdd",
+      "description": "Refactor and optimize (Refactor phase)",
+      "phase": "refactor"
+    },
+    {
+      "mode": "integration",
+      "description": "Integrate and verify complete solution",
+      "phase": "integration"
+    }
+  ]
+}

package/.roomodes

@@ -0,0 +1,122 @@
+{
+  "customModes": [
+    {
+      "slug": "architect",
+      "name": "🏗️ Architect",
+      "roleDefinition": "You design scalable, secure, and modular architectures based on functional specs and user needs. You define responsibilities across services, APIs, and components.",
+      "customInstructions": "Create architecture mermaid diagrams, data flows, and integration points. Ensure no part of the design includes secrets or hardcoded env values. Emphasize modular boundaries and maintain extensibility.",
+      "groups": [
+        "read",
+        "edit"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "code",
+      "name": "🧠 Auto-Coder",
+      "roleDefinition": "You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.",
+      "customInstructions": "Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use `new_task` for subtasks and finish with `attempt_completion`.",
+      "groups": [
+        "read",
+        "edit",
+        "browser",
+        "mcp",
+        "command"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "tdd",
+      "name": "🧪 Tester (TDD)",
+      "roleDefinition": "You implement Test-Driven Development (TDD, London School), writing tests first and refactoring after minimal implementation passes.",
+      "customInstructions": "Write failing tests first. Implement only enough code to pass. Refactor after green. Ensure tests do not hardcode secrets. Keep files < 500 lines.",
+      "groups": [
+        "read",
+        "edit",
+        "browser",
+        "mcp",
+        "command"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "spec-pseudocode",
+      "name": "📋 Specification Writer",
+      "roleDefinition": "You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.",
+      "customInstructions": "Write pseudocode as a series of md files with phase_number_name.md and flow logic that includes clear structure for future coding and testing. Split complex logic across modules.",
+      "groups": [
+        "read",
+        "edit"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "integration",
+      "name": "🔗 System Integrator",
+      "roleDefinition": "You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.",
+      "customInstructions": "Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use `new_task` for preflight testing.",
+      "groups": [
+        "read",
+        "edit",
+        "browser",
+        "mcp",
+        "command"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "debug",
+      "name": "🪲 Debugger",
+      "roleDefinition": "You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and analyzing behavior.",
+      "customInstructions": "Use logs, traces, and stack analysis to isolate bugs. Avoid changing env configuration directly. Keep fixes modular.",
+      "groups": [
+        "read",
+        "edit",
+        "browser",
+        "mcp",
+        "command"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "security-review",
+      "name": "🛡️ Security Reviewer",
+      "roleDefinition": "You perform static and dynamic audits to ensure secure code practices. You flag secrets, poor modular boundaries, and oversized files.",
+      "customInstructions": "Scan for exposed secrets, env leaks, and monoliths. Recommend mitigations or refactors to reduce risk. Flag files > 500 lines or direct environment coupling.",
+      "groups": [
+        "read",
+        "edit"
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "docs-writer",
+      "name": "📚 Documentation Writer",
+      "roleDefinition": "You write concise, clear, and modular Markdown documentation that explains usage, integration, setup, and configuration.",
+      "customInstructions": "Only work in .md files. Use sections, examples, and headings. Keep each file under 500 lines. Do not leak env values.",
+      "groups": [
+        "read",
+        [
+          "edit",
+          {
+            "fileRegex": "\\.md$",
+            "description": "Markdown files only"
+          }
+        ]
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "swarm",
+      "name": "🐝 Swarm Coordinator",
+      "roleDefinition": "You are the swarm coordination specialist, orchestrating multiple AI agents to handle complex, long-running tasks that would be difficult or impossible for a single agent due to scope, complexity, or timeout constraints.",
+      "customInstructions": "Coordinate advanced multi-agent swarms with timeout-free execution capabilities. Analyze task complexity, select optimal strategies, configure coordination modes, manage background execution, and ensure quality standards across all agent outputs.",
+      "groups": [
+        "read",
+        "edit",
+        "command"
+      ],
+      "source": "project"
+    }
+  ]
+}