- Updated the `/workflow:plan` command description to clarify its orchestration of a 4-phase planning workflow. - Revised the execution flow and core planning principles for improved clarity and structure. - Removed the `ANALYSIS_RESULTS.md` file as it is no longer needed in the workflow. - Enhanced the `concept-enhanced` tool documentation to specify mandatory first steps and output requirements. - Expanded the `ui-designer` role template to include detailed design workflows, output requirements, and collaboration strategies. - Introduced new design phases with clear outputs and user approval checkpoints in the UI designer template.
6.4 KiB
name, description, usage, argument-hint, examples, allowed-tools
| name | description | usage | argument-hint | examples | allowed-tools | ||||
|---|---|---|---|---|---|---|---|---|---|
| plan | Orchestrate 4-phase planning workflow by executing commands and passing context between phases | /workflow:plan [--agent] <input> | [--agent] "text description"|file.md|ISS-001 |
|
SlashCommand(*), TodoWrite(*), Read(*), Bash(*) |
Workflow Plan Command (/workflow:plan)
Coordinator Role
This command is a pure orchestrator: Execute 4 slash commands in sequence, parse their outputs, pass context between them, and ensure complete execution.
Execution Flow:
- Initialize TodoWrite → Execute Phase 1 → Parse output → Update TodoWrite
- Execute Phase 2 with Phase 1 data → Parse output → Update TodoWrite
- Execute Phase 3 with Phase 2 data → Parse output → Update TodoWrite
- Execute Phase 4 with Phase 3 validation → Update TodoWrite → Return summary
Execution Modes:
- Manual Mode (default): Use
/workflow:tools:task-generate - Agent Mode (
--agent): Use/workflow:tools:task-generate-agent
Core Rules
- Start Immediately: First action is TodoWrite initialization, second action is Phase 1 command execution
- No Preliminary Analysis: Do not read files, analyze structure, or gather context before Phase 1
- Parse Every Output: Extract required data from each command's output for next phase
- Sequential Execution: Each phase depends on previous phase's output
- Complete All Phases: Do not return to user until Phase 4 completes
- Track Progress: Update TodoWrite after every phase completion
4-Phase Execution
Phase 1: Session Discovery
Command: SlashCommand(command="/workflow:session:start --auto \"[task-description]\"")
Parse Output:
- Extract:
SESSION_ID: WFS-[id](store assessionId)
Validation:
- Session ID successfully extracted
- Session directory
.workflow/[sessionId]/exists
TodoWrite: Mark phase 1 completed, phase 2 in_progress
Phase 2: Context Gathering
Command: SlashCommand(command="/workflow:tools:context-gather --session [sessionId] \"[task-description]\"")
Input: sessionId from Phase 1
Parse Output:
- Extract: context-package.json path (store as
contextPath) - Typical pattern:
.workflow/[sessionId]/.context/context-package.json
Validation:
- Context package path extracted
- File exists and is valid JSON
TodoWrite: Mark phase 2 completed, phase 3 in_progress
Phase 3: Intelligent Analysis
Command: SlashCommand(command="/workflow:tools:concept-enhanced --session [sessionId] --context [contextPath]")
Input: sessionId from Phase 1, contextPath from Phase 2
Parse Output:
- Verify ANALYSIS_RESULTS.md created
Validation:
- File
.workflow/[sessionId]/ANALYSIS_RESULTS.mdexists - Contains task recommendations section
TodoWrite: Mark phase 3 completed, phase 4 in_progress
Phase 4: Task Generation
Command:
- Manual:
SlashCommand(command="/workflow:tools:task-generate --session [sessionId]") - Agent:
SlashCommand(command="/workflow:tools:task-generate-agent --session [sessionId]")
Input: sessionId from Phase 1
Validation:
.workflow/[sessionId]/IMPL_PLAN.mdexists.workflow/[sessionId]/.task/IMPL-*.jsonexists (at least one).workflow/[sessionId]/TODO_LIST.mdexists
TodoWrite: Mark phase 4 completed
Return to User:
Planning complete for session: [sessionId]
Tasks generated: [count]
Plan: .workflow/[sessionId]/IMPL_PLAN.md
Next: /workflow:execute or /workflow:status
TodoWrite Pattern
// Initialize (before Phase 1)
TodoWrite({todos: [
{"content": "Execute session discovery", "status": "in_progress", "activeForm": "Executing session discovery"},
{"content": "Execute context gathering", "status": "pending", "activeForm": "Executing context gathering"},
{"content": "Execute intelligent analysis", "status": "pending", "activeForm": "Executing intelligent analysis"},
{"content": "Execute task generation", "status": "pending", "activeForm": "Executing task generation"}
]})
// After Phase 1
TodoWrite({todos: [
{"content": "Execute session discovery", "status": "completed", "activeForm": "Executing session discovery"},
{"content": "Execute context gathering", "status": "in_progress", "activeForm": "Executing context gathering"},
{"content": "Execute intelligent analysis", "status": "pending", "activeForm": "Executing intelligent analysis"},
{"content": "Execute task generation", "status": "pending", "activeForm": "Executing task generation"}
]})
// Continue pattern for Phase 2, 3, 4...
Data Flow
User Input (task description)
↓
Phase 1: session:start --auto "description"
↓ Output: sessionId
↓ Session Memory: Previous tasks, context, artifacts
↓
Phase 2: context-gather --session sessionId "description"
↓ Input: sessionId + session memory
↓ Output: contextPath (context-package.json)
↓
Phase 3: concept-enhanced --session sessionId --context contextPath
↓ Input: sessionId + contextPath + session memory
↓ Output: ANALYSIS_RESULTS.md
↓
Phase 4: task-generate[--agent] --session sessionId
↓ Input: sessionId + ANALYSIS_RESULTS.md + session memory
↓ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md
↓
Return summary to user
Session Memory Flow: Each phase receives session ID, which provides access to:
- Previous task summaries
- Existing context and analysis
- Brainstorming artifacts
- Session-specific configuration
Error Handling
- Parsing Failure: If output parsing fails, retry command once, then report error
- Validation Failure: If validation fails, report which file/data is missing
- Command Failure: Keep phase
in_progress, report error to user, do not proceed
Coordinator Checklist
✅ Initialize TodoWrite before any command ✅ Execute Phase 1 immediately (no preliminary steps) ✅ Parse session ID from Phase 1 output ✅ Pass session ID to Phase 2 command ✅ Parse context path from Phase 2 output ✅ Pass session ID and context path to Phase 3 command ✅ Verify ANALYSIS_RESULTS.md after Phase 3 ✅ Select correct Phase 4 command based on --agent flag ✅ Pass session ID to Phase 4 command ✅ Verify all Phase 4 outputs ✅ Update TodoWrite after each phase ✅ Return summary only after Phase 4 completes