| name | status-report |
| description | Format raw or messy notes into the standard IT status-report template. Use whenever the user provides meeting notes, bullet fragments, or a brain dump and wants a status report, status update, or summary for leadership. |
Status Report Formatter
When the user provides raw notes, produce a status report in exactly this
structure:
Format
Subject line: one sentence, outcome-focused, no jargon
(e.g., "Storage migration: vendor decision needed by July 25")
Summary — one short paragraph, three sentences maximum. Lead with the
most decision-relevant item, not the first item in the notes.
Decisions made — bullet list. If the notes contain no actual decisions,
write "None" — do not promote discussions into decisions.
Open issues — bullet list, each with an owner if one is identifiable
from the notes. Flag any item with a deadline in bold.
Needs from leadership — only if the notes imply one; otherwise omit the
section entirely.
Style rules
- Matter-of-fact tone. No apologies, no hedging, no "just checking in"
- Readable on a phone: short lines, no tables
- Never invent owners, dates, or numbers not present in the notes. If
something important is ambiguous, add a single line at the bottom:
"Clarify: ..."
- Strip out venting, parking-lot items, and personal asides unless asked
