sprint-pretty-html

Objective

Produce ONE self-contained .html file that renders a sprint as an interactive dependency DAG in the dark "mission control" aesthetic (Instrument Serif + IBM Plex Mono, blueprint dot-grid, teal accent). All interactivity (filters, chain tracing, counts) is already implemented in the bundled template — your job is extracting a correct graph model from the raw sprint and filling in the data arrays.

Output

Write sprint-dag-<cycle-or-date>.html (e.g. sprint-dag-c146.html) into the current working directory. assets/template.html is read-only source material — never edit it in place.

Workflow

1. Extract the model from the raw sprint. Whatever the input format, pull out:

• People — every assignee. Also note per-person priority pill counts if present (used to verify your totals later).
• Tickets — title, tracker id (or NEW), priority (P0/P1/P2), owner.
• Explicit dependencies — a "Dependencies" callout, or per-ticket markers like "blocked by X", "→ unblocks Y", "depends on Z". These become SOLID edges.
• Implied links — sequenced phases (days 1–3 → 3–6 → 6–14), API-before-frontend clusters, "feeds into", external blockers ("blocked on design"), mentoring/support. These become DASHED edges, with a short label where it helps ("awaiting design", "sequenced", "supports").
• Prerequisites that are already done — work landed in a previous cycle that this sprint's tickets build on. These become ghost cards in the "Done · External" column, not sprint tickets.