claude-code-templates 1.21.12 → 1.21.13

package/cli-tool/components/commands/orchestration/remove.md

@@ -0,0 +1,301 @@
+# Orchestration Remove Command
+
+Safely remove a task from the orchestration system, updating all references and dependencies.
+
+## Usage
+
+```
+/orchestration/remove TASK-ID [options]
+```
+
+## Description
+
+Removes a task completely from the orchestration system, handling all dependencies, references, and related documentation. Provides impact analysis before removal and ensures system consistency.
+
+## Basic Commands
+
+### Remove Single Task
+```
+/orchestration/remove TASK-003
+```
+Shows impact analysis and confirms before removal.
+
+### Force Remove
+```
+/orchestration/remove TASK-003 --force
+```
+Skips confirmation (use with caution).
+
+### Dry Run
+```
+/orchestration/remove TASK-003 --dry-run
+```
+Shows what would be affected without making changes.
+
+## Impact Analysis
+
+Before removal, the system analyzes:
+
+```
+Task Removal Impact Analysis: TASK-003
+======================================
+
+Task Details:
+- Title: JWT token validation
+- Status: in_progress
+- Location: /tasks/in_progress/TASK-003-jwt-validation.md
+
+Dependencies:
+- Blocks: TASK-005 (User profile API)
+- Blocks: TASK-007 (Session management)
+- Depends on: None
+
+References Found:
+- MASTER-COORDINATION.md: Line 45 (Wave 1 tasks)
+- EXECUTION-TRACKER.md: Active task count
+- TASK-005: Lists TASK-003 as dependency
+- TASK-007: Lists TASK-003 as dependency
+
+Git History:
+- 2 commits reference this task
+- Branch: feature/jwt-auth
+
+Warning: This task has downstream dependencies!
+
+Proceed with removal? [y/N]
+```
+
+## Removal Process
+
+### 1. Update Dependent Tasks
+```
+Updating dependent tasks:
+- TASK-005: Removing dependency on TASK-003
+  New status: Ready to start (no blockers)
+  
+- TASK-007: Removing dependency on TASK-003
+  Warning: Still blocked by TASK-009
+```
+
+### 2. Update Tracking Files
+```yaml
+# TASK-STATUS-TRACKER.yaml updates:
+status_history:
+  TASK-003: [REMOVED - archived to .removed/]
+  
+current_status_summary:
+  in_progress: [TASK-003 removed from list]
+
+removal_log:
+  - task_id: TASK-003
+    removed_at: "2024-03-15T16:00:00Z"
+    removed_by: "user"
+    reason: "Requirement changed"
+    final_status: "in_progress"
+```
+
+### 3. Update Coordination Documents
+```
+Updates applied:
+✓ MASTER-COORDINATION.md - Removed from Wave 1
+✓ EXECUTION-TRACKER.md - Updated task counts
+✓ TASK-DEPENDENCIES.yaml - Removed all references
+✓ Dependency graph regenerated
+```
+
+## Options
+
+### Archive Instead of Delete
+```
+/orchestration/remove TASK-003 --archive
+```
+Moves to `.removed/` directory instead of deleting.
+
+### Remove Multiple Tasks
+```
+/orchestration/remove TASK-003,TASK-005,TASK-008
+```
+Analyzes and removes multiple tasks in dependency order.
+
+### Remove by Pattern
+```
+/orchestration/remove --pattern "oauth-*"
+```
+Removes all tasks matching pattern.
+
+### Cascade Removal
+```
+/orchestration/remove TASK-003 --cascade
+```
+Also removes tasks that depend on this task.
+
+## Handling Special Cases
+
+### Task with Commits
+```
+Warning: TASK-003 has associated commits:
+- abc123: "feat(auth): implement JWT validation"
+- def456: "test(auth): add JWT tests"
+
+Options:
+[1] Keep commits, remove task only
+[2] Add removal note to commit messages
+[3] Cancel removal
+```
+
+### Task in QA/Completed
+```
+Warning: TASK-003 is in 'completed' status
+
+This usually means work was done. Consider:
+[1] Archive task instead of removing
+[2] Document why it's being removed
+[3] Check if commits should be reverted
+```
+
+### Critical Path Task
+```
+ERROR: TASK-003 is on the critical path!
+
+Removing this task will impact project timeline:
+- Current completion: 5 days
+- After removal: 7 days (due to replanning)
+
+Override with --force-critical
+```
+
+## Removal Strategies
+
+### Soft Remove (Default)
+```
+/orchestration/remove TASK-003
+```
+- Archives task file
+- Updates all references
+- Logs removal reason
+- Preserves git history
+
+### Hard Remove
+```
+/orchestration/remove TASK-003 --hard
+```
+- Deletes task file permanently
+- Removes all traces
+- Updates git tracking
+- No recovery possible
+
+### Replace Remove
+```
+/orchestration/remove TASK-003 --replace-with TASK-015
+```
+- Transfers dependencies to new task
+- Updates all references
+- Maintains continuity
+
+## Undo Capabilities
+
+### Recent Removal
+```
+/orchestration/remove --undo-last
+```
+Restores the most recently removed task.
+
+### Restore from Archive
+```
+/orchestration/remove --restore TASK-003
+```
+Restores archived task with all references.
+
+## Examples
+
+### Example 1: Obsolete Feature
+```
+/orchestration/remove TASK-008 --reason "Feature descoped"
+
+Removing TASK-008: OAuth provider integration
+- No dependencies
+- No commits yet
+- Safe to remove
+
+Task removed successfully.
+```
+
+### Example 2: Duplicate Task
+```
+/orchestration/remove TASK-012 --replace-with TASK-005
+
+Removing duplicate: TASK-012
+Transferring to: TASK-005
+- Dependencies transferred: 2
+- References updated: 4
+
+Duplicate removed, TASK-005 updated.
+```
+
+### Example 3: Changed Requirements
+```
+/orchestration/remove TASK-003,TASK-004,TASK-005 --reason "Auth system redesigned"
+
+Removing authentication task group:
+- 3 tasks to remove
+- 2 have commits (will archive)
+- 5 dependent tasks need updates
+
+Proceed? [y/N]
+```
+
+## Audit Trail
+
+All removals are logged:
+```yaml
+# .orchestration-audit.yaml
+removals:
+  - task_id: TASK-003
+    removed_at: "2024-03-15T16:00:00Z"
+    removed_by: "user-id"
+    reason: "Requirement changed"
+    status_at_removal: "in_progress"
+    dependencies_affected: ["TASK-005", "TASK-007"]
+    commits_preserved: ["abc123", "def456"]
+    archived_to: ".removed/2024-03-15/TASK-003/"
+```
+
+## Best Practices
+
+1. **Always Check Dependencies**: Review impact before removing
+2. **Document Reason**: Provide clear removal reason
+3. **Archive Important Work**: Use --archive for completed work
+4. **Update Team**: Notify about critical removals
+5. **Review Commits**: Check if code needs reverting
+
+## Integration
+
+### With Other Commands
+```
+# First check status
+/orchestration/status --task TASK-003
+
+# Then remove if needed
+/orchestration/remove TASK-003
+```
+
+### Bulk Operations
+```
+# Find and remove all on-hold tasks older than 30 days
+/orchestration/find --status on_hold --older-than 30d | /orchestration/remove --batch
+```
+
+## Safety Features
+
+- Confirmation required (unless --force)
+- Dependencies checked and warned
+- Commits preserved by default
+- Audit trail maintained
+- Undo capability for recent removals
+
+## Notes
+
+- Removed tasks are archived for 30 days by default
+- Git commits are never automatically reverted
+- Dependencies are gracefully handled
+- System consistency is maintained throughout

