Stats
Actions
Tags
From orchestr8
Creates multi-phase workflow definitions with JIT resource loading, progress tracking, structured phases, and metadata.
How this command is triggered — by the user, by Claude, or both
Slash command
/orchestr8:create-workflowThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Create Workflow: $ARGUMENTS **Request:** $ARGUMENTS ## How to Load MCP Resources **CRITICAL:** All `orchestr8://` URIs in this workflow must be loaded using `ReadMcpResourceTool` with `server: "plugin:orchestr8:orchestr8-resources"` and the `uri` parameter set to the resource URI shown. For detailed instructions and examples, load: `orchestr8://guides/mcp-resource-loading` ## Your Role You are the **Workflow Architect** responsible for designing structured, multi-phase workflows with dynamic resource loading and clear execution strategies. ## Phase 1: Workflow Definition & Analys...
Request: $ARGUMENTS
CRITICAL: All orchestr8:// URIs in this workflow must be loaded using ReadMcpResourceTool with server: "plugin:orchestr8:orchestr8-resources" and the uri parameter set to the resource URI shown.
For detailed instructions and examples, load: orchestr8://guides/mcp-resource-loading
You are the Workflow Architect responsible for designing structured, multi-phase workflows with dynamic resource loading and clear execution strategies.
→ Load: orchestr8://workflows/workflow-create-workflow
Activities:
→ Checkpoint: Workflow scope and phases defined
→ Load: orchestr8://match?query=workflow+phased+delivery+jit+loading&categories=pattern,skill&mode=index&maxResults=5
Activities:
Design Phase Structure:
Plan Token Budgets:
Design Metadata:
→ Checkpoint: Phase structure and resource loading strategy defined
→ Load: orchestr8://match?query=$ARGUMENTS+implementation&categories=pattern,skill,example&mode=index&maxResults=8
Activities:
Write Workflow Fragment:
Metadata Requirements:
---
id: workflow-name
category: pattern
tags: [workflow, domain, keywords]
capabilities:
- What workflow accomplishes 1
- What workflow accomplishes 2
- What workflow accomplishes 3
useWhen:
- Specific scenario 1
- Specific scenario 2
- Specific scenario 3
estimatedTokens: 500-600
---
Workflow Structure:
# Workflow Name
**Phases:** Phase1 (0-X%) → Phase2 (X-Y%) → Phase3 (Y-100%)
## Phase 1: Name (0-X%)
**→ JIT Load:** orchestr8://match?query=...&mode=index&maxResults=5
**Activities:**
- Activity 1
- Activity 2
**Parallel tracks (if applicable):**
- Track A: Independent work
- Track B: Independent work
**→ Checkpoint:** Completion criteria
## Phase 2-N: [Additional phases]
## Parallelism
- **Independent:** What can run in parallel
- **Dependencies:** What must run sequentially
## Success Criteria
✅ Criterion 1
✅ Criterion 2
JIT Loading Patterns:
# Static URI (specific agent/skill)
orchestr8://agents/typescript-core
# Dynamic URI (query matching)
orchestr8://match?query=testing+validation&mode=index&maxResults=5
# Category filtering
orchestr8://match?query=deployment&categories=guide,skill&mode=index&maxResults=3
# With argument substitution (for commands)
orchestr8://match?query=${technology}+${domain}&mode=index&maxResults=8
→ Checkpoint: Workflow content complete with JIT loading
→ Load: orchestr8://match?query=workflow+testing+discovery&categories=skill&mode=index&maxResults=3
Activities:
Validation:
Discovery Testing:
Integration:
resources/workflows/Command Wrapper (optional):
---
description: Brief description
---
# Workflow Name: $ARGUMENTS
**Request:** $ARGUMENTS
## Your Role
Brief role description
## Phase 1: Name (0-X%)
**→ Load:** orchestr8://workflows/workflow-name
[Additional command-specific content]
→ Checkpoint: Workflow tested and integrated
---
id: workflow-add-feature
category: pattern
tags: [workflow, feature-development, implementation, testing, integration]
capabilities:
- Complete feature implementation with design and testing
- Seamless integration into existing codebase
- Concurrent backend/frontend/test development
useWhen:
- Adding features to existing codebase
- Implementing new functionality with tests
- Integrating features with validation
estimatedTokens: 520
---
# Add Feature Pattern
**Phases:** Design (0-20%) → Implementation (20-70%) → Quality (70-90%) → Deploy (90-100%)
## Phase 1: Analysis & Design (0-20%)
**→ Load:** orchestr8://match?query=requirement+analysis+design&mode=index&maxResults=5
**Activities:**
- Parse requirements, define acceptance criteria
- Analyze affected components
- Design API contracts and data models
**→ Checkpoint:** Design approved
## Phase 2: Implementation (20-70%)
**→ Load:** orchestr8://match?query=implementation+testing&mode=index&maxResults=8
**Parallel tracks:**
- **Backend:** Schema, models, API endpoints
- **Frontend:** Components, state, integration
- **Tests:** Unit, integration tests
**→ Checkpoint:** Feature works, tests pass
## Phase 3-4: [Additional phases]
## Parallelism
- **Independent:** Backend + Frontend + Tests (Phase 2)
- **Dependencies:** Frontend needs backend API
✅ Workflow purpose clearly defined ✅ No duplication with existing workflows ✅ 3-6 well-structured phases ✅ Progress ranges assigned ✅ Activities clear and actionable ✅ Checkpoints measurable ✅ JIT loading strategy defined ✅ Token budgets appropriate ✅ Parallelism opportunities identified ✅ Dependencies documented ✅ Complete metadata (tags, capabilities, useWhen) ✅ Token count within guidelines (500-600) ✅ Discoverable via relevant queries ✅ Saved to correct location ✅ Index rebuilt successfully ✅ Loadable via MCP ✅ Command wrapper created if needed ✅ Documentation updated
npx claudepluginhub seth-schultz/orchestr8 --plugin orchestr8/create-workflowScaffolds a custom swarm workflow by generating a mode skill and shortcut command. Prompts for workflow purpose and structure type, then produces the files.
/runParses and executes legacy inline orchestration workflow syntax supporting raw operators, YAML frontmatter templates, and temporary AI agents with model overrides.
/workflowsSaves recent development actions as reusable workflows, lists them in a dashboard, executes selected workflows, and supports optimization.
/sc-workflowGenerates structured implementation workflows from PRDs or feature descriptions using multi-persona coordination. Supports --strategy, --depth, and --parallel options.
/build-workflowScaffolds a new workflow-as-markdown file in workflows/ directory with YAML frontmatter for outputs, agents, and validation. Prompts for purpose, expected outputs, and agents; optionally creates agent stubs.
/ns-workflowRoutes user intents to the appropriate phase-pipeline skill — discuss, spec, plan, execute, verify, add tests, and more. Supports autonomous, fast, and MVP modes.