@claude-flow/cli 3.10.46 → 3.11.0

package/.claude/commands/sparc/spec-pseudocode.md

@@ -1,80 +1,80 @@
----
-name: sparc-spec-pseudocode
-description: 📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...
----
-
-# 📋 Specification Writer
-
-## Role Definition
-You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.
-
-## Custom Instructions
-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. Never include hard-coded secrets or config values. Ensure each spec module remains < 500 lines.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-
-## Usage
-
-### Option 1: Using MCP Tools (Preferred in Claude Code)
-```javascript
-mcp__claude-flow__sparc_mode {
-  mode: "spec-pseudocode",
-  task_description: "define payment flow requirements",
-  options: {
-    namespace: "spec-pseudocode",
-    non_interactive: false
-  }
-}
-```
-
-### Option 2: Using NPX CLI (Fallback when MCP not available)
-```bash
-# Use when running from terminal or MCP tools unavailable
-npx claude-flow sparc run spec-pseudocode "define payment flow requirements"
-
-# For alpha features
-npx claude-flow@alpha sparc run spec-pseudocode "define payment flow requirements"
-
-# With namespace
-npx claude-flow sparc run spec-pseudocode "your task" --namespace spec-pseudocode
-
-# Non-interactive mode
-npx claude-flow sparc run spec-pseudocode "your task" --non-interactive
-```
-
-### Option 3: Local Installation
-```bash
-# If claude-flow is installed locally
-./claude-flow sparc run spec-pseudocode "define payment flow requirements"
-```
-
-## Memory Integration
-
-### Using MCP Tools (Preferred)
-```javascript
-// Store mode-specific context
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "spec-pseudocode_context",
-  value: "important decisions",
-  namespace: "spec-pseudocode"
-}
-
-// Query previous work
-mcp__claude-flow__memory_search {
-  pattern: "spec-pseudocode",
-  namespace: "spec-pseudocode",
-  limit: 5
-}
-```
-
-### Using NPX CLI (Fallback)
-```bash
-# Store mode-specific context
-npx claude-flow memory store "spec-pseudocode_context" "important decisions" --namespace spec-pseudocode
-
-# Query previous work
-npx claude-flow memory query "spec-pseudocode" --limit 5
-```
+---
+name: sparc-spec-pseudocode
+description: 📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...
+---
+
+# 📋 Specification Writer
+
+## Role Definition
+You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.
+
+## Custom Instructions
+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. Never include hard-coded secrets or config values. Ensure each spec module remains < 500 lines.
+
+## Available Tools
+- **read**: File reading and viewing
+- **edit**: File modification and creation
+
+## Usage
+
+### Option 1: Using MCP Tools (Preferred in Claude Code)
+```javascript
+mcp__claude-flow__sparc_mode {
+  mode: "spec-pseudocode",
+  task_description: "define payment flow requirements",
+  options: {
+    namespace: "spec-pseudocode",
+    non_interactive: false
+  }
+}
+```
+
+### Option 2: Using NPX CLI (Fallback when MCP not available)
+```bash
+# Use when running from terminal or MCP tools unavailable
+npx claude-flow sparc run spec-pseudocode "define payment flow requirements"
+
+# For alpha features
+npx claude-flow@alpha sparc run spec-pseudocode "define payment flow requirements"
+
+# With namespace
+npx claude-flow sparc run spec-pseudocode "your task" --namespace spec-pseudocode
+
+# Non-interactive mode
+npx claude-flow sparc run spec-pseudocode "your task" --non-interactive
+```
+
+### Option 3: Local Installation
+```bash
+# If claude-flow is installed locally
+./claude-flow sparc run spec-pseudocode "define payment flow requirements"
+```
+
+## Memory Integration
+
+### Using MCP Tools (Preferred)
+```javascript
+// Store mode-specific context
+mcp__claude-flow__memory_usage {
+  action: "store",
+  key: "spec-pseudocode_context",
+  value: "important decisions",
+  namespace: "spec-pseudocode"
+}
+
+// Query previous work
+mcp__claude-flow__memory_search {
+  pattern: "spec-pseudocode",
+  namespace: "spec-pseudocode",
+  limit: 5
+}
+```
+
+### Using NPX CLI (Fallback)
+```bash
+# Store mode-specific context
+npx claude-flow memory store "spec-pseudocode_context" "important decisions" --namespace spec-pseudocode
+
+# Query previous work
+npx claude-flow memory query "spec-pseudocode" --limit 5
+```