gapfDev Status Reporter
Generate a short and actionable execution report for stakeholders and orchestration agents.
Input
- Milestone ticket list and states.
- Dependency map and current bottlenecks.
- Latest PR and issue activity.
- Constraint: Keep report concise and action-first.
Output
- Current progress snapshot.
- Bottleneck and blocker summary.
- Immediate next actions by agent.
Process
Phase 1: Gather Current State
- Count closed/open/blocked tickets.
- Identify recently changed tickets and PRs.
- Detect dependency bottlenecks.
- For each In Progress ticket with an active branch, check if the branch is behind the target branch. If behind, append
[STALE: N commits behind]to the ticket status in the report.
Phase 2: Build Action Report
- Summarize progress in one block.
- Highlight who is waiting on what.
- List next actions in dependency order.
Phase 3: Publish and Follow-up
- Post or share the status update.
- Include time of snapshot and scope.
- Trigger follow-up when blockers persist.
Completeness Checklist
- □ Report includes done/open/blocked numbers.
- □ Report identifies current bottleneck ticket(s).
- □ Report lists concrete next actions per agent.
Rules
- ALWAYS include timestamp and scope in each report.
- ALWAYS connect blockers to exact dependency tickets.
- NEVER publish narrative-only reports without actions.
- NEVER mix historical and current status without clear separation.