Execution status management and reporting for implementation plugin. Use when initializing execution tracking, updating task status, generating progress reports, calculating completion metrics, tracking layer execution, monitoring feature implementation progress, or when user mentions execution status, progress tracking, or implementation monitoring.
Limited to specific tools
Additional assets for this skill
This skill is limited to using the following tools:
examples/error-scenarios.mdexamples/status-examples.mdexamples/workflow-integration.mdscripts/calculate-metrics.shscripts/parse-layered-tasks.shscripts/update-status.shtemplates/error-log-entry.jsontemplates/execution-status.jsontemplates/layer-entry.jsontemplates/status-report.mdtemplates/task-entry.jsonStatus file management and progress reporting for the implementation plugin.
This skill provides comprehensive execution tracking capabilities including status file initialization, task completion tracking, progress calculation, report generation, and metrics aggregation. Manages execution state in .claude/execution/ directory with JSON-based status files.
Use this skill when:
Script: scripts/update-status.sh init <spec-id>
Creates new execution status file from layered tasks specification.
What it does:
specs/<spec>/layered-tasks.md to extract task structure.claude/execution/<spec>.json status fileExample:
bash scripts/update-status.sh init F001
# Creates: .claude/execution/F001.json
Script: scripts/update-status.sh update <spec> <layer> <task-index> <status>
Updates individual task completion status.
Supported statuses:
complete - Task successfully completedfailed - Task execution failedskipped - Task skipped (dependency issue)in_progress - Task currently executingWhat it does:
last_updated timestampExample:
bash scripts/update-status.sh update F001 L1 2 complete
# Marks third task in L1 as complete
Script: scripts/update-status.sh complete-layer <spec> <layer>
Marks entire layer as complete and advances to next layer.
What it does:
current_layer to next layerExample:
bash scripts/update-status.sh complete-layer F001 L0
# Marks L0 complete, advances to L1
Script: scripts/update-status.sh error <spec> <layer> <task-index> <error-message>
Logs execution errors for troubleshooting.
What it does:
Example:
bash scripts/update-status.sh error F001 L1 3 "API endpoint creation failed: invalid path syntax"
Script: scripts/update-status.sh report <spec>
Creates comprehensive progress report from status file.
Report includes:
Output:
Feature F001: AI Chat Interface
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall Progress: 38% (5/13 tasks)
Time Elapsed: 30 minutes
Estimated Remaining: 49 minutes
Layer 0 (Infrastructure): ✅ Complete (2/2 tasks)
Layer 1 (Core Services): 🔄 In Progress (3/5 tasks)
Layer 2 (Features): ⏳ Pending (0/4 tasks)
Layer 3 (Integration): ⏳ Pending (0/2 tasks)
Currently Executing:
- Create message API endpoint (fastapi-agent, medium) - Started 5m ago
Next 3 Pending Tasks:
1. [L1] Implement chat storage (supabase-agent, easy)
2. [L1] Add user authentication (auth-agent, medium)
3. [L2] Build chat UI component (react-agent, hard)
Errors: 0
Next Action: Continue L1 execution with /implementation:execute F001 --layer=L1
.claude/execution/<spec>.json (e.g., .claude/execution/F001.json)
{
"feature": "F001",
"feature_name": "AI Chat Interface",
"started_at": "2025-11-17T12:00:00Z",
"last_updated": "2025-11-17T12:30:00Z",
"status": "in_progress",
"current_layer": "L1",
"total_tasks": 13,
"completed_tasks": 5,
"failed_tasks": 0,
"skipped_tasks": 0,
"completion_percentage": 38,
"average_task_duration_ms": 1450,
"estimated_remaining_ms": 11600,
"layers": {
"L0": {
"name": "Infrastructure",
"status": "complete",
"total_tasks": 2,
"completed_tasks": 2,
"failed_tasks": 0,
"started_at": "2025-11-17T12:00:00Z",
"completed_at": "2025-11-17T12:10:00Z",
"duration_ms": 600000,
"tasks": [
{
"index": 0,
"description": "Setup database schema",
"command": "/supabase:create-schema chat",
"agent": "supabase-agent",
"complexity": "easy",
"status": "complete",
"started_at": "2025-11-17T12:00:00Z",
"completed_at": "2025-11-17T12:05:00Z",
"duration_ms": 300000,
"output": "Created schema successfully",
"files_created": ["supabase/migrations/001_chat_schema.sql"]
},
{
"index": 1,
"description": "Initialize API structure",
"command": "/fastapi-backend:init api",
"agent": "fastapi-agent",
"complexity": "easy",
"status": "complete",
"started_at": "2025-11-17T12:05:00Z",
"completed_at": "2025-11-17T12:10:00Z",
"duration_ms": 300000,
"output": "API structure initialized",
"files_created": ["backend/app/main.py", "backend/app/routers/__init__.py"]
}
]
},
"L1": {
"name": "Core Services",
"status": "in_progress",
"total_tasks": 5,
"completed_tasks": 3,
"failed_tasks": 0,
"started_at": "2025-11-17T12:10:00Z",
"tasks": [...]
},
"L2": {
"name": "Features",
"status": "pending",
"total_tasks": 4,
"completed_tasks": 0,
"failed_tasks": 0,
"tasks": [...]
},
"L3": {
"name": "Integration",
"status": "pending",
"total_tasks": 2,
"completed_tasks": 0,
"failed_tasks": 0,
"tasks": [...]
}
},
"errors": [],
"warnings": [],
"next_action": "Continue L1: 2 tasks remaining"
}
completion_percentage = (completed_tasks / total_tasks) * 100
layer_percentage = (layer.completed_tasks / layer.total_tasks) * 100
avg_task_duration = sum(all_completed_task_durations) / completed_tasks
remaining_tasks = total_tasks - completed_tasks
estimated_remaining = avg_task_duration * remaining_tasks
attempted_tasks = completed_tasks + failed_tasks + skipped_tasks
success_rate = (completed_tasks / attempted_tasks) * 100
layer_duration = layer.completed_at - layer.started_at
pending - Not started (0% complete)in_progress - Some tasks complete (1-99%)paused - Execution paused (manual intervention needed)complete - All tasks done (100% complete)failed - Critical error, cannot continuepending - Not yet startedin_progress - Currently executingcomplete - Successfully finishedfailed - Execution failedskipped - Skipped due to dependency# Initialize tracking
bash scripts/update-status.sh init F001
# Update tasks as they complete
bash scripts/update-status.sh update F001 L0 0 complete
bash scripts/update-status.sh update F001 L0 1 complete
# Mark layer complete
bash scripts/update-status.sh complete-layer F001 L0
# Generate report
bash scripts/update-status.sh report F001
# Agent reads status file
status=$(cat .claude/execution/F001.json)
# Agent updates task status
bash scripts/update-status.sh update F001 L1 2 complete
# Agent generates report for user
bash scripts/update-status.sh report F001
# Log error when task fails
bash scripts/update-status.sh error F001 L1 3 "Database connection timeout"
# Check error count before continuing
error_count=$(jq '.errors | length' .claude/execution/F001.json)
if [ "$error_count" -gt 5 ]; then
echo "Too many errors, pausing execution"
bash scripts/update-status.sh pause F001
fi
See templates/ directory for:
See examples/ directory for:
Used by:
/implementation:execute command - Main execution orchestratorprogress-tracker agent - Real-time progress monitoringerror-handler agent - Error logging and recovery/implementation:status command - Status reportingDepends on:
layered-tasks.md - Source of task definitionsfeatures.json - Feature metadataLocation: plugins/implementation/skills/execution-tracking/
Purpose: Comprehensive execution status management
Complexity: Medium - Requires JSON manipulation and metric calculation