package/cli-tool/components/commands/orchestration/report.md

@@ -0,0 +1,292 @@
+# Task Report Command
+
+Generate comprehensive reports on task execution, progress, and metrics.
+
+## Usage
+
+```
+/task-report [report-type] [options]
+```
+
+## Description
+
+Creates detailed reports for project management, sprint reviews, and performance analysis. Supports multiple report types and output formats.
+
+## Report Types
+
+### Executive Summary
+```
+/task-report executive
+```
+High-level overview for stakeholders with key metrics and progress.
+
+### Sprint Report
+```
+/task-report sprint --date 03_15_2024
+```
+Detailed sprint progress with burndown charts and velocity.
+
+### Daily Standup
+```
+/task-report standup
+```
+What was completed, in progress, and blocked.
+
+### Performance Report
+```
+/task-report performance --period week
+```
+Team and individual performance metrics.
+
+### Dependency Report
+```
+/task-report dependencies
+```
+Visual dependency graph and bottleneck analysis.
+
+## Output Examples
+
+### Executive Summary Report
+```
+EXECUTIVE SUMMARY - Authentication System Project
+================================================
+Report Date: 2024-03-15
+Project Start: 2024-03-13
+Duration: 3 days (60% complete)
+
+KEY METRICS
+-----------
+• Total Tasks: 24
+• Completed: 12 (50%)
+• In Progress: 3 (12.5%)
+• Blocked: 2 (8.3%)
+• Remaining: 7 (29.2%)
+
+TIMELINE
+--------
+• Original Estimate: 5 days
+• Current Projection: 5.5 days
+• Risk Level: Low
+
+HIGHLIGHTS
+----------
+✓ Core authentication API completed
+✓ Database schema migrated
+✓ Unit tests passing (98% coverage)
+
+BLOCKERS
+--------
+⚠ Payment integration waiting on external API
+⚠ UI components need design approval
+
+NEXT MILESTONES
+--------------
+→ Complete JWT implementation (Today)
+→ Integration testing (Tomorrow)
+→ Security audit (Day 4)
+```
+
+### Sprint Burndown Report
+```
+/task-report burndown --sprint current
+```
+```
+SPRINT BURNDOWN - Sprint 24
+===========================
+
+Tasks Remaining by Day:
+Day 1: ████████████████████ 24
+Day 2: ████████████████     20 
+Day 3: ████████████         15 (TODAY)
+Day 4: ████████             10 (projected)
+Day 5: ████                 5  (projected)
+
+Velocity Metrics:
+- Average: 4.5 tasks/day
+- Yesterday: 5 tasks
+- Today: 3 tasks (in progress)
+
+Risk Assessment: ON TRACK
+```
+
+### Performance Report
+```
+TEAM PERFORMANCE REPORT - Week 11
+=================================
+
+By Agent:
+┌─────────────────┬────────┬───────────┬─────────┬────────────┐
+│ Agent           │ Completed │ Avg Time │ Quality │ Efficiency │
+├─────────────────┼────────┼───────────┼─────────┼────────────┤
+│ dev-frontend    │    8   │   3.2h    │   95%   │    125%    │
+│ dev-backend     │    6   │   4.1h    │   98%   │    110%    │
+│ test-developer  │    4   │   2.8h    │   100%  │    115%    │
+└─────────────────┴────────┴───────────┴─────────┴────────────┘
+
+By Task Type:
+- Features: 12 completed (avg 3.8h)
+- Bugfixes: 4 completed (avg 1.5h)
+- Tests: 8 completed (avg 2.2h)
+
+Quality Metrics:
+- First-time pass rate: 88%
+- Rework required: 2 tasks
+- Blocked time: 4.5 hours total
+```
+
+## Customization Options
+
+### Time Period
+```
+/task-report summary --from 2024-03-01 --to 2024-03-15
+/task-report summary --last 7d
+/task-report summary --this-month
+```
+
+### Specific Project
+```
+/task-report sprint --project authentication_system
+```
+
+### Format Options
+```
+/task-report executive --format markdown
+/task-report executive --format html
+/task-report executive --format pdf
+```
+
+### Include/Exclude
+```
+/task-report summary --include completed,qa
+/task-report summary --exclude on_hold
+```
+
+## Specialized Reports
+
+### Critical Path Analysis
+```
+/task-report critical-path
+```
+Shows tasks that directly impact completion time.
+
+### Bottleneck Analysis
+```
+/task-report bottlenecks
+```
+Identifies tasks causing delays.
+
+### Resource Utilization
+```
+/task-report resources
+```
+Shows agent allocation and availability.
+
+### Risk Assessment
+```
+/task-report risks
+```
+Identifies potential delays and issues.
+
+## Visualization Options
+
+### Gantt Chart
+```
+/task-report gantt --weeks 2
+```
+
+### Dependency Graph
+```
+/task-report dependencies --visual
+```
+
+### Status Flow
+```
+/task-report flow --animated
+```
+
+## Automated Reports
+
+### Schedule Reports
+```
+/task-report schedule daily-standup --at "9am"
+/task-report schedule weekly-summary --every friday
+```
+
+### Email Reports
+```
+/task-report executive --email team@company.com
+```
+
+## Comparison Reports
+
+### Sprint Comparison
+```
+/task-report compare --sprint 23 24
+```
+
+### Week over Week
+```
+/task-report trends --weeks 4
+```
+
+## Examples
+
+### Example 1: Morning Status
+```
+/task-report standup --format slack
+```
+Generates Slack-formatted standup report.
+
+### Example 2: Sprint Review
+```
+/task-report sprint --include-velocity --include-burndown
+```
+Comprehensive sprint metrics for review meeting.
+
+### Example 3: Blocker Focus
+```
+/task-report blockers --show-dependencies --show-resolution
+```
+Deep dive into what's blocking progress.
+
+## Integration Features
+
+### Export to Tools
+```
+/task-report export-jira
+/task-report export-asana
+/task-report export-github
+```
+
+### API Endpoints
+```
+/task-report api --generate-endpoint
+```
+Creates API endpoint for external access.
+
+## Best Practices
+
+1. **Daily Reviews**: Run standup report each morning
+2. **Weekly Summaries**: Generate performance reports on Fridays
+3. **Sprint Planning**: Use velocity trends for estimation
+4. **Stakeholder Updates**: Schedule automated executive summaries
+
+## Report Components
+
+Each report can include:
+- Summary statistics
+- Timeline visualization
+- Task lists by status
+- Agent performance
+- Dependency analysis
+- Risk assessment
+- Recommendations
+- Historical trends
+
+## Notes
+
+- Reports use data from all TASK-STATUS-TRACKER.yaml files
+- Completed tasks are included in historical metrics
+- Time calculations use business hours by default
+- All times shown in local timezone
+- Charts require terminal unicode support