← ClaudeAtlas

sprint-effort-reportlisted

Generate a per-assignee effort summary from a Jira sprint CSV export. Use when the user provides a sprint CSV file (e.g. s144.csv, sprint export) and wants to summarize effort by assignee, see who helped on cross-team subtasks, or understand sprint load distribution. Produces a new markdown report file.
alycd/agent-skills · ★ 0 · Data & Documents · score 56
Install: claude install-skill alycd/agent-skills
# Sprint Effort Report Generates a per-assignee effort breakdown from a Jira sprint CSV and writes a new markdown report file in the same directory as the CSV. ## CSV format Expected columns (order matters): ``` Parent Key, Parent Summary, Key, Type, Summary, Status, Assignee, Impact, Effort, Created, Updated ``` The `Effort` column contains size values: `Small`, `Medium`, `Large`, `Extra-Large` (or blank). ## Rules 1. **Only count items with Status = "Done".** Any other status → excluded from all counts. 2. **Only count items that have an Effort value.** Blank effort → excluded from all counts. 3. **Count all non-Sub-task types** (Story, Task, Feature, Bug, Template, Epic, etc.) for their assigned person. 4. **Sub-tasks**: only count toward the subtask's assignee if that assignee **differs** from the parent story/task's assignee. - To find the parent's assignee: look up the Parent Key in the same CSV and read its Assignee column. - If the parent does not appear as its own row in the CSV, treat it as unknown — count the subtask. 5. **Unassigned** items are always excluded. 6. **Effort buckets**: Extra-Large, Large, Medium, Small (no "no size" bucket — those are dropped). 7. **Effort weights** for the weighted total: Extra-Large = 8, Large = 5, Medium = 3, Small = 1. ## Instructions ### Step 1 — Read the CSV Read the full CSV file. Build two lookup maps: - `row_by_key`: key → full row (for parent lookups) - `assignee_by_key`: key → assignee (for quick parent own