
sc-workflow
Generate structured implementation workflows from PRDs and feature requirements. Use when planning implementations, decomposing features, or coordinating multi-domain development.
- Installs
- 93
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tony363/superclaude --skill sc-workflow- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sc-workflow automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Implementation Workflow Generator Skill
Transform PRDs and requirements into structured implementation plans.
Quick Start
# PRD-based workflow
/sc:workflow feature-spec.md --strategy systematic --depth deep
# Feature workflow
/sc:workflow "user auth system" --strategy agile --parallel
# Enterprise planning
/sc:workflow enterprise-prd.md --strategy enterprise --validate
Behavioral Flow
- Analyze - Parse PRD and feature specifications
- Plan - Generate workflow structure with dependencies
- Coordinate - Activate personas for domain expertise
- Execute - Create step-by-step workflows
- Validate - Apply quality gates and completeness checks
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--strategy | string | systematic | systematic, agile, enterprise |
--depth | string | normal | shallow, normal, deep |
--parallel | bool | false | Enable parallel task generation |
--validate | bool | false | Include quality gates |
Personas Activated
- architect - System design and technical planning
- analyzer - Requirements analysis
- frontend - UI/UX implementation planning
- backend - API and data layer planning
- security - Security requirements integration
- devops - Infrastructure and deployment planning
- project-manager - Timeline and resource coordination
MCP Integration
PAL MCP (Planning & Validation)
| Tool | When to Use | Purpose |
|---|---|---|
mcp__pal__planner | Complex workflows | Sequential planning with branching |
mcp__pal__consensus | High-risk decisions | Multi-model validation of approach |
mcp__pal__thinkdeep | Architecture planning | Deep analysis of system design |
mcp__pal__chat | Clarification | Get second opinion on workflow structure |
PAL Usage Patterns
# Plan complex workflow
mcp__pal__planner(
step="Planning authentication system implementation workflow",
step_number=1,
total_steps=5,
is_branch_point=True,
branch_id="auth-approach-oauth"
)
# Validate architectural decisions
mcp__pal__consensus(
models=[
{"model": "gpt-5.2", "stance": "for"},
{"model": "gemini-3-pro", "stance": "against"},
{"model": "deepseek", "stance": "neutral"}
],
step="Evaluate: Should auth be microservice or monolith module?"
)
# Deep analysis for enterprise planning
mcp__pal__thinkdeep(
step="Analyzing compliance requirements for enterprise auth",
hypothesis="SOC2 requires audit logging at every auth event",
confidence="medium",
focus_areas=["compliance", "security", "scalability"]
)
Rube MCP (Project Management)
| Tool | When to Use | Purpose |
|---|---|---|
mcp__rube__RUBE_SEARCH_TOOLS | Project tools | Find Jira, Asana, Linear, Notion |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Backlog creation | Create tasks, epics, stories |
mcp__rube__RUBE_CREATE_PLAN | Complex workflows | Generate execution plans |
mcp__rube__RUBE_CREATE_UPDATE_RECIPE | Reusable workflows | Save workflow templates |
Rube Usage Patterns
# Create backlog items from workflow
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "JIRA_CREATE_ISSUE", "arguments": {
"project": "AUTH",
"summary": "Implement OAuth2 provider integration",
"issue_type": "Epic",
"description": "## Scope\n- Google OAuth\n- GitHub OAuth\n- SAML support"
}},
{"tool_slug": "JIRA_CREATE_ISSUE", "arguments": {
"project": "AUTH",
"summary": "Set up JWT token generation",
"issue_type": "Story",
"description": "Implement JWT with refresh tokens"
}},
{"tool_slug": "JIRA_CREATE_ISSUE", "arguments": {
"project": "AUTH",
"summary": "Add rate limiting to auth endpoints",
"issue_type": "Task"
}}
])
# Notify team of new workflow
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "SLACK_SEND_MESSAGE", "arguments": {
"channel": "#project-planning",
"text": "New implementation workflow created: Authentication System\nEpic: AUTH-123\n5 stories, 12 tasks"
}},
{"tool_slug": "NOTION_CREATE_PAGE", "arguments": {
"title": "Auth System Implementation Plan",
"content": "## Phases\n1. OAuth Integration\n2. JWT Implementation\n3. Rate Limiting\n\n## Timeline\nSprint 1-3"
}}
])
# Save workflow as reusable template
mcp__rube__RUBE_CREATE_UPDATE_RECIPE(
name="Auth System Workflow Template",
description="Standard workflow for implementing authentication systems",
workflow_code="..."
)
Flags (Extended)
| Flag | Type | Default | Description |
|---|---|---|---|
--pal-plan | bool | false | Use PAL planner for complex workflows |
--consensus | bool | false | Validate approach with multi-model consensus |
--create-backlog | bool | false | Create backlog items via Rube |
--notify | string | - | Notify via Rube (slack, teams, email) |
--save-template | bool | false | Save as reusable Rube recipe |
Evidence Requirements
This skill does NOT require hard evidence. Deliverables are:
- Structured workflow documentation
- Task dependency maps
- Implementation phases
Workflow Strategies
Systematic (--strategy systematic)
- Comprehensive task decomposition
- Full dependency mapping
- Documentation-heavy approach
Agile (--strategy agile)
- Sprint-oriented planning
- User story focused
- Iterative milestones
Enterprise (--strategy enterprise)
- Compliance integration
- Stakeholder alignment
- Risk assessment included
Workflow Components
Task Decomposition
- Feature breakdown into implementable units
- Clear acceptance criteria
- Effort estimation
Dependency Mapping
- Task prerequisites
- Blocking relationships
- Parallel execution opportunities
Quality Gates
- Testing requirements
- Review checkpoints
- Deployment criteria
Examples
PRD Analysis
/sc:workflow docs/PRD/feature.md --strategy systematic --depth deep
# Full PRD parsing with comprehensive workflow
# Multi-persona coordination for complete plan
Feature Implementation
/sc:workflow "payment integration" --strategy agile --parallel
# Sprint-ready task breakdown
# Parallel frontend/backend tracks
Enterprise Planning
/sc:workflow enterprise-spec.md --strategy enterprise --validate
# Compliance-aware workflow
# Security and devops integration
Quick Planning
/sc:workflow "add search feature" --depth shallow
# Rapid task list generation
# High-level milestone planning
Output Structure
Workflows include:
- Overview - Feature summary and scope
- Phases - Implementation stages
- Tasks - Detailed work items
- Dependencies - Task relationships
- Milestones - Key checkpoints
- Risks - Identified concerns
Tool Coordination
- Read/Write - PRD analysis and documentation
- TodoWrite - Progress tracking
- Task - Parallel workflow generation
- WebSearch - Technology research
FAQ
What does the sc-workflow skill do?
Generate structured implementation workflows from PRDs and feature requirements. Use when planning implementations, decomposing features, or coordinating multi-domain development.
How do I install sc-workflow?
Run npx skills add https://github.com/tony363/superclaude --skill sc-workflow in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sc-workflow/ (personal) or .claude/skills/sc-workflow/ (project).
Which AI agents can use sc-workflow?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sc-workflow safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sc-workflow?
It is published by tony363 in tony363/superclaude. It has 93 recorded installs.
More from tony363/superclaude
agent-performance-engineer
tony363/superclaude
Expert performance engineer specializing in system optimization, bottleneck identification, and scalability engineering. Masters performance testing, profiling, and tuning across applications, databases, and infrastructure with focus on achieving optimal response times and resource efficiency.
agent-security-engineer
tony363/superclaude
Expert infrastructure security engineer specializing in DevSecOps, cloud security, and compliance frameworks. Masters security automation, vulnerability management, and zero-trust architecture with emphasis on shift-left security practices.
sc-estimate
tony363/superclaude
Provide development estimates for tasks, features, or projects with intelligent analysis. Use when planning timelines, assessing complexity, or scoping resources.
agent-fullstack-developer
tony363/superclaude
End-to-end feature owner with expertise across the entire stack. Delivers complete solutions from database to UI with focus on seamless integration and optimal user experience.
sc-design
tony363/superclaude
Design system architecture, APIs, and component interfaces with comprehensive specifications. Use when planning architecture, designing APIs, creating component interfaces, or modeling databases.
agent-technical-writer
tony363/superclaude
Open the skill to read its SKILL.md instructions.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。