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

sprint-perspectives

Skill4 starsChanged 10 months agoMITView on GitHub

Generate per-sprint perspectives (narrative + cards) by mining git history for documents and files co-updated alongside sprint anchor docs. Use when the user asks for sprint perspectives, evidence linking, research doc discovery, or sprint retrospectives with code-change metrics.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Add window/subgraph receipts (requires Dev Graph API): python skills/sprint-perspectives/scripts/generate_sprint_perspectives.py --sprint …

    line 17
  2. Very specific:

    Put files under: docs/sprints/sprint-11/_dev_graph_visuals/

    line 19

≈ “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 Perspectives

Generate a per-sprint PERSPECTIVES.md plus a card-style HTML/PDF report by:

  1. summarizing sprint anchor docs inside docs/sprints/<sprint>/, and
  2. using git history to discover which other docs/files were co-updated while those sprint docs were edited.

Quickstart

  • Single sprint: python skills/sprint-perspectives/scripts/generate_sprint_perspectives.py --sprint sprint-11 --no-pdf
  • All sprints: python skills/sprint-perspectives/scripts/generate_sprint_perspectives.py --all --no-pdf

Optional Dev Graph (enrichment + visuals)

  • Add window/subgraph receipts (requires Dev Graph API): python skills/sprint-perspectives/scripts/generate_sprint_perspectives.py --sprint sprint-11 --dev-graph-api http://localhost:8080 --no-pdf
  • Embed visuals (drop SVG/PNG into the sprint folder first):
    • Put files under: docs/sprints/sprint-11/_dev_graph_visuals/
    • Then run: python skills/sprint-perspectives/scripts/generate_sprint_perspectives.py --sprint sprint-11 --no-pdf

Outputs (per sprint folder)

  • docs/sprints/<sprint>/PERSPECTIVES.md
  • docs/sprints/<sprint>/_linked_docs.json (docs only)
  • docs/sprints/<sprint>/_cochanged_files.json (all files)
  • docs/sprints/<sprint>/SPRINT_PERSPECTIVES_CARDS.pdf (when weasyprint is installed; otherwise HTML is left next to the intended PDF path)

Notes

  • Works git-first (no Dev Graph required). When provided, --dev-graph-api adds sprint-window receipts and basic subgraph counts.
  • The main protagonist is documentation evidence (.md/.txt/.pdf), but code-change metrics are included as supportive context.

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