progress-report

You can auto-generate stakeholder-ready Quarto progress reports by collecting git commits, R targets status, and iteration logs into a reports/YYYYMMDD.qmd file. This assembles project state into formatted prose and gt tables without manual formatting.

Summarize codebook iterations and LLM evaluation metrics by reading prompts/iterations/*.yml logs and previous reports. The process maps internal jargon to reader-facing language, creating accessible executive summaries for monthly milestone reporting.

Generating a Quarto progress report writes the reports/YYYYMMDD.qmd file without auto-rendering. You must manually render the Quarto document afterward to produce the final output, ensuring you can review the generated prose and gt tables first.

You can use this reporting workflow to track pipeline targets for briefing preparation by reading R targets status and setup chunks. It extracts only required targets to summarize changes, producing stage-gate reports and briefing notes for external stakeholders or funders.

Include git commit history and previous reports in a stakeholder progress update by auto-gathering commits since the last report and reading the most recent existing report. This summarizes what changed into jargon-free prose with consistent shorthand.

You need gt tables and Quarto conventions to format stakeholder progress reports because the generated reports/YYYYMMDD.qmd file uses minimal front matter and gt tables following project styling rules. This ensures outputs are compliant and readable for stakeholders.