sitrep-reporting

Convert vague status updates into structured SITREP messages with status codes and ETAs.

2|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/krzemienski/shannon-framework --skill sitrep-reporting
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: sitrep-reporting
Source: https://github.com/krzemienski/shannon-framework/tree/main/skills/sitrep-reporting
Command: npx skills add https://github.com/krzemienski/shannon-framework --skill sitrep-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Military-style SITREP protocol that enforces structured status updates with codes, progress, blockers, dependencies, ETAs, and secure handoffs.

Core Features & Use Cases

  • Full and brief SITREP formats
  • Status codes, progress metrics, blockers, and dependencies
  • Authorization codes for handoffs
  • Wave coordination and burn-in for multi-agent flows

Quick Start

Use SITREP reporting when a coordinator requests status across several agents.

Frequently Asked Questions about sitrep-reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure status updates for multi-agent coordination?ā–¼

SITREP reporting converts vague status updates into structured messages with explicit status codes (🟢, 🟔, šŸ”“), quantified progress, blockers, dependencies, and ETAs. Use full or brief SITREP formats on 30-minute intervals or when triggered, ensuring all agents report consistently for wave coordination and handoff authorization.

What is a SITREP and when do I need structured status reporting?ā–¼

SITREP is a military-style protocol enforcing precise, auditable status messages across teams. Use it when coordinating multiple agents, escalating blockers, authorizing handoffs, or maintaining cross-session audit trails—particularly in workflows requiring formal status codes and quantified progress metrics.

How do I set up handoff authorization codes between agents?ā–¼

SITREP reporting generates secure HANDOFF codes that authorize agent transitions within multi-agent flows. Each handoff includes status validation, blocker clearance checks, and ETA confirmation, integrating with wave orchestration to ensure coordinated, auditable agent handoffs.

Can I use SITREP reporting for trigger-based alerts instead of regular intervals?ā–¼

Yes. SITREP reporting supports both regular 30-minute interval reports and trigger-based escalations. Use trigger reports when blockers emerge, dependencies change, or status shifts to 🟔 or šŸ”“, maintaining audit trails through context-preservation and Serena integration.

What's the difference between full and brief SITREP formats?ā–¼

Full SITREP includes all fields—status codes, progress, blockers, dependencies, ETAs, and handoff codes—for formal reviews. Brief SITREP strips non-critical details for quick updates while maintaining status codes and critical blockers, enabling faster coordination without losing accountability.

How does SITREP integrate with wave orchestration for multi-agent workflows?ā–¼

SITREP reporting enforces structured formatting across agent waves, enabling burn-in tracking, dependency mapping, and coordinated handoffs. Each agent's SITREP syncs with wave state, ensuring blockers propagate upward and handoff authorization aligns with orchestration logic.