skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/trackers/skills/backlog-triage/examples/northwind-backlog.csv

@@ -0,0 +1,28 @@
+Issue key,Issue Type,Summary,Status,Priority,Assignee,Reporter,Created,Updated,Custom field (Story Points),Labels,Labels,Description
+CHK-101,Story,Guest checkout without creating an account,To Do,Highest,,Priya Nair,02/Jun/26 9:14 AM,10/Jun/26 4:02 PM,13,checkout,growth,"Let shoppers pay without signing up. Biggest drop-off in the funnel is the forced sign-up step."
+CHK-102,Story,Save card for future purchases,In Progress,High,Tom Okafor,Priya Nair,05/Jun/26 11:20 AM,28/Sep/26 2:45 PM,5,checkout,payments,"Acceptance criteria:
+- Given a signed-in shopper, when they tick Save card, then the card token is stored with the PSP
+- The full card number is never stored by us"
+CHK-103,Bug,Apple Pay button missing on Safari 17,To Do,High,Lena Fischer,Support,12/Aug/26 8:01 AM,25/Sep/26 10:30 AM,3,checkout,bug,"Reported by 14 customers. Given Safari 17 on macOS, when the shopper reaches payment, then the Apple Pay button shows."
+CHK-104,Story,Allow guest checkout without an account,Backlog,Medium,,Marco Rossi,19/Jul/26 3:30 PM,19/Jul/26 3:30 PM,8,checkout,,"Shoppers should be able to check out as a guest."
+CHK-105,Story,Show delivery date estimate on the cart page,To Do,Medium,Lena Fischer,Priya Nair,01/Sep/26 9:00 AM,29/Sep/26 9:15 AM,3,cart,,"Acceptance criteria:
+- Given an item with stock in the nearest warehouse, then the cart shows Arrives by <date>
+- Given no stock, then the line says Ships in 5-7 days"
+CHK-106,Story,Rebuild the payments service on the new platform,Backlog,High,Tom Okafor,Tom Okafor,14/Mar/26 10:00 AM,02/Apr/26 1:10 PM,21,payments,tech-debt,"Move everything off the legacy payments monolith."
+CHK-107,Task,Update PCI self-assessment questionnaire,To Do,Highest,Aisha Bello,Compliance,03/Sep/26 9:30 AM,30/Sep/26 8:40 AM,2,compliance,,"Definition of done: SAQ-A submitted to the acquirer before 31 Oct."
+CHK-108,Story,Promo code field on checkout,Done,Medium,Lena Fischer,Marco Rossi,10/May/26 2:00 PM,20/Jun/26 5:00 PM,3,checkout,,"Acceptance criteria:
+- Given a valid code, then the discount line appears"
+CHK-109,Bug,Apple Pay button not showing in Safari,Backlog,Medium,,Support,26/Aug/26 4:12 PM,26/Aug/26 4:12 PM,,checkout,bug,"Customer says the Apple Pay option is gone on their Mac."
+CHK-110,Story,Address autocomplete for UK postcodes,To Do,Low,Marco Rossi,Marco Rossi,22/Apr/26 11:00 AM,30/Apr/26 3:00 PM,5,checkout,,"Use a postcode lookup so shoppers don't type the full address."
+CHK-111,Story,Split shipment tracking emails,Backlog,Medium,,Priya Nair,08/Jan/26 9:00 AM,15/Feb/26 10:00 AM,8,notifications,,"One email per parcel when an order ships in more than one box."
+CHK-112,Story,One-click reorder from order history,To Do,High,Aisha Bello,Priya Nair,15/Sep/26 1:30 PM,27/Sep/26 11:00 AM,5,growth,,"Acceptance criteria:
+- Given a past order, when the shopper taps Reorder, then all in-stock items are added to the cart"
+CHK-113,Task,Add fraud score to order admin view,In Progress,Highest,Tom Okafor,Ops,10/Sep/26 10:00 AM,30/Sep/26 6:00 PM,3,payments,ops,"- [ ] Score shown next to order total
+- [ ] Orders above 80 highlighted"
+CHK-114,Story,Klarna pay-later option,Backlog,Highest,,Marco Rossi,20/Aug/26 2:00 PM,22/Aug/26 9:00 AM,13,payments,growth,"Partner deal signed. Add Klarna as a payment method."
+CHK-115,Story,Gift message at checkout,Backlog,Lowest,,Priya Nair,11/Nov/25 3:00 PM,11/Nov/25 3:00 PM,2,checkout,,"Let shoppers add a gift message."
+CHK-116,Story,Persist cart across devices for signed-in users,To Do,Medium,Lena Fischer,Priya Nair,04/Sep/26 9:00 AM,24/Sep/26 4:00 PM,5,cart,,"Given a signed-in shopper adds an item on mobile, when they open the site on desktop, then the item is in the cart."
+CHK-117,Story,Persist the cart across devices for logged-in shoppers,Backlog,Low,,Marco Rossi,18/Jun/26 10:00 AM,18/Jun/26 10:00 AM,,cart,,"Cart should follow the user."
+CHK-118,Bug,Order confirmation email sent twice,Closed,High,Tom Okafor,Support,01/Jul/26 9:00 AM,03/Jul/26 9:00 AM,2,notifications,bug,"Fixed by idempotency key on the send job."
+CHK-119,Story,Accessibility fixes on the payment form,To Do,High,,Aisha Bello,21/Sep/26 9:00 AM,21/Sep/26 9:00 AM,5,checkout,a11y,"Screen readers skip the card expiry field. Labels missing on CVV."
+CHK-120,Story,Checkout analytics dashboard,Backlog,Highest,Marco Rossi,Priya Nair,05/May/26 11:00 AM,12/May/26 2:00 PM,8,analytics,,"We need to see the funnel."

skilldrop_cli/data/packs/trackers/skills/backlog-triage/examples/northwind-checkout-triage.md

@@ -0,0 +1,202 @@
+# Example: triaging the Northwind checkout backlog
+
+The user exported the Northwind checkout team's Jira backlog to CSV and asked: "Triage this
+before Thursday's refinement. Who's missing, what's a duplicate, what should we pull next?"
+The export is [`northwind-backlog.csv`](northwind-backlog.csv): 20 issues, Jira's default CSV
+columns, dates in Jira's `02/Jun/26 9:14 AM` format.
+
+## Step 1: run the script
+
+```bash
+python3 scripts/triage_backlog.py examples/northwind-backlog.csv --as-of 2026-10-01 \
+  -o triage.md --changes changes.csv
+```
+
+## Step 2: the script's output, unedited
+
+`triage.md`:
+
+```markdown
+# Backlog triage findings: northwind-backlog.csv
+
+As of 2026-10-01 · 20 items in export · 18 open · 2 done or closed (skipped)
+Thresholds: stale > 30 days · similarity >= 0.75 · oversized estimate > 8
+
+Columns used: key='Issue key', title='Summary', description='Description', status='Status', owner='Assignee', priority='Priority', estimate='Custom field (Story Points)', created='Created', updated='Updated', labels='Labels'
+
+| Check | Count |
+|---|---:|
+| Duplicate candidate pairs | 3 |
+| No owner | 8 |
+| No acceptance criteria | 11 |
+| Stale (> 30 days) | 10 |
+| Oversized | 3 |
+| Priority conflicts | 11 |
+
+## Duplicate candidates
+
+| Pair | Score | Titles | Shared words |
+|---|---:|---|---|
+| CHK-116 / CHK-117 | 0.87 | Persist cart across devices for signed-in users / Persist the cart across devices for logged-in shoppers | across cart devices persist |
+| CHK-103 / CHK-109 | 0.86 | Apple Pay button missing on Safari 17 / Apple Pay button not showing in Safari | apple button pay safari |
+| CHK-101 / CHK-104 | 0.80 | Guest checkout without creating an account / Allow guest checkout without an account | account checkout guest without |
+
+Title similarity only. Read both descriptions before merging.
+
+## No owner
+
+| Key | Title | Status | Priority | Last update |
+|---|---|---|---|---|
+| CHK-101 | Guest checkout without creating an account | To Do | Highest | 2026-06-10 |
+| CHK-104 | Allow guest checkout without an account | Backlog | Medium | 2026-07-19 |
+| CHK-109 | Apple Pay button not showing in Safari | Backlog | Medium | 2026-08-26 |
+| CHK-111 | Split shipment tracking emails | Backlog | Medium | 2026-02-15 |
+| CHK-114 | Klarna pay-later option | Backlog | Highest | 2026-08-22 |
+| CHK-115 | Gift message at checkout | Backlog | Lowest | 2025-11-11 |
+| CHK-117 | Persist the cart across devices for logged-in shoppers | Backlog | Low | 2026-06-18 |
+| CHK-119 | Accessibility fixes on the payment form | To Do | High | 2026-09-21 |
+
+## No acceptance criteria
+
+| Key | Title | Status | Priority | Owner |
+|---|---|---|---|---|
+| CHK-101 | Guest checkout without creating an account | To Do | Highest | - |
+| CHK-104 | Allow guest checkout without an account | Backlog | Medium | - |
+| CHK-106 | Rebuild the payments service on the new platform | Backlog | High | Tom Okafor |
+| CHK-109 | Apple Pay button not showing in Safari | Backlog | Medium | - |
+| CHK-110 | Address autocomplete for UK postcodes | To Do | Low | Marco Rossi |
+| CHK-111 | Split shipment tracking emails | Backlog | Medium | - |
+| CHK-114 | Klarna pay-later option | Backlog | Highest | - |
+| CHK-115 | Gift message at checkout | Backlog | Lowest | - |
+| CHK-117 | Persist the cart across devices for logged-in shoppers | Backlog | Low | - |
+| CHK-119 | Accessibility fixes on the payment form | To Do | High | - |
+| CHK-120 | Checkout analytics dashboard | Backlog | Highest | Marco Rossi |
+
+## Stale (no update in more than 30 days)
+
+| Key | Title | Status | Priority | Days since update |
+|---|---|---|---|---|
+| CHK-115 | Gift message at checkout | Backlog | Lowest | 324 |
+| CHK-111 | Split shipment tracking emails | Backlog | Medium | 228 |
+| CHK-106 | Rebuild the payments service on the new platform | Backlog | High | 182 |
+| CHK-110 | Address autocomplete for UK postcodes | To Do | Low | 154 |
+| CHK-120 | Checkout analytics dashboard | Backlog | Highest | 142 |
+| CHK-101 | Guest checkout without creating an account | To Do | Highest | 113 |
+| CHK-117 | Persist the cart across devices for logged-in shoppers | Backlog | Low | 105 |
+| CHK-104 | Allow guest checkout without an account | Backlog | Medium | 74 |
+| CHK-114 | Klarna pay-later option | Backlog | Highest | 40 |
+| CHK-109 | Apple Pay button not showing in Safari | Backlog | Medium | 36 |
+
+## Oversized (split before scheduling)
+
+| Key | Title | Status | Priority | Why |
+|---|---|---|---|---|
+| CHK-101 | Guest checkout without creating an account | To Do | Highest | estimate 13 > 8 |
+| CHK-106 | Rebuild the payments service on the new platform | Backlog | High | estimate 21 > 8 |
+| CHK-114 | Klarna pay-later option | Backlog | Highest | estimate 13 > 8 |
+
+## Priority conflicts
+
+- Priority inflation: 5 of 18 prioritised open items (28%) are at the top priority.
+- CHK-101 (Guest checkout without creating an account): priority Highest but no owner
+- CHK-101 (Guest checkout without creating an account): priority Highest but no update in 113 days
+- CHK-106 (Rebuild the payments service on the new platform): priority High but no update in 182 days
+- CHK-114 (Klarna pay-later option): priority Highest but no owner
+- CHK-114 (Klarna pay-later option): priority Highest but no update in 40 days
+- CHK-119 (Accessibility fixes on the payment form): priority High but no owner
+- CHK-120 (Checkout analytics dashboard): priority Highest but no update in 142 days
+- CHK-116 (Persist cart across devices for signed-in users): likely duplicate of CHK-117 but priority Medium vs Low
+- CHK-103 (Apple Pay button missing on Safari 17): likely duplicate of CHK-109 but priority High vs Medium
+- CHK-101 (Guest checkout without creating an account): likely duplicate of CHK-104 but priority Highest vs Medium
+
+## Priority distribution (open items)
+
+| Priority | Open items |
+|---|---:|
+| Highest | 5 |
+| High | 5 |
+| Medium | 5 |
+| Low | 2 |
+| Lowest | 1 |
+
+```
+
+`changes.csv` (first 6 of 35 rows):
+
+```csv
+key,action,field,proposed_value,reason
+CHK-117,confirm-duplicate,status,Duplicate of CHK-116,title similarity 0.87 with CHK-116
+CHK-109,confirm-duplicate,status,Duplicate of CHK-103,title similarity 0.86 with CHK-103
+CHK-104,confirm-duplicate,status,Duplicate of CHK-101,title similarity 0.80 with CHK-101
+CHK-101,assign-owner,assignee,,open item with no owner
+CHK-104,assign-owner,assignee,,open item with no owner
+CHK-109,assign-owner,assignee,,open item with no owner
+```
+
+## Step 3: the triage, after reading the descriptions
+
+Every count below comes from the script output above. The duplicate verdicts, the priority
+proposals and the ordering are judgment, and each one gives its reason.
+
+```markdown
+# Backlog triage: Northwind checkout, as of 2026-10-01
+
+18 open items. 3 duplicate pairs, 8 with no owner, 11 with no acceptance criteria,
+10 stale (over 30 days), 3 oversized. 5 of 18 open items (28%) are at Highest.
+
+## Duplicates (confirmed by reading both descriptions)
+
+| Keep | Close | Why they're the same | Why this one survives |
+|---|---|---|---|
+| CHK-116 | CHK-117 | Both ask for the cart to follow a signed-in shopper across devices | CHK-116 has an owner, acceptance criteria and an update 7 days ago; CHK-117 has none of these |
+| CHK-103 | CHK-109 | Same symptom: the Apple Pay button doesn't show in Safari | CHK-103 names the version (Safari 17), the report count (14) and acceptance criteria. Copy CHK-109's customer note into CHK-103 as a comment |
+| CHK-101 | CHK-104 | Both ask for guest checkout without an account | CHK-101 states the reason (the forced sign-up step is the biggest funnel drop-off). Carry CHK-104's reporter over as a watcher |
+
+## Proposed ordering (open, not yet started)
+
+| # | Key | Title | Why here | Ready to pull? |
+|---|---|---|---|---|
+| 1 | CHK-107 | Update PCI self-assessment questionnaire | Fixed external date: submit before 31 Oct. Owned, 2 points, definition of done present | Yes |
+| 2 | CHK-103 | Apple Pay button missing on Safari 17 | 14 customer reports; blocks a payment method. Owned, 3 points | Yes |
+| 3 | CHK-119 | Accessibility fixes on the payment form | Screen readers skip a payment field, so some shoppers can't pay | No: needs an owner and acceptance criteria |
+| 4 | CHK-112 | One-click reorder from order history | High, owned, acceptance criteria, 5 points | Yes |
+| 5 | CHK-101 | Guest checkout without creating an account | Highest value claim in the backlog, but 13 points, unowned, 113 days without an update | No: split first, then assign |
+| 6 | CHK-105 | Show delivery date estimate on the cart page | Medium, owned, acceptance criteria, 3 points | Yes |
+| 7 | CHK-116 | Persist cart across devices for signed-in users | Medium, owned, acceptance criteria, 5 points | Yes |
+
+In progress and left where they are: CHK-102, CHK-113.
+
+## Priority conflicts to resolve
+
+- **Five items at Highest (28% of the backlog).** CHK-120 (analytics dashboard) has had no update
+  in 142 days and has no acceptance criteria. Proposal: drop it to Medium unless someone owns a
+  date for it.
+- **CHK-114 Klarna is Highest but unowned, 13 points, no acceptance criteria.** The description
+  says a partner deal is signed. Ask whether the deal carries a launch date; if it does, it
+  moves above CHK-112 once split.
+- **CHK-106 payments rebuild is High, 21 points, 182 days untouched.** Keep High only if the
+  team can name the first slice; otherwise move it to Low and revisit at planning.
+
+## Change list
+
+| Key | Change | Reason |
+|---|---|---|
+| CHK-117 | Close as duplicate of CHK-116 | Same request, see above |
+| CHK-109 | Close as duplicate of CHK-103; copy customer note | Same symptom |
+| CHK-104 | Close as duplicate of CHK-101 | Same story |
+| CHK-101, CHK-114, CHK-106 | Split with `user-story-splitter` | Estimates 13, 13, 21 (limit 8) |
+| CHK-101, CHK-114, CHK-119, CHK-111 | Assign an owner | Open with no assignee |
+| CHK-119, CHK-110, CHK-120 | Add acceptance criteria | None found |
+| CHK-120 | Priority Highest → Medium (proposal) | Stale 142 days, no criteria |
+| CHK-115 | Close: won't do | Lowest, no owner, 324 days without an update |
+| CHK-111, CHK-110 | Ask the reporter to confirm or close | 228 and 154 days without an update |
+
+## Questions before applying
+
+1. Who owns CHK-101, CHK-114 and CHK-119?
+2. Does the Klarna deal (CHK-114) have a launch date?
+3. Is CHK-120 still Highest, and for whom?
+```
+
+What the triage did *not* do: it didn't change any priority on its own, and it didn't
+invent an owner or a date. Each of those is a question in the last section.

skilldrop_cli/data/packs/trackers/skills/backlog-triage/manifest.json

@@ -0,0 +1,42 @@
+{
+  "name": "backlog-triage",
+  "version": "0.1.1",
+  "description": "Triage a whole backlog export from Jira, Linear or GitHub Projects (CSV, JSON or an MCP tool) — duplicate and near-duplicate pairs with the reason, items missing acceptance criteria or an owner, stale items, oversized items to split, priority conflicts, and a proposed ordering with a reason per item — ending in a change list the user can apply. A stdlib script computes the mechanical checks. Use when the user wants to clean up, groom or refine a backlog, find duplicate tickets, or says \"triage our backlog\", \"what should we pull next?\".",
+  "entrypoint": "SKILL.md",
+  "deps": {
+    "npm": [],
+    "pip": []
+  },
+  "env": {
+    "required": [],
+    "optional": []
+  },
+  "related": [
+    "bug-triage",
+    "team-status-report",
+    "tracker-brief-sync",
+    "user-story-splitter"
+  ],
+  "handoff": [
+    {
+      "to": "user-story-splitter",
+      "when": "an item is over the size limit or too vague to estimate",
+      "purpose": "Split it into independently shippable stories with acceptance criteria before it is scheduled.",
+      "fallback": "If user-story-splitter is absent, list the item as 'split before scheduling' in the change list with the estimate that triggered it."
+    }
+  ],
+  "tags": [
+    "backlog",
+    "triage",
+    "jira",
+    "linear",
+    "github-projects",
+    "refinement",
+    "duplicates"
+  ],
+  "permissions": {"network": [], "commands": [], "files": "named-paths"},
+  "model": {
+    "tier": "standard",
+    "rationale": "A script does the counting; the model confirms duplicates by reading, judges readiness and writes a reasoned ordering. Bounded judgment over structured data."
+  }
+}

skilldrop_cli/data/packs/trackers/skills/backlog-triage/reference.md

@@ -0,0 +1,106 @@
+# backlog-triage reference
+
+## Getting the export
+
+The script reads CSV, TSV, JSON or JSONL. Pick whichever your tracker gives you most easily.
+
+| Tracker | Export route | Notes |
+|---|---|---|
+| Jira | Issue search (filter the backlog with JQL, e.g. `project = CHK AND statusCategory != Done`) → Export → CSV (all fields) | Repeated columns such as `Labels, Labels` are joined. Story points usually appear as `Custom field (Story Points)` |
+| Linear | Workspace settings → import/export → export CSV, or copy issues through the Linear MCP | Numeric priority 0–4 is understood (1 = Urgent … 4 = Low, 0 = none) |
+| GitHub Issues | `gh issue list --state open --limit 500 --json number,title,body,state,assignees,labels,createdAt,updatedAt > issues.json` | Gives dates, so staleness works. No priority or estimate unless you use labels |
+| GitHub Projects | `gh project item-list <number> --owner <org> --format json > items.json`, or the view's export to CSV if your view offers it | Custom fields (Status, Priority, Size) come through by name. Item lists may not carry an updated date; join with `gh issue list` if you need staleness |
+| Any tracker via MCP | Ask the agent to fetch the open issues with the tracker's MCP tool and save the result as JSON | Objects nested under `fields` (Jira REST) or `content` (GitHub Projects) are flattened |
+
+## Field mapping
+
+The script looks for these column names, case-insensitively, and uses the first it finds.
+Override any of them with `--map field="Your Column"`.
+
+| Field | Jira CSV | Linear | GitHub Issues / Projects | Used for |
+|---|---|---|---|---|
+| key | Issue key | ID / identifier | number | Naming items in findings |
+| title | Summary | Title | title | Duplicate detection (required) |
+| description | Description | Description | body | Acceptance-criteria check |
+| acceptance | Custom field (Acceptance Criteria) | (none) | (none) | Acceptance-criteria check, if your Jira has the field |
+| status | Status | Status / state | state / Status | Skipping done items |
+| owner | Assignee | Assignee | assignees | No-owner check |
+| priority | Priority | Priority | Priority (Projects field) or labels | Priority conflicts |
+| estimate | Custom field (Story Points), Story point estimate | Estimate | Size / Estimate (Projects field) | Oversized check |
+| created | Created | Created / createdAt | createdAt | Fallback when there's no updated date |
+| updated | Updated | Updated / updatedAt | updatedAt | Staleness |
+| resolved | Resolved | Completed / completedAt | closedAt | Skipping done items |
+| labels | Labels | Labels | labels | Shown in context |
+
+A missing column turns its check off, and the report says which checks were skipped. A
+missing title column stops the run.
+
+## How each check works
+
+| Check | Rule | Default |
+|---|---|---|
+| Open | Status not in the done set (Done, Closed, Resolved, Completed, Canceled, Duplicate, Won't Do, Released, Shipped) and no resolved date | — |
+| Duplicate candidate | `difflib.SequenceMatcher` ratio on titles, lower-cased, punctuation and common stopwords removed | `--similarity 0.75` |
+| No owner | Owner empty, "Unassigned" or "None" | — |
+| No acceptance criteria | Description has none of: "acceptance criteria", "definition of done", "AC:", a Given/When/Then line, a `- [ ]` checklist; and the acceptance column (if any) is empty | — |
+| Stale | Days from last update (or created, if no update) to `--as-of` | `--stale-days 30` |
+| Oversized | Numeric estimate above the limit, or size XL / XXL | `--max-estimate 8` |
+| Priority conflict | Top-two priority but unowned or stale; a duplicate pair at different priorities; more than the threshold share of open items at the top priority | `--inflation-pct 25` |
+
+### Priority ranks
+
+| Rank | Values recognised |
+|---|---|
+| 0 (top) | Highest, Blocker, Urgent, Critical, P0, Linear `1` |
+| 1 | High, Major, P1, Linear `2` |
+| 2 | Medium, Normal, P2, Linear `3` |
+| 3 | Low, Minor, P3, Linear `4` |
+| 4 | Lowest, Trivial, P4 |
+| none | No priority, None, Linear `0` |
+
+Anything else is listed as "not recognised" and left unranked. Tell the user, and map it
+yourself when you write the ordering.
+
+## Limits of the mechanical checks
+
+- **Title similarity misses reworded duplicates** ("Pay later with Klarna" vs "BNPL option") and
+  flags look-alikes that differ ("Export invoices as PDF" vs "Import invoices from PDF"). Read
+  both descriptions before calling a pair a duplicate. Look for reworded duplicates yourself
+  among items with the same label or component.
+- **The acceptance-criteria check is a text search.** "We need AC" matches nothing; "AC: TBD"
+  matches but is empty. Spot-check the items you're about to put at the top.
+- **Staleness measures tracker activity, not relevance.** A Lowest item untouched for a year is a
+  close candidate; a High item untouched for a year is a priority question.
+- **Pair-wise comparison is O(n²).** Up to a few thousand items is fine. For larger exports,
+  filter to one project or component first.
+
+## Ordering method
+
+Order open, not-started items by these, in turn. State which one placed each item.
+
+1. **A fixed external date** (regulator, contract, event). Ask for the date if the description
+   only hints at one; never assume it.
+2. **Users currently harmed** (a bug with reports, a payment or access failure), more if the
+   description gives a count.
+3. **Ready to pull:** owner, acceptance criteria, and size within the limit. An item that isn't
+   ready can't be first, however valuable. Put its readiness work at the top instead.
+4. **Stated value over size.** Use the value the item itself claims; don't invent a business case.
+5. **Everything else** keeps its current relative order.
+
+In-progress items are not reordered. Report them separately.
+
+## Change list format
+
+The `--changes` CSV has `key, action, field, proposed_value, reason`. Actions:
+
+| action | What applying it means |
+|---|---|
+| confirm-duplicate | Read both; close the weaker one as a duplicate and link it to the survivor |
+| assign-owner | Set the assignee (the user names who) |
+| add-acceptance-criteria | Write criteria, or hand to `user-story-splitter` if the item is also large |
+| confirm-or-close | Ask the reporter whether it's still wanted; close if no answer by a date |
+| split | Hand to `user-story-splitter` before it's scheduled |
+
+The script's list is mechanical. The final change list you give the user removes rows your
+judgment overrode (for example, both items of a pair you decided aren't duplicates) and adds the
+priority changes you proposed.