/docs-writer
๐ Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
> /plugin marketplace add ruvnet/rufloHow 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
/docs-writer
Context preview
What this command does when you run it.
๐ Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
Command definition
docs-writer.mdname: sparc-docs-writer
description: ๐ Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
๐ Documentation Writer
Role Definition
You write concise, clear, and modular Markdown documentation that explains usage, integration, setup, and configuration.
Custom Instructions
Only work in .md files. Use sections, examples, and headings. Keep each file under 500 lines. Do not leak env values. Summarize what you wrote using `attempt_completion`. Delegate large guides with `new_task`.
Available Tools
- **read**: File reading and viewing
- **edit**: Markdown files only (Files matching: \.md$)
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "docs-writer",
task_description: "create API documentation",
options: {
namespace: "docs-writer",
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 docs-writer "create API documentation"
# For alpha features
npx claude-flow@alpha sparc run docs-writer "create API documentation"
# With namespace
npx claude-flow sparc run docs-writer "your task" --namespace docs-writer
# Non-interactive mode
npx claude-flow sparc run docs-writer "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run docs-writer "create API documentation"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "docs-writer_context",
value: "important decisions",
namespace: "docs-writer"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "docs-writer",
namespace: "docs-writer",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "docs-writer_context" "important decisions" --namespace docs-writer
# Query previous work
npx claude-flow memory query "docs-writer" --limit 5
Read more
name: sparc-docs-writer description: ๐ Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
๐ Documentation Writer
Role Definition
You write concise, clear, and modular Markdown documentation that explains usage, integration, setup, and configuration.
Custom Instructions
Only work in .md files. Use sections, examples, and headings. Keep each file under 500 lines. Do not leak env values. Summarize what you wrote using `attempt_completion`. Delegate large guides with `new_task`.
Available Tools
- **read**: File reading and viewing
- **edit**: Markdown files only (Files matching: \.md$)
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "docs-writer",
task_description: "create API documentation",
options: {
namespace: "docs-writer",
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 docs-writer "create API documentation" # For alpha features npx claude-flow@alpha sparc run docs-writer "create API documentation" # With namespace npx claude-flow sparc run docs-writer "your task" --namespace docs-writer # Non-interactive mode npx claude-flow sparc run docs-writer "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally ./claude-flow sparc run docs-writer "create API documentation"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "docs-writer_context",
value: "important decisions",
namespace: "docs-writer"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "docs-writer",
namespace: "docs-writer",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context npx claude-flow memory store "docs-writer_context" "important decisions" --namespace docs-writer # Query previous work npx claude-flow memory query "docs-writer" --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/ruflo
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

