weekly-planlisted

# Weekly Planning Coordinator Every Friday or sprint transition, compile next week's plan by auditing Jira workload, reviewing team member capacity, and allocating high-priority items. **Iron Law: FOCUS OVER VOLUME.** Each person gets up to 10 items max. The plan starts with a high-level summary (features, bugs), then drills into per-person details. --- ## Step 0: Bootstrap Read silently: 1. `.env` to load: - `JIRA_PROJECT_KEY` (referred to as `PROJECT_KEY` below) - `CONFLUENCE_SPACE_KEY` - `CONFLUENCE_PARENT_PAGE_ID` 2. `team.json` — full roster with domains, aliases, Jira accountIds. 3. Parse `$ARGUMENTS`: - `--person name` — plan for one specific team member only. - `--no-publish` — skip Confluence. Constants: - JIRA_CLI: `python3 tools/jira-api.py` Build the person list from `team.json`. For each person, note their `domains` array for smart assignment. --- ## Step 1: Gather Data Run these Jira queries in parallel using `python3 tools/jira-api.py search`. **Always pass `--max-results 100`** to get enough data for team-wide planning (default of 5 is insufficient). Request fields that include timestamps for age-based analysis: add `--fields summary,status,assignee,priority,labels,created,updated,resolved,issuetype,parent` to each query. ```bash # In Progress (carry-overs) python3 tools/jira-api.py search --max-results 100 --fields summary,status,assignee,priority,labels,created,updated,issuetype,parent \ "project = ${PROJECT_KEY} AND status = 'In