Evidence organized is handled by this skill in a customer-readable, reusable workflow.
Blockers reported is handled by this skill in a customer-readable, reusable workflow.
What is this?
A project can have real progress and still feel invisible to the owner if the evidence is buried in diffs, task files, logs, and chat history. Project Report Generator turns that evidence into a report for the intended audience: completed work, verification status, blockers, decisions, risks, and next actions. It helps founders, clients, and teams understand the state of work without reading raw engineering artifacts.

When this helps
- Owner report
- Evidence summary
- Blocker list
- Next-action section
- A lot has happened in the project, but you no longer have a clear view of what is done, what is blocked, what is risky, and what decision comes next.
- You need to report to a founder, client, team, or yourself without relying on vague progress impressions.
- You want tasks, evidence, blockers, important changes, and next steps turned into a readable operating report.
- It cannot create reliable reports from missing evidence. Weak source evidence must be labeled, not hidden.
Clearer progress visibility -> Better stakeholder updates -> Reusable report rhythm
A normal summary prompt can sound polished while mixing facts, assumptions, and missing evidence. Project Report Generator is stronger because it builds reports from governed project evidence, separates progress from blockers, and turns next actions into owner-readable status. The buyer gets a report that is useful for decisions, not just a narrative recap. Boundary: It cannot create reliable reports from missing evidence; weak source evidence must be labeled, not hidden.
Included interface patterns
Reusable project report intake workflow support.
report-intake.mdReusable evidence summary table workflow support.
evidence-summary-table.mdReusable project report template workflow support.
project-report-template.md