agentleFS
Sign inStart free
rm2thaddeusrm2thaddeus/Aitor_Skills/sprint-summary-pdf/SKILL.md

sprint-summary-pdf

Skill4 starsChanged 10 months agoMITView on GitHub

Generate per-sprint PDF summaries with a card layout from docs/sprints. Use when the user asks for sprint summaries, sprint recap PDFs, shareable sprint story cards, or to drop PDFs into each sprint folder.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to generate a clean PDF per sprint, saved inside each sprint folder.

    line 8
  2. Very specific:

    All sprints (default): python skills/sprint-summary-pdf/scripts/generate_sprint_summary_pdf.py

    line 11
  3. Distinctive:

    If a sprint is missing a summary file, synthesize a short summary from README and PRD only.

    line 36
  4. Distinctive:

    Use a grid of cards (4 to 6 cards per sprint).

    line 39
  5. Distinctive:

    Keep it readable at a glance.

    line 45
  6. Distinctive:

    Do not depend on running services.

    line 51
  7. Distinctive:

    If user asks for a single sprint, only generate that sprint PDF.

    line 54
  8. Very specific:

    If user asks for all, iterate every sprint folder under docs/sprints/.

    line 55
  9. Distinctive:

    If a sprint folder has no bullet lists, generate a single Summary card using the first paragraph of README/PRD.

    line 63
  10. Distinctive:

    Prefer README for narrative, PRD for goals, and completion summaries for wins and gaps.

    line 64
  11. Distinctive:

    Keep cards concise; trim long bullets and drop low-signal items.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sprint Summary PDF

Use this skill to generate a clean PDF per sprint, saved inside each sprint folder.

Quickstart

  • All sprints (default): python skills/sprint-summary-pdf/scripts/generate_sprint_summary_pdf.py
  • Single sprint: python skills/sprint-summary-pdf/scripts/generate_sprint_summary_pdf.py --sprint sprint-11

Inputs

  • docs/sprints/*/README.md
  • docs/sprints/*/PRD.md
  • docs/sprints/*/*SUMMARY*.md
  • docs/sprints/*/completion-summary*.md
  • docs/sprints/*/mindmap*.md

Output

  • Default filename: SPRINT_SUMMARY_CARDS.pdf
  • Save inside each sprint folder, for example:
    • docs/sprints/sprint-11/SPRINT_SUMMARY_CARDS.pdf

Content extraction

For each sprint folder, extract:

  • Title and sprint name
  • Dates or time window (if present)
  • Goal or theme (from README or PRD)
  • Key wins or delivered features
  • Risks or known gaps
  • Next steps or transition notes
  • Metrics or performance highlights (if present)

If a sprint is missing a summary file, synthesize a short summary from README and PRD only.

Layout and style

  • Use a grid of cards (4 to 6 cards per sprint).
  • Visual tone inspired by the Pixel Detective frontend:
    • dark base, high contrast text
    • cyan or teal accent lines
    • rounded cards, subtle shadows
    • bold section headers
  • Keep it readable at a glance. Each card should be 3 to 6 bullets.
  • Include a small header with sprint name, status, and dates.

PDF generation approach

  • Build a single HTML per sprint with inline CSS.
  • Render to PDF using WeasyPrint when available; otherwise leave HTML for manual export.
  • Do not depend on running services.

Scope control

  • If user asks for a single sprint, only generate that sprint PDF.
  • If user asks for all, iterate every sprint folder under docs/sprints/.

Template and script

  • Template: skills/sprint-summary-pdf/assets/sprint_cards_template.html
  • Script: python skills/sprint-summary-pdf/scripts/generate_sprint_summary_pdf.py (defaults to --all)
  • Single sprint: --sprint sprint-11

Notes

  • If a sprint folder has no bullet lists, generate a single Summary card using the first paragraph of README/PRD.
  • Prefer README for narrative, PRD for goals, and completion summaries for wins and gaps.
  • Keep cards concise; trim long bullets and drop low-signal items.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free