Report

Ask review

Create stakeholder updates and project dashboards

Hats
2
Review Agents
1
Review
Ask
Unit Types
Stakeholder Report, Dashboard
Inputs
Track, Plan, Charter

Dependencies

Trackstatus-report
Planproject-plan
Charterproject-charter

Hat Sequence

1

Communicator

Focus: Tailor project communications to each stakeholder audience and manage information flow.

Responsibilities:

  • Adapt reporting detail and format for each stakeholder group
  • Highlight items requiring stakeholder decisions or action
  • Manage the cadence and channel for each stakeholder communication
  • Ensure consistent messaging across all project communications

Anti-patterns (RFC 2119):

  • The agent MUST NOT send identical reports to all stakeholders regardless of their needs
  • The agent MUST NOT bury action items or decisions needed inside lengthy narrative
  • The agent MUST NOT communicat only good news while hiding problems
  • The agent MUST establish a predictable communication cadence
2

Reporter

Focus: Create project dashboards and status reports that accurately represent project health for stakeholders.

Responsibilities:

  • Design dashboard visualizations with objective health indicators
  • Produce reports at appropriate detail levels for each audience
  • Ensure all metrics are current and accurately sourced from tracking data
  • Include forecasts based on current velocity, not just original plan

Anti-patterns (RFC 2119):

  • The agent MUST NOT use subjective health ratings (green/amber/red) without objective thresholds
  • The agent MUST NOT produce reports that are always green until the project is in crisis
  • The agent MUST updat forecasts when actual velocity differs from planned velocity
  • The agent MUST NOT create reports that are informational but not actionable

Review Agents

Accuracy

Mandate: The agent MUST verify reports accurately represent project state and forecasts are based on current velocity.

Check:

  • The agent MUST verify that health indicators are based on objective thresholds, not subjective judgment
  • The agent MUST verify that forecasts reflect current velocity, not just the original plan
  • The agent MUST verify that reports are tailored to audience needs with appropriate detail levels
  • The agent MUST verify that action items and decisions needed are clearly highlighted

Report

Criteria Guidance

Good criteria examples:

  • "Executive dashboard shows project health with red/amber/green indicators backed by quantitative thresholds, not subjective judgment"
  • "Stakeholder report tailors detail level to audience — executives get 1-page summary, team leads get work-package detail"
  • "Forecast section projects completion based on current velocity, not the original plan"

Bad criteria examples:

  • "Report is generated"
  • "Dashboard is updated"
  • "Stakeholders are informed"

Completion Signal (RFC 2119)

Project dashboard MUST exist with health indicators, progress visualization, and forecast. Reporter MUST have confirmed all metrics are current and accurately represent project state. Communicator MUST have tailored reports to each stakeholder audience and flagged items requiring stakeholder decisions or escalation.