budget-reporting

Budget Reporting

Generates a periodic activity report for datagouv/apistration at 4 levels of detail.

Prerequisites : the MCP linear-server must be connected (non-tech topics — user research, partnerships, steering committee, events — are only in Linear). If the MCP is not available, notify the user before starting; do not attempt to work around it.

Step 1 — Gather the parameters

Before any exploration, ask the user two questions (in a single message, compact format):

1. Period : start and end dates (e.g. 2026-04-01 → 2026-04-30). Deduce the file suffix (e.g. avril, 2026-q2).
2. Notable developments outside Linear/GitHub : structuring events invisible in commits/PRs/issues — partnership signed, steering committee, external event, org decision, launch of a cross-cutting program, etc.

Do not start the exploration until the answer is received.

Step 2 — Exploration

Collect in this order, in parallel when possible:

1. Commits on develop in the period:

   git log --since=YYYY-MM-DD --until=YYYY-MM-DD --pretty=format:'%h %ad %s' --date=short develop
   

2. GitHub PRs on datagouv/apistration (merged + open + closed in the period):

   gh pr list --repo datagouv/apistration --state all --limit 200 \
     --search "merged:YYYY-MM-DD..YYYY-MM-DD" \
     --json number,title,author,mergedAt,labels
   gh pr list --repo datagouv/apistration --state all --limit 200 \
     --search "created:YYYY-MM-DD..YYYY-MM-DD" \
     --json number,title,author,state,createdAt
   

   Read the body of significant PRs via gh pr view <num> --repo datagouv/apistration.
3. GitHub issues opened or closed in the period:

   gh issue list --repo datagouv/apistration --state all \
     --search "created:YYYY-MM-DD..YYYY-MM-DD" --json number,title,author,state
   

4. Linear : mcp__linear-server__list_issues for issues updated in the period. Filter by API Entreprise / API Particulier team. For non-tech topics (user research, partnerships, events, steering committee), Linear is often the only source.
5. Developments outside Linear/GitHub provided by the user in step 1.

Step 3 — Production of the deliverables

Produce 4 files in sandbox/ (create the folder if it does not exist), with a suffix derived from the period (e.g. avril, 2026-04, 2026-q2) :

File	Audience	Style	Template
sandbox/budget-summary-<suffixe>.exploration.md	internal record	raw, exhaustive	references/exploration.md
sandbox/budget-summary-<suffixe>.md	tech / product owners	detailed, structured, with PR#	references/tech-summary.md
sandbox/budget-executive-summary-<suffixe>.md	management / business	non-technical summary	references/executive-summary.md
sandbox/budget-flash-<suffixe>.md	comms deliverable	ultra-short, 3 sections	references/flash.md

Read the corresponding template before writing each file.

Cross-cutting rules

• Everything in French.
• No emojis.
• PR numbers (PR #N) included in exploration and tech-summary ; removed in executive and flash.
• Distinguish API Particulier (CNOUS, CAF/CNAV QF, MEN bourses [education grants], Pôle Emploi, DGFiP particulier [individual services]…) and API Entreprise (Data Subvention, GIP-MDS effectifs [staff counts], INSEE, DGFiP entreprise [business services], Acoss/Urssaf, MICAF…) when the context allows.
• The file exploration must make it possible to regenerate the other 3: record in it all raw sources (PRs, commits, Linear issues by identifier, external events).
• The file flash must fit in ~15 bullets across 3 sections: Notable changes / API Particulier / API Entreprise.
• Never invent figures: any volume cited must come from the exploration.

Step 4 — Reporting

Announce the 4 paths created in one sentence. Do not copy the content.