/spec-pseudocode
📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...
> /plugin marketplace add ruvnet/claude-flowHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/spec-pseudocode
Context preview
What this command does when you run it.
📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...
Command definition
spec-pseudocode.mdname: 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)
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)
# 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
# If claude-flow is installed locally
./claude-flow sparc run spec-pseudocode "define payment flow requirements"
Memory Integration
Using MCP Tools (Preferred)
// 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)
# 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
Read more
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)
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)
# 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
# If claude-flow is installed locally ./claude-flow sparc run spec-pseudocode "define payment flow requirements"
Memory Integration
Using MCP Tools (Preferred)
// 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)
# 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
An agent meta-harness for Claude Code and Codex. Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work.
Repo: ruvnet/claude-flow
Other commands on claude-flow.
- /agent-capabilities
Matrix of agent capabilities and their specializations.
Open command - /agent-coordination
Coordination patterns for multi-agent collaboration.
Open command - /agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Open command - /agent-types
Complete guide to all 54 available agent types in Claude Flow.
Open command - /COMMAND_COMPLIANCE_REPORT
Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls
Open command - /bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
Open command

