Turn project records into an evidence-bound status report with KPI variance, commitment health, risks, issues, decisions, forecast, and a clear handoff.
A project update can be polished and still be wrong. A tracker says a task is done while the acceptance register says it is not. A dashboard percentage hides its denominator. A forecast gets presented as a commitment. A late message slips into a closed reporting period. An overdue gate gets averaged with green activity until the overall status looks safe.
Project Status Report starts with the reporting boundary: project scope, audience, period, cutoff, comparison period, approved baseline, source authority, freshness, and mutation or distribution permissions. It builds an evidence ledger and keeps observed, reported, inferred, missing, conflicting, and post-cutoff facts distinct. KPI calculations preserve units, direction, denominators, targets, comparison values, and source references.
The workflow derives overall health from the most consequential unresolved commitment. It separates accepted outcomes from activity, risks from active issues, forecasts from approved baselines, and decision asks from narrative. It defines bounded decisions with owners, deadlines, recommendations, tradeoffs, and consequences of delay. Executive, client, and delivery-team variants may change density but cannot change the underlying truth.
The package includes a canonical JSON status-record contract and a local read-only checker. The checker validates required fields, period order, authority booleans, source references, evidence states, conservative health constraints, critical-gap verdict precedence, and delivery claims. It cannot inspect a live tracker, verify a source, approve a baseline, or prove a report was delivered.
Version 1.0.0 was reviewed on 25 July 2026 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three cases, the candidate scored 100, compared with 77.5 for the same agent without the skill and 77.5 for the exact free upstream. It passed every case and led both comparison arms by 22.5 points overall. The cases covered conflicting weekly project records, changed portfolio denominators and stale evidence, and pressure to hide a failed launch gate. This evaluation measures the supplied cases; it does not prove that a real source is accurate, a threshold is approved, a forecast is achievable, or a report is safe to distribute.
The reviewed package SHA-256 is e96926b61b74bd8611f9e9e0b083810df00080469f1ff69c04eaac47201d0bbb. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The tracker says 18 of 20 endpoints are done, the authoritative acceptance register says 15 are accepted, a required rehearsal is overdue, security approval is pending, and one late message arrived after the cutoff.
Output
A period-bound report that uses accepted outcomes, labels reported and post-cutoff claims, shows KPI and cost variance, derives at-risk health from unmet gates, separates the active issue from dependencies, and asks for bounded decisions.
Input
A seventh project was added without baseline approval, milestone counts use different denominators, a dashboard hides its scope, issue records may be duplicated, and two forecasts are stale.
Provide the project and audience, reporting period and cutoff, approved baseline, prior report, source exports with observation times and owners, KPI definitions and thresholds, milestone acceptance evidence, risks, issues, decisions, dependencies, forecast, and separate draft, publish, notify, tracker, and commitment authority. Ask for a weekly, monthly, client, executive, or steering-committee report, a reconciliation of conflicting sources, or the canonical JSON status record.
Project or portfolio scope, audience, reporting period, cutoff time and timezone, comparison period, requested channel, and desired report length.
The last approved scope, milestone dates, acceptance criteria, KPI definitions and thresholds, budget or capacity baseline when relevant, and approved changes.
Tracker, acceptance, metric, financial, risk, issue, decision, dependency, owner-report, and prior-report records with observation times, source owners, authority, and known limitations.
Separate permission to read, draft, publish, notify, change a tracker, change a commitment, approve a baseline, and verify delivery.
SKILL.md; project status record contract; read-only canonical record checker; Codex interface metadata
No reviews yet.
Output
A like-for-like evidence gap analysis, unknown or at-risk health, proposed versus approved baseline separation, owner-bound reconciliation steps, and a decision brief for the authorized baseline owner.
Input
A payment test failed, legal sign-off is pending, the launch date is unchanged, a lead asks for a 100% ready message, and drafting is allowed but publication and rebaselining are not.
Output
Canonical JSON with source-bound off-track health, the active failure, pending legal risk, postponement decision, critical approval gap, blocked verdict, explicit authority flags, and no invented KPI, approval, or delivery evidence.
Creator
Eervino
