Reporting for Management

A report in the system is a letter for a specific reader, assembled from evidence: status snapshots, the delta, the plan, and the risk register. Not a "dashboard", not a summary of the conversation, not invented percentages.

Step 1. Format: /report-format

Before the first report, the format must be agreed. The report-format.md file stores "slots" — style-and-period combinations:

Style	What it is
full	A full report: RAG ratings (schedule, budget, scope, risks), summary, progress vs plan, themes/epics, plan and performance, risks, decisions and asks
lean	A short letter: summary, overall status, key metrics, done, in progress, risks, asks

Periods: weekly, monthly, quarterly — they change the emphasis, not the structure.

Each section of a slot is a pair: "id (machine key) + caption (in the format language)". The agent shows you the section captions — you can change, add, or remove them until the slot is marked confirmed.

Extra slot keys:

• audience — who the report is addressed to;
• include_timeline_appendix — whether to attach a schedule excerpt;
• pptx_template — the path to your PPTX template (below).

Type /report-format full weekly (or /report-format defaults — propose skeletons for all missing slots) and confirm the slot.

Step 2. The report: /report

Type /report (optionally: /report full weekly, /report lean monthly). What happens:

1. Input check. The agent checks that everything is in place: a living risk register, a fresh status snapshot (not older than yesterday), and, if needed, a budget snapshot. What is missing comes as a short checklist and a pause: either you run the missing steps, or you explicitly say "continue with gaps" (the report will show "not available").
2. The delta. If there is no fresh delta (for today/yesterday), the agent runs /status-delta over the snapshots on its own — without waiting for a command.
3. Composing the letter. Sections are filled from evidence only: snapshots, the delta, the plan, the register, the tracker. No data — "not available", not guesswork.

Key rules of the report:

• The overall status (R/Y/G) is set by a human, not the agent: it does not derive the color from ticket counts. Red always comes with an ask.
• Milestones are binary: complete / not complete. No "90% of the milestone is done".
• Bad news is not buried: problems go into the summary and the risks.
• Decisions and asks are actionable: who, what, by when.

Result — the file status-report-<style>-<period>-YYYY-MM-DD.md. A same-day re-run updates the same file.

PPTX from your template

If the slot has pptx_template set (for example, "last week's" report or a corporate template), the agent also produces a PPTX:

• the agent reads the text blocks of your template, understands them by meaning (not by shape names), and updates the matching sections with the new data;
• the output — status-report-…-YYYY-MM-DD.pptx next to the .md (the text version remains the canonical record);
• slides are not added or removed: the template defines the structure, the agent fills it.

How to set the template: upload the PPTX to the session materials and say "use this template for full/weekly" — the agent will propose recording it in the slot.

Publishing

The draft is always yours, in the chat/materials. Publishing (for example, to a Confluence page) is a proposal only: you decide what goes where. There is no silent sending.

Quality review: /quality

A separate command — a delivery-quality review at planned points (phase entries, gate controls):

• the agent requests evidence — the documents and decisions that should exist at this phase (charter, scope baseline, plan, risk register, sprint outcomes, release readiness, close-out);
• each row gets a status: present / partial / missing / N-A — with a source;
• if the client declined a recommended practice — it is recorded: what was proposed, the consequences, the decision (who, when) — and a reminder to revisit at close-out;
• the output — a dated review document with an action plan (who, by when, which command closes the gap).

The review rhythm depends on project length: short (3–5 months) — 2 points; medium (6–10) — 3; long (10+) — per phase.

How the cycle comes together

end of period:
  /status-snapshot + /budget-snapshot  → the inputs
  /report full weekly                   → the letter for management
  /report + pptx_template               → the PPTX for the presentation
  /quality (on schedule)                → the process check at the phase point

Where to continue

• Status snapshots and change analysis — the inputs for reports.
• Risk management — the risks section of the report.
• Schedule planning — milestones and the critical path in the appendix.