jupes/agent-forge-harness / .agents/skills/project-status-report
project-status-report
VerifiedCreate a polished project-status PDF for a manager or director from Beads, user notes, and attached documents. Use for fortnightly updates or a user-specified reporting period.
Project status report
Deliver a shareable PDF that answers: where the project stands, what changed, why it matters, and what leadership needs to decide. Translate engineering activity into supported outcomes without inflating delivery or business impact.
1. Set the reporting contract
Resolve the project, audience, period, timezone, and supplied material from context. Ask only if project selection or a material date ambiguity remains unresolved. Default to the last 14 completed calendar days, ending yesterday in the user's timezone. Print inclusive start/end dates and the timezone. If the user includes today, label it a partial day and show the extraction cutoff.
Use a manager/director audience and a restrained editorial design unless the user provides branding. Keep the main report to about two pages when content allows; add pages for meaningful evidence rather than shrinking text.
2. Gather and reconcile evidence
Read evidence rules before querying Beads or synthesizing documents. Inspect all project members and dependencies, not only ready work. Collect period events, the status at period end, and current risks separately. Read relevant user notes and attachments, including tables and page context.
Write a local evidence ledger under reports/<slug>/: claim, date, source locator,
confidence, and whether it is an outcome, current status, or plan. Preserve raw
exports in that ignored directory when useful. Reading the tracker is sufficient;
report generation does not require changing issues or publishing project data.
This step is complete when every proposed headline and metric has support, conflicting accounts are resolved or marked, and unavailable sources are explicitly listed. If the tracker is unavailable, a report from supplied material is valid with that coverage limitation; absence of data is not evidence of no progress.
3. Synthesize for leadership
Lead with overall health and a short rationale, followed by:
- Accomplishments: the material change and its supported value, grouped by outcome.
- Risks and blockers: consequence, mitigation, owner and date when known.
- Next period: planned outcomes with owners/targets where supported.
- Decisions needed: the choice, why now, and the effect of delay.
- Evidence and coverage: compact source notes and important limitations.
Use On track / At risk / Off track / Unknown as textual status labels. Explain the assessment against commitments; use Unknown when milestones or status evidence are insufficient. Distinguish shipped, verified, implemented, and merely closed issues. Metrics are optional, never substitutes for outcomes. Include a prior-period trend only when comparable evidence exists. Treat absent owners and dates as unassigned or unconfirmed.
4. Render
Read the PDF contract and layout guide. Create report JSON using the synthetic example as a structural guide; replace its content completely. The reusable renderer takes two paths:
python .claude/skills/project-status-report/scripts/render_report.py <report.json> <report.pdf>
It requires Python 3.10+ and ReportLab; the guide covers runtime discovery, fonts,
rendering, and alternatives. It emits {ok,data,error} and a nonzero exit on failure.
Keep real outputs and evidence under ignored reports/, or the user's destination.
The helper creates a local PDF only; it does not upload or send it.
5. Verify and deliver
Extract the PDF text and compare dates, numbers, qualifications, and source notes with the evidence ledger. Render every page to PNG and inspect at readable size. Correct clipping, awkward splits, missing glyphs, weak contrast, and excessive density; regenerate and inspect the changed output. Use text labels alongside color.
Deliver the PDF link, its exact reporting range, and any material coverage limitation. Keep editable JSON beside it for revision. Report a rendering or verification blocker honestly; an HTML/Markdown draft alone is not a completed PDF request.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |