Skip to main content
command CX Codex

workflow · superclaude-org — Claude Code command: what it does, how to install

workflow parses PRDs and feature requirements to generate structured implementation plans with dependency mapping. It plans the execution without touching your code.

MIT ★ 23,950 updated 2026-09-27

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/workflow.md
Open on GitHub

What workflow does

The /sc:workflow command processes project briefs or feature descriptions to map implementation phases. It activates specialized viewpoints like system architecture and security. The resulting plan is saved directly into claudedocs/workflow_*.md with explicit checkpoints.

Workflows adapt using the --strategy flag (systematic, agile, enterprise) alongside --depth controls. The command coordinates with MCP servers like SequentialThinking or Serena if present. When optional MCP servers are missing, it falls back to native reasoning.

A strict operational boundary applies. This tool never writes or modifies application code. It only outputs the workflow document without running builds or edits. Step-by-step execution starts only when you run /sc:implement.

What it helps with

  • generate structured implementation roadmaps from PRD documents
  • map component dependencies prior to starting implementation
  • break down feature specifications across architecture and security domains
  • define execution checkpoints and validation gates for complex tasks

Example prompts for the agent

  • /sc:workflow Claudedocs/PRD/feature-spec.md --strategy systematic --depth deep
  • /sc:workflow "user authentication system" --strategy agile --parallel
  • /sc:workflow project-brief.md --depth normal

How to install workflow

Manually: put the files in place

.claude/commands/workflow.md

Call it with /workflow. For all projects use ~/.claude/commands/

Questions about workflow

How to install workflow in Claude Code?

Add the command file to .claude/commands/workflow.md inside your project directory.

What does the workflow command do?

It parses requirement documents and outputs an execution roadmap. The generated file outlines implementation phases, task ordering, and verification checkpoints.

Does the workflow command modify code?

No, it stops immediately after generating the plan document. To begin implementing the scheduled steps, execute /sc:implement.

Source text

workflow.md · MIT
---
name: workflow
description: "Generate structured implementation workflows from PRDs and feature requirements"
category: orchestration
complexity: advanced
mcp-servers: [sequential, context7, magic, playwright, morphllm, serena]
personas: [architect, analyzer, frontend, backend, security, devops, project-manager]
---

# /sc:workflow - Implementation Workflow Generator

## Triggers
- PRD and feature specification analysis for implementation planning
- Structured workflow generation for development projects
- Multi-persona coordination for complex implementation strategies
- Cross-session workflow management and dependency mapping

## Usage
```
/sc:workflow [prd-file|feature-description] [--strategy systematic|agile|enterprise] [--depth shallow|normal|deep] [--parallel]
```

## Behavioral Flow
1. **Analyze**: Parse PRD and feature specifications to understand implementation requirements
2. **Plan**: Generate comprehensive workflow structure with dependency mapping and task orchestration
3. **Coordinate**: Activate multiple personas for domain expertise and implementation strategy
4. **Execute**: Create structured step-by-step workflows with automated task coordination
5. **Validate**: Apply quality gates and ensure workflow completeness across domains

Key behaviors:
- Multi-persona orchestration across architecture, frontend, backend, security, and devops domains
- Advanced MCP coordination with intelligent routing for specialized workflow analysis
- Systematic execution with progressive workflow enhancement and parallel processing
- Cross-session workflow management with comprehensive dependency tracking

## MCP Integration
- **Sequential MCP**: Complex multi-step workflow analysis and systematic implementation planning
- **Context7 MCP**: Framework-specific workflow patterns and implementation best practices
- **Magic MCP**: UI/UX workflow generation and design system integration strategies
- **Playwright MCP**: Testing workflow integration and quality assurance automation
- **Morphllm MCP**: Large-scale workflow transformation and pattern-based optimization
- **Serena MCP**: Cross-session workflow persistence, memory management, and project context
- **Availability fallback**: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers.

## Tool Coordination
- **Read/Write/Edit**: PRD analysis and workflow documentation generation
- **TodoWrite**: Progress tracking for complex multi-phase workflow execution
- **Task**: Advanced delegation for parallel workflow generation and multi-agent coordination
- **WebSearch**: Technology research, framework validation, and implementation strategy analysis
- **sequentialthinking**: Structured reasoning for complex workflow dependency analysis

## Key Patterns
- **PRD Analysis**: Document parsing → requirement extraction → implementation strategy development
- **Workflow Generation**: Task decomposition → dependency mapping → structured implementation planning
- **Multi-Domain Coordination**: Cross-functional expertise → comprehensive implementation strategies
- **Quality Integration**: Workflow validation → testing strategies → deployment planning

## Examples

### Systematic PRD Workflow
```
/sc:workflow Claudedocs/PRD/feature-spec.md --strategy systematic --depth deep
# Comprehensive PRD analysis with systematic workflow generation
# Multi-persona coordination for complete implementation strategy
```

### Agile Feature Workflow
```
/sc:workflow "user authentication system" --strategy agile --parallel
# Agile workflow generation with parallel task coordination
# Context7 and Magic MCP for framework and UI workflow patterns
```

### Enterprise Implementation Planning
```
/sc:workflow enterprise-prd.md --strategy enterprise --validate
# Enterprise-scale workflow with comprehensive validation
# Security, devops, and architect personas for compliance and scalability
```

### Cross-Session Workflow Management
```
/sc:workflow project-brief.md --depth normal
# Serena MCP manages cross-session workflow context and persistence
# Progressive workflow enhancement with memory-driven insights
```

## Boundaries

**Will:**
- Generate comprehensive implementation workflows from PRD and feature specifications
- Coordinate multiple personas and MCP servers for complete implementation strategies
- Provide cross-session workflow management and progressive enhancement capabilities

**Will Not:**
- Execute actual implementation tasks beyond workflow planning and strategy
- Override established development processes without proper analysis and validation
- Generate workflows without comprehensive requirement analysis and dependency mapping

## CRITICAL BOUNDARIES

**STOP AFTER PLAN CREATION**

This command produces an IMPLEMENTATION PLAN ONLY - no code execution.

**Explicitly Will NOT**:
- Execute any implementation tasks
- Write or modify code
- Create files (except the workflow plan document)
- Make architectural changes
- Run builds or tests

**Output**: Workflow plan document (`claudedocs/workflow_*.md`) containing:
- Implementation phases
- Task dependencies
- Execution order
- Checkpoints and validation steps

**Next Step**: After workflow completes, use `/sc:implement` to execute the plan step by step.

© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

workflow by other authors comes first.

workflow Son Nguyen workflow pulls one session's stats, complexity score and most frequent tool sequences from the local Agent Monitor dashboard and prints a short summary. CX Codex +1 ★ 1,198repo stars requirement-convergence shinpr requirement-convergence — a Claude Code skill that isolates a project outcome from proposed requirements and records user-stated exclusions. Runs at requirement intake before any system design begins. CX Codex +1 ★ 720repo stars task-decomposer curiositech task-decomposer decomposes plain-text problem statements into structured sub-tasks for DAG nodes, spotting dependencies and parallel execution paths. CX Codex +1 155installs plan-execution gojko The plan-execution command for Claude Code drafts an implementation plan and a .plan.json sidecar so that /execute can run the workflow. CX Codex +1 ★ 112repo stars goal-plan ruvnet goal-plan — a skill that builds step-by-step plans for complex tasks, tracks what conditions must be met before each step, estimates costs, and switches to an alternative path if something fails. CX Codex +1 771installs clarifying-assumptions b-mendoza clarifying-assumptions — a skill that runs the conversational layer for plan verification. Asks critical questions upfront or before individual tasks, delegates artifact analysis to subagents. CX Codex +1 129installs orchestrator Rohit Ghumare orchestrator — a subagent for Claude Code that splits complex builds into three phases: research, plan, implement. Each phase requires approval before the next — use it for features touching 5+ files or needing architecture decisions. CX Codex ★ 2,966repo stars

From the same set56

The whole set →
improve improve removes technical debt, tunes execution speed, and patches vulnerabilities in your project. Useful for component refactoring and enforcing code standards. CX Codex +1 ★ 23,950repo stars estimate This command estimates development time, effort, or complexity and returns a breakdown with risks. Use it to scope work before implementation begins. CX Codex +1 ★ 23,950repo stars implement The /sc:implement command coordinates feature development in Claude Code using specialist personas and MCP tools. It handles planning, code generation, and test prep. CX Codex +1 ★ 23,950repo stars task task — a slash command for multi-stage project execution with seven expert personas, intelligent MCP server routing, and cross-session context preservation. User-invoked, runs to completion, then stops. CX Codex +1 ★ 23,950repo stars brainstorm brainstorm is a command for Claude Code, Codex, GitHub Copilot, and Gemini CLI that clarifies vague project ideas and turns them into requirements before planning. CX Codex +1 ★ 23,950repo stars help help is a Claude Code command that lists SuperClaude Framework /sc commands with descriptions. It helps explore the framework’s capabilities. CX Codex +1 ★ 23,950repo stars business-panel-experts business-panel-experts simulates an advisory panel combining Christensen, Porter, Drucker, Taleb, and Collins. Useful for evaluating business models, competitive forces, and structural risks. CX Codex ★ 23,950repo stars socratic-mentor The socratic-mentor subagent teaches programming concepts through guided questions. Use it to examine code, work through Clean Code principles, or identify GoF patterns. CX Codex ★ 23,950repo stars

Project sponsors

Companies that keep this analytics open