claude-code-templates 1.21.4 → 1.21.6

package/components/commands/orchestration/resume.md

@@ -0,0 +1,256 @@
+# Orchestration Resume Command
+
+Resume work on existing task orchestrations after session loss or context switch.
+
+## Usage
+
+```
+/orchestration/resume [options]
+```
+
+## Description
+
+Restores full context for active orchestrations, showing current progress, identifying next actions, and providing all necessary information to continue work seamlessly.
+
+## Basic Commands
+
+### List Active Orchestrations
+```
+/orchestration/resume
+```
+Shows all orchestrations with active (non-completed) tasks.
+
+### Resume Specific Orchestration
+```
+/orchestration/resume --date 03_15_2024 --project auth_system
+```
+Loads complete context for a specific orchestration.
+
+### Resume Most Recent
+```
+/orchestration/resume --latest
+```
+Automatically resumes the most recently active orchestration.
+
+## Output Format
+
+### Orchestration List View
+```
+Active Task Orchestrations
+==========================
+
+1. 03_15_2024/authentication_system
+   Started: 3 days ago | Progress: 65% | Active Tasks: 3
+   └─ Focus: JWT implementation, OAuth integration
+
+2. 03_14_2024/payment_processing  
+   Started: 4 days ago | Progress: 40% | Active Tasks: 2
+   └─ Focus: Stripe webhooks, refund handling
+
+3. 03_12_2024/admin_dashboard
+   Started: 1 week ago | Progress: 85% | Active Tasks: 1
+   └─ Focus: Final testing and deployment
+
+Select orchestration to resume: [1-3] or use --date and --project
+```
+
+### Detailed Resume View
+```
+Resuming: authentication_system (03_15_2024)
+============================================
+
+## Current Status Summary
+- Total Tasks: 24 (12 completed, 3 in progress, 2 on hold, 7 todos)
+- Time Elapsed: 3 days
+- Estimated Remaining: 2 days
+
+## Tasks In Progress
+┌──────────┬────────────────────────────┬───────────────┬──────────────┐
+│ Task ID  │ Title                      │ Agent         │ Duration     │
+├──────────┼────────────────────────────┼───────────────┼──────────────┤
+│ TASK-003 │ JWT token validation       │ dev-backend   │ 2.5h         │
+│ TASK-007 │ OAuth provider setup       │ dev-frontend  │ 1h           │
+│ TASK-011 │ Integration tests          │ test-dev      │ 30m          │
+└──────────┴────────────────────────────┴───────────────┴──────────────┘
+
+## Blocked Tasks (Require Attention)
+- TASK-005: User profile API - Blocked by TASK-003 (JWT validation)
+- TASK-009: OAuth callback handling - Waiting for provider credentials
+
+## Next Available Tasks (Ready to Start)
+1. TASK-013: Password reset flow (4h, frontend)
+   Files: src/auth/reset.tsx, src/api/auth.ts
+   
+2. TASK-014: Session management (3h, backend)
+   Files: src/services/session.ts, src/middleware/auth.ts
+
+## Recent Git Activity
+- feature/jwt-auth: 2 commits behind, last commit 2h ago
+- feature/oauth-setup: clean, last commit 1h ago
+
+## Quick Actions
+[1] Show TASK-003 details (current focus)
+[2] Pick up TASK-013 (password reset)
+[3] View dependency graph
+[4] Show recent commits
+[5] Generate status report
+```
+
+## Context Recovery Features
+
+### Task Context
+```
+/orchestration/resume --task TASK-003
+```
+Shows:
+- Full task description and requirements
+- Implementation progress and notes
+- Related files with recent changes
+- Test requirements and status
+- Dependencies and blockers
+
+### File Context
+```
+/orchestration/resume --show-files
+```
+Lists all files mentioned in active tasks with:
+- Last modified time
+- Current git status
+- Which tasks reference them
+
+### Dependency Context
+```
+/orchestration/resume --deps
+```
+Shows dependency graph focused on active tasks.
+
+## Working State Recovery
+
+### Git State Summary
+```
+## Git Working State
+Current Branch: feature/jwt-auth
+Status: 2 files modified, 1 untracked
+
+Modified Files:
+- src/auth/jwt.ts (related to TASK-003)
+- tests/auth.test.ts (related to TASK-003)
+
+Untracked:
+- src/auth/jwt.config.ts (new file for TASK-003)
+
+Recommendation: Commit current changes before switching tasks
+```
+
+### Last Session Summary
+```
+## Last Session (2 hours ago)
+- Completed: TASK-002 (Database schema)
+- Started: TASK-003 (JWT validation)
+- Commits: 2 (feat: add user auth schema, test: auth unit tests)
+- Next planned: Continue TASK-003, then TASK-005
+```
+
+## Filtering Options
+
+### By Status
+```
+/orchestration/resume --show in_progress,on_hold
+```
+
+### By Date Range
+```
+/orchestration/resume --since "last week"
+```
+
+### By Completion
+```
+/orchestration/resume --incomplete  # < 50% done
+/orchestration/resume --nearly-done  # > 80% done
+```
+
+## Integration Features
+
+### Direct Task Pickup
+```
+/orchestration/resume --pickup TASK-013
+```
+Automatically:
+1. Shows task details
+2. Moves to in_progress
+3. Shows relevant files
+4. Creates feature branch if needed
+
+### Status Check Integration
+```
+/orchestration/resume --with-status
+```
+Includes full status report with resume context.
+
+### Commit History
+```
+/orchestration/resume --commits 5
+```
+Shows last 5 commits related to the orchestration.
+
+## Quick Resume Patterns
+
+### Morning Standup
+```
+/orchestration/resume --latest --with-status
+```
+Perfect for daily standups - shows what you were working on and current state.
+
+### Context Switch
+```
+/orchestration/resume --save-state
+```
+Saves current working state before switching to another orchestration.
+
+### Team Handoff
+```
+/orchestration/resume --handoff
+```
+Generates detailed handoff notes for another developer.
+
+## Examples
+
+### Example 1: Quick Continue
+```
+/orchestration/resume --latest --pickup-where-left-off
+```
+Resumes exactly where you stopped, showing the in-progress task.
+
+### Example 2: Monday Morning
+```
+/orchestration/resume --since friday --show-completed
+```
+Shows what was done Friday and what's next for Monday.
+
+### Example 3: Multiple Projects
+```
+/orchestration/resume --all --summary
+```
+Quick overview of all active orchestrations.
+
+## State Persistence
+
+The command reads from:
+- EXECUTION-TRACKER.md for progress metrics
+- TASK-STATUS-TRACKER.yaml for current state
+- Task files for detailed context
+- Git for working directory state
+
+## Best Practices
+
+1. **Use at Session Start**: Run `/orchestration/resume` when starting work
+2. **Save State**: Use `--save-state` before extended breaks
+3. **Check Dependencies**: Review blocked tasks that may now be unblocked
+4. **Commit Regularly**: Keep git state aligned with task progress
+
+## Notes
+
+- Automatically detects uncommitted changes related to tasks
+- Suggests next actions based on dependencies and priorities
+- Integrates with git worktrees if in use
+- Preserves task history for full context

package/components/commands/orchestration/start.md

@@ -0,0 +1,169 @@
+# Orchestrate Tasks Command
+
+Initiates the task orchestration workflow using the three-agent system (task-orchestrator, task-decomposer, and dependency-analyzer) to create a comprehensive execution plan.
+
+## Usage
+
+```
+/orchestrate [task list or file path]
+```
+
+## Description
+
+This command activates the task-orchestrator agent to process requirements and create a hyper-efficient execution plan. The orchestrator will:
+
+1. **Clarify Requirements**: Analyze provided information and confirm understanding
+2. **Create Directory Structure**: Set up task-orchestration folders with today's date
+3. **Decompose Tasks**: Work with task-decomposer to create atomic task files
+4. **Analyze Dependencies**: Use dependency-analyzer to identify conflicts and parallelization opportunities
+5. **Generate Master Plan**: Create comprehensive coordination documents
+
+## Input Formats
+
+### Direct Task List
+```
+/orchestrate
+- Implement user authentication with JWT
+- Add payment processing with Stripe
+- Create admin dashboard
+- Set up email notifications
+```
+
+### File Reference
+```
+/orchestrate features.md
+```
+
+### Mixed Context
+```
+/orchestrate
+Based on our meeting notes (lots of discussion about UI colors), we need to:
+1. Fix the security vulnerability in file uploads
+2. Add rate limiting to APIs
+3. Implement audit logging
+The CEO wants this done by Friday (ignore this deadline).
+```
+
+## Workflow
+
+1. **Requirement Clarification**
+   - The orchestrator will extract actionable tasks from provided context
+   - Confirm understanding before proceeding
+   - Ask clarifying questions if needed
+
+2. **Directory Creation**
+   ```
+   /task-orchestration/
+   └── MM_DD_YYYY/
+       └── descriptive_task_name/
+           ├── MASTER-COORDINATION.md
+           ├── EXECUTION-TRACKER.md
+           ├── TASK-STATUS-TRACKER.yaml
+           └── tasks/
+               ├── todos/
+               ├── in_progress/
+               ├── on_hold/
+               ├── qa/
+               └── completed/
+   ```
+
+3. **Task Processing**
+   - Creates individual task files in todos/
+   - Analyzes dependencies and conflicts
+   - Generates execution strategy
+
+4. **Deliverables**
+   - Master coordination plan
+   - Task dependency graph
+   - Resource allocation matrix
+   - Execution timeline
+
+## Options
+
+### Focused Mode
+```
+/orchestrate --focus security
+[task list]
+```
+Prioritizes tasks related to the specified focus area.
+
+### Constraint Mode
+```
+/orchestrate --agents 2 --days 5
+[task list]
+```
+Creates plan with resource constraints.
+
+### Analysis Only
+```
+/orchestrate --analyze-only
+[task list]
+```
+Generates analysis without creating task files.
+
+## Examples
+
+### Example 1: Clear Task List
+```
+/orchestrate
+1. Implement OAuth2 authentication
+2. Add user profile management
+3. Create password reset flow
+4. Set up 2FA
+```
+
+### Example 2: From Requirements Doc
+```
+/orchestrate requirements/sprint-24.md
+```
+
+### Example 3: Mixed Context Extraction
+```
+/orchestrate
+From the customer feedback:
+"The app is too slow" - Need performance optimization
+"Can't find the export button" - UI improvement needed
+"Want dark mode" - New feature request
+
+Technical debt from last sprint:
+- Refactor authentication service
+- Update deprecated dependencies
+```
+
+## Interactive Mode
+
+The orchestrator will:
+1. Present extracted tasks for confirmation
+2. Ask about priorities and constraints
+3. Suggest optimal approach
+4. Request approval before creating files
+
+## Error Handling
+
+- If tasks are unclear: Asks for clarification
+- If file not found: Prompts for correct path
+- If conflicts detected: Presents options
+- If dependencies circular: Suggests resolution
+
+## Integration
+
+Works seamlessly with:
+- `/task-status` - Check progress
+- `/task-move` - Update task status
+- `/task-report` - Generate reports
+- `/task-assign` - Allocate to agents
+
+## Best Practices
+
+1. **Provide Context**: Include relevant background information
+2. **Be Specific**: Clear task descriptions enable better planning
+3. **Mention Constraints**: Include deadlines, resources, or blockers
+4. **Review Output**: Confirm the extracted tasks match your intent
+
+## Notes
+
+- The orchestrator filters out irrelevant context automatically
+- Tasks are created in todos/ status by default
+- All tasks get unique IDs (TASK-XXX format)
+- Status tracking begins immediately
+- Supports incremental additions to existing orchestrations

package/components/commands/orchestration/status.md

@@ -0,0 +1,219 @@
+# Task Status Command
+
+Check the current status of tasks in the orchestration system with various filtering and reporting options.
+
+## Usage
+
+```
+/task-status [options]
+```
+
+## Description
+
+Provides comprehensive visibility into task progress, status distribution, and execution metrics across all active orchestrations.
+
+## Command Variants
+
+### Basic Status Overview
+```
+/task-status
+```
+Shows summary of all tasks across all active orchestrations.
+
+### Today's Tasks
+```
+/task-status --today
+```
+Shows only tasks from today's orchestrations.
+
+### Specific Orchestration
+```
+/task-status --date 03_15_2024 --project payment_integration
+```
+Shows tasks from a specific orchestration.
+
+### Status Filter
+```
+/task-status --status in_progress
+/task-status --status qa
+/task-status --status on_hold
+```
+Shows only tasks with specified status.
+
+### Detailed View
+```
+/task-status --detailed
+```
+Shows comprehensive information for each task.
+
+## Output Formats
+
+### Summary View (Default)
+```
+Task Orchestration Status Summary
+=================================
+
+Active Orchestrations: 3
+Total Tasks: 47
+
+Status Distribution:
+┌─────────────┬───────┬────────────┐
+│ Status      │ Count │ Percentage │
+├─────────────┼───────┼────────────┤
+│ completed   │  12   │    26%     │
+│ qa          │   5   │    11%     │
+│ in_progress │   3   │     6%     │
+│ on_hold     │   2   │     4%     │
+│ todos       │  25   │    53%     │
+└─────────────┴───────┴────────────┘
+
+Active Tasks (in_progress):
+- TASK-001: Implement JWT authentication (Agent: dev-frontend)
+- TASK-007: Create payment webhook handler (Agent: dev-backend)
+- TASK-012: Write integration tests (Agent: test-developer)
+
+Blocked Tasks (on_hold):
+- TASK-004: User profile API (Blocked by: TASK-001)
+- TASK-009: Payment confirmation UI (Blocked by: TASK-007)
+```
+
+### Detailed View
+```
+Task Details for: 03_15_2024/authentication_system
+==================================================
+
+TASK-001: Implement JWT authentication
+Status: in_progress
+Agent: dev-frontend
+Started: 2024-03-15T14:30:00Z
+Duration: 3.5 hours
+Progress: 75% (est. 1 hour remaining)
+Dependencies: None
+Blocks: TASK-004, TASK-005
+Location: /task-orchestration/03_15_2024/authentication_system/tasks/in_progress/
+
+Status History:
+- todos → in_progress (2024-03-15T14:30:00Z) by dev-frontend
+```
+
+### Timeline View
+```
+/task-status --timeline
+```
+Shows Gantt-style timeline of task execution.
+
+### Velocity Report
+```
+/task-status --velocity
+```
+Shows completion rates and performance metrics.
+
+## Filtering Options
+
+### By Agent
+```
+/task-status --agent dev-frontend
+```
+
+### By Priority
+```
+/task-status --priority high
+```
+
+### By Type
+```
+/task-status --type feature
+/task-status --type bugfix
+```
+
+### Multiple Filters
+```
+/task-status --status todos --priority high --type security
+```
+
+## Quick Actions
+
+### Show Critical Path
+```
+/task-status --critical-path
+```
+Highlights tasks that are blocking others.
+
+### Show Overdue
+```
+/task-status --overdue
+```
+Shows tasks exceeding estimated time.
+
+### Show Available
+```
+/task-status --available
+```
+Shows todos tasks ready to be picked up.
+
+## Integration Commands
+
+### Export Status
+```
+/task-status --export markdown
+/task-status --export csv
+```
+
+### Watch Mode
+```
+/task-status --watch
+```
+Updates status in real-time (refreshes every 30 seconds).
+
+## Examples
+
+### Example 1: Morning Standup View
+```
+/task-status --today --detailed
+```
+
+### Example 2: Find Blocked Work
+```
+/task-status --status on_hold --show-blockers
+```
+
+### Example 3: Agent Workload
+```
+/task-status --by-agent --status in_progress
+```
+
+### Example 4: Sprint Progress
+```
+/task-status --date 03_15_2024 --metrics
+```
+
+## Metrics and Analytics
+
+### Completion Metrics
+- Average time per task
+- Tasks completed per day
+- Status transition times
+
+### Bottleneck Analysis
+- Most blocking tasks
+- Longest on_hold duration
+- Critical path duration
+
+### Agent Performance
+- Tasks per agent
+- Average completion time
+- Current workload
+
+## Best Practices
+
+1. **Daily Check**: Run `/task-status --today` each morning
+2. **Blocker Review**: Check `/task-status --status on_hold` regularly
+3. **Progress Tracking**: Use `/task-status --velocity` for trends
+4. **Resource Planning**: Monitor `/task-status --by-agent`
+
+## Notes
+
+- Status data is read from TASK-STATUS-TRACKER.yaml files
+- All times are shown in local timezone
+- Completed tasks are included in metrics but not in active lists
+- Use `--all` flag to include historical orchestrations