For the complete documentation index, see llms.txt. This page is also available as Markdown.

Task Status Tracking

Overview

Task status communicates intent and progress.

Consistent status use keeps reporting reliable.

Key Concepts

  • Status: current state of execution work

  • Status type: reusable workflow definition

  • Blocked: explicit signal that work cannot proceed

How It’s Used

Update status during daily execution.

Review status distribution during weekly governance.

Benefits

  • Clear execution signals for stakeholders

  • Faster escalation of risk

  • Cleaner reporting across Projects

Setup Steps

1

Set a starting status

  1. Create or open a task.

  2. Set status to the correct starting state.

  3. Avoid moving work to In progress without active execution.

2

Use Blocked as a high-signal state

  1. Set status to Blocked when progress cannot continue.

  2. Add a comment with the unblock condition.

  3. Add an owner for the unblock action.

3

Close tasks cleanly

  1. Set status to Complete only when acceptance criteria are met.

  2. Add evidence links or notes when required.

Best Practices

  • Keep statuses simple and stable.

  • Use the same meanings across Projects when possible.

  • Review blocked and overdue work weekly.

Summary

Status is a shared contract for progress reporting.

For status definitions and governance, see Status Types and Meanings.

Last updated