/task-update

Update task tracking files to reflect current progress and status.

Overview

The /task-update command maintains accurate task tracking within your project. It updates task files in .orchestre/tasks/ to reflect completed work, progress made, and new tasks discovered during development.

This command was recovered from Orchestre v4 and enhanced in v5.3.0 with improved task file formats and automatic progress tracking.

Usage

/task-update [task-info]

Parameters

• task-info (optional): Specific task or context to update
  • Examples: "completed authentication", "api endpoints in progress", "discovered new requirements"
  • Default: Updates based on recent activity

Examples

Basic Task Update

/task-update

Automatically detects recent changes and updates task tracking accordingly.

Mark Task Complete

/task-update "completed user authentication feature"

Updates the task tracking to mark authentication as complete and document outcomes.

Progress Update

/task-update "api development 70% complete, 3 endpoints remaining"

Updates task progress with specific completion information.

Task File Structure

Task files in .orchestre/tasks/ follow this format:

{
  "id": "task-2024-01-15-001",
  "command": "/execute-task",
  "title": "Implement user authentication",
  "status": "in-progress",
  "progress": 70,
  "created": "2024-01-15T10:00:00Z",
  "updated": "2024-01-15T14:30:00Z",
  "outcomes": {
    "completed": [
      "Login endpoint",
      "Registration flow",
      "JWT token generation"
    ],
    "remaining": [
      "Password reset",
      "Email verification",
      "OAuth integration"
    ],
    "discovered": [
      "Need rate limiting",
      "Session management complexity"
    ]
  }
}

Workflow Integration

The /task-update command:

1. Analyzes Current State

   • Scans .orchestre/tasks/ directory
   • Identifies active and recent tasks
   • Checks code changes since last update

2. Updates Task Files

   • Modifies task status (pending → in-progress → completed)
   • Updates progress percentages
   • Documents outcomes and learnings

3. Maintains History

   • Preserves task evolution
   • Tracks time spent
   • Documents blockers and solutions

Automatic Tracking

All Orchestre commands automatically create task entries:

• /execute-task creates detailed task files
• /compose-saas-mvp tracks MVP progress
• /add-enterprise-feature documents feature additions
• Other commands create appropriate task records

Best Practices

1. Regular Updates

   • Update tasks as you make progress
   • Don't wait until completion
   • Document blockers immediately

2. Detailed Information

   • Include specific outcomes
   • Note unexpected discoveries
   • Document decision changes

3. Team Coordination

   • Update before handoffs
   • Document dependencies
   • Note collaboration points

Task Status Flow

pending → in-progress → completed
                ↓
            blocked → in-progress

Integration with Other Commands

• Works with /status to show task progress
• Complements /execute-task execution
• Feeds into /update-memory for documentation
• Helps /orchestrate understand project state

Related Commands

• /execute-task - Execute tasks intelligently
• /status - View project status
• /update-memory - Update project memory
• /orchestrate - Analyze and plan

Version History

• v5.3.0: Recovered from v4, enhanced task file format
• v4.0.0: Original implementation with basic tracking