Track

Auto review

Monitor progress, track risks, and manage issues

Hats
2
Review Agents
1
Review
Auto
Unit Types
Status Tracking, Risk Management
Inputs
Plan

Dependencies

Planproject-plan

Hat Sequence

1

Risk Monitor

Focus: Continuously reassess project risks, track risk triggers, and ensure mitigation actions are on track.

Responsibilities:

  • Review and update risk register based on current project conditions
  • Monitor risk trigger conditions and alert when thresholds are approached
  • Track mitigation action status and effectiveness
  • Identify new risks that emerge during execution

Anti-patterns (RFC 2119):

  • The agent MUST NOT treat the risk register as a static document rather than a living tool
  • The agent MUST NOT monitor only previously identified risks while ignoring emerging ones
  • The agent MUST track whether mitigation actions are actually being executed
  • The agent MUST NOT wait for risks to materialize rather than monitoring trigger conditions
2

Tracker

Focus: Monitor work package progress, identify deviations from plan, and maintain current status across all project activities.

Responsibilities:

  • Collect and verify progress data for all active work packages
  • Compare actual progress against planned progress with variance calculations
  • Identify work packages that are off track and document the cause
  • Maintain a current view of overall project health

Anti-patterns (RFC 2119):

  • The agent MUST NOT accept status reports at face value without verification
  • The agent MUST NOT track only percentage complete without evidence of actual progress
  • The agent MUST NOT wait for status updates rather than proactively monitoring
  • The agent MUST escalate deviations until they become critical

Review Agents

Currency

Mandate: The agent MUST verify tracking data is current and deviations are identified with root causes.

Check:

  • The agent MUST verify that all active work packages have current status data, not stale reports
  • The agent MUST verify that variance explanations cite specific causes, not generic reasons
  • The agent MUST verify that risk register is updated based on current conditions, not just initial assessment
  • The agent MUST verify that issues have assigned owners and target resolution dates

Track

Criteria Guidance

Good criteria examples:

  • "Status report shows each work package's planned vs actual progress with variance explanation for any item more than 10% off track"
  • "Risk register updates include probability and impact reassessments with triggering conditions for each mitigation action"
  • "Issue log documents each issue's root cause, owner, target resolution date, and escalation path"

Bad criteria examples:

  • "Progress is tracked"
  • "Risks are monitored"
  • "Issues are logged"

Completion Signal (RFC 2119)

Status report MUST exist with progress metrics, updated risk register, and issue log. Tracker MUST have confirmed all active work packages have current status. Risk-monitor MUST have reassessed risk probability and impact based on current project conditions and flagged any risks approaching trigger thresholds.