emasoft/amama-status-reporting

Status Reporting Skill

Overview

Generate status reports by querying AI Maestro APIs for live agent, team, and task data. Reports combine API-sourced status with GitHub issue/PR data for a unified view.

Prerequisites

• AI Maestro running, API reachable at $AIMAESTRO_API
• GitHub CLI (gh) installed for issue/PR status
• design/reports/ directory must exist (create if missing)

Instructions

1. Determine report type: quick status, progress, handoff summary, or blocker
2. Query AI Maestro APIs for live data:
   • GET /api/sessions -- session liveness (proxies agent health; no /api/agents/health endpoint)
   • GET /api/agents -- registered agents (filter client-side by status)
   • GET /api/teams/{id} -- team config and members
   • GET /api/teams/{id}/tasks -- tasks with Kanban statuses
3. Query GitHub for issue/PR status via gh CLI
4. Read session memory files for additional context
5. Compile into report format and save to design/reports/
6. Present formatted report to user

Task Kanban statuses flow: backlog -> pending -> in_progress -> review -> completed. See task-system reference for details.

For API query examples, see api-endpoints reference.

Output

Reports are saved as Markdown to design/reports/:

• status-{date}.md -- Quick status
• progress-{date}.md -- Progress report
• handoff-{date}.md -- Handoff summary
• blockers-{date}.md -- Blocker report

For detailed report section formats, see report-formats reference.

Error Handling

| Error | Resolution | |-------|------------| | API unreachable | Start AI Maestro, report to user | | No active sessions | Report "no active agent sessions" | | Session inactive / stale | Escalate to AMCOS for recovery | | Team/task 404 | Verify team ID, create if needed | | GitHub API failure | Use cached data, note staleness | | Report dir missing | Create design/reports/ automatically |

Examples

Quick Status (abbreviated):

## Quick Status - 2025-01-30
### Agent Sessions
| Agent | Status | Uptime |
| amaa-architect | active | 2h 15m |
| amoa-orchestrator | active | 1h 42m |
### Task Kanban
| Status | Count |
| in_progress | 2 |
| completed | 4 |
**Blockers**: AMIA unresponsive -- escalating

For full examples including progress reports, see report-formats reference.

Checklist

Copy this checklist and track your progress:

• [ ] Determine report type (quick status, progress, handoff, blocker)
• [ ] Query AI Maestro APIs for sessions, agents, teams, tasks
• [ ] Query GitHub for issue/PR status via gh CLI
• [ ] Read session memory files for context
• [ ] Compile report and save to design/reports/
• [ ] Present formatted report to user

Resources

• api-endpoints -- API endpoint details and query examples
  • API Endpoints
  • Query Examples
  • Task Query for Reports
• task-system -- Task system and Kanban status details
  • Task Storage
  • Task Statuses (Kanban)
• report-formats -- Report types, formats, and full examples
  • Report Types
  • Output Locations
  • Report Sections
  • Full Examples
• checklist -- Step-by-step execution checklist
  • Status Reporting Checklist
  • Table of Contents
  • Determine report type
  • Verify AI Maestro API reachable
  • Query sessions endpoint
  • Query agents endpoint
  • Query teams endpoint
  • Query teams tasks endpoint
  • Verify GitHub CLI
  • Query GitHub issues and PRs
  • Read session memory files
  • Compile into report format
  • Create reports directory
  • Save report to file
  • Present report to user