- Create unified workflow-architecture.md combining: - data-model.md (JSON-only architecture, task schemas) - file-structure-standards.md (progressive structures, templates) - session-management-principles.md (marker files, session ops) - complexity-rules.md (classification thresholds, behaviors) - Update 11 files with references to new consolidated document - Remove redundant documentation while preserving all functionality - Streamline maintenance with single source of truth 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
3.8 KiB
Workflow Plan Command (/workflow:plan)
Overview
Creates actionable implementation plans with intelligent input source detection. Supports text, files, issues, and templates through automatic recognition.
Core Principles
File Structure: @~/.claude/workflows/workflow-architecture.md
Usage
/workflow/plan <input>
Input Detection Logic
The command automatically detects input type:
File Input (Auto-detected)
/workflow:plan requirements.md
/workflow:plan PROJECT_SPEC.txt
/workflow:plan config.json
/workflow:plan spec.yaml
Triggers: Extensions: .md, .txt, .json, .yaml, .yml Processing: Reads file contents and extracts requirements
Issue Input (Auto-detected)
/workflow:plan ISS-001
/workflow:plan ISSUE-123
/workflow:plan feature-request-45
Triggers: Patterns: ISS-, ISSUE-, -request- Processing: Loads issue data and acceptance criteria
Template Input (Auto-detected)
/workflow:plan web-api
/workflow:plan mobile-app
/workflow:plan database-migration
/workflow:plan security-feature
Triggers: Known template names Processing: Loads template and prompts for customization
Text Input (Default)
/workflow:plan "Build user authentication with JWT and OAuth2"
/workflow:plan "Fix performance issues in dashboard"
Triggers: Everything else Processing: Parse natural language requirements
Automatic Behaviors
Session Management
- Creates new session if none exists
- Uses active session if available
- Generates session ID: WFS-[topic-slug]
Complexity Detection
- Simple: <5 tasks → Direct IMPL_PLAN.md
- Medium: 5-15 tasks → IMPL_PLAN.md + TODO_LIST.md
- Complex: >15 tasks → Full decomposition
Task Generation
- Automatically creates .task/ files when complexity warrants
- Generates hierarchical task structure (max 3 levels)
- Updates session state with task references
Session Check Process
⚠️ CRITICAL: Check for existing active session before planning
- Check Active Session: Check for
.workflow/.active-*marker file - Session Selection: Use existing active session or create new
- Context Integration: Load session state and existing context
Output Documents
IMPL_PLAN.md (Always Created)
# Implementation Plan - [Project Name]
*Generated from: [input_source]*
## Requirements
[Extracted requirements from input source]
## Task Breakdown
- **IMPL-001**: [Task description]
- **IMPL-002**: [Task description]
## Success Criteria
[Measurable completion conditions]
Optional TODO_LIST.md (Auto-triggered)
Created when complexity > simple or task count > 5
Task JSON Files (Auto-created)
Generated in .task/ directory when decomposition enabled
Error Handling
Input Processing Errors
- File not found: Clear error message with suggestions
- Invalid issue: Verify issue ID exists
- Unknown template: List available templates
- Empty input: Prompt for valid input
Integration Points
Related Commands
/workflow:session:start- Create new session first/context- View generated plan/task/execute- Execute decomposed tasks/workflow:execute- Run implementation phase
Template System
Available templates:
web-api: REST API developmentmobile-app: Mobile applicationdatabase-migration: Database changessecurity-feature: Security implementation
System ensures: Unified planning interface with intelligent input detection and automatic complexity handling