skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/stakeholder-comms/skills/guide-builder/templates/api-reference.md

@@ -0,0 +1,120 @@
+# {API / event stream name} — Developer reference
+
+**Base URL:** `{https://api.example.com/v1}`
+**Auth:** {e.g. "Bearer token in `Authorization` header; obtain via …"}
+**Versioning:** {e.g. "URL-path `/v1`; breaking changes ship a new path. See Changelog."}
+**Content type:** `application/json` unless stated.
+
+## Conventions
+
+These apply to every endpoint/event below — read once, don't repeat per item.
+
+- **Errors** return this shape:
+  ```json
+  { "error": { "code": "string", "message": "human-readable", "details": {} } }
+  ```
+- **Pagination:** {e.g. "cursor-based: pass `?cursor=`; response includes `next_cursor` (null on last page)"}
+- **Idempotency:** {e.g. "mutating calls accept an `Idempotency-Key` header; replays within 24h return the original result"}
+- **Rate limits:** {e.g. "600 req/min/token; `429` with `Retry-After` when exceeded"}
+- **Timestamps:** ISO 8601 UTC (`2026-05-26T14:30:00Z`).
+
+---
+
+## Endpoints
+
+### `{METHOD} /{path}` — {one-line purpose}
+
+{One sentence on when a consumer calls this.}
+
+**Auth:** {required scope/role, or "none"}
+
+**Path / query params**
+
+| Param | In | Type | Required | Description |
+|---|---|---|---|---|
+| `{id}` | path | string | yes | {…} |
+| `{limit}` | query | integer | no | {default, max} |
+
+**Request body**
+
+| Field | Type | Required | Description |
+|---|---|---|---|
+| `{field}` | string | yes | {…} |
+| `{field}` | integer | no | {default} |
+
+```json
+{ "field": "value", "field2": 42 }
+```
+
+**Response `200`**
+
+| Field | Type | Description |
+|---|---|---|
+| `{id}` | string | {…} |
+| `{status}` | enum(`a`,`b`) | {…} |
+
+```json
+{ "id": "abc_123", "status": "a", "created_at": "2026-05-26T14:30:00Z" }
+```
+
+**Errors**
+
+| Status | `error.code` | When |
+|---|---|---|
+| `400` | `invalid_request` | {…} |
+| `404` | `not_found` | {…} |
+| `409` | `conflict` | {…} |
+
+```json
+{ "error": { "code": "not_found", "message": "No resource with id abc_123" } }
+```
+
+---
+
+## Events / messages
+
+For each event a consumer subscribes to.
+
+### `{event.name}` — {one-line: what happened}
+
+- **Emitted when:** {the trigger}
+- **Transport:** {e.g. "Kafka topic `orders.v1`" / "webhook POST to your callback URL" / "SNS topic ARN …"}
+- **Delivery:** {e.g. "at-least-once; consumers MUST be idempotent on `event_id`"}
+- **Ordering:** {e.g. "ordered per `partition_key = order_id`; no global order"}
+
+**Payload**
+
+| Field | Type | Required | Description |
+|---|---|---|---|
+| `event_id` | string (uuid) | yes | dedup key |
+| `occurred_at` | string (ISO 8601) | yes | when the fact happened (not when delivered) |
+| `data.{field}` | string | yes | {…} |
+
+```json
+{
+  "event_id": "evt_01HX...",
+  "type": "{event.name}",
+  "occurred_at": "2026-05-26T14:30:00Z",
+  "data": { "order_id": "ord_123", "amount_cents": 4999 }
+}
+```
+
+**Consumer notes:** {what a subscriber must handle — out-of-order arrival, schema evolution, poison messages}
+
+---
+
+## Error code catalog
+
+| `error.code` | Meaning | Consumer action |
+|---|---|---|
+| `invalid_request` | malformed input | fix and retry; don't blind-retry |
+| `rate_limited` | over quota | back off per `Retry-After` |
+| `conflict` | idempotency or state clash | inspect existing resource |
+| {…} | … | … |
+
+## Changelog
+
+| Version / date | Change | Breaking? |
+|---|---|---|
+| `v1` — {YYYY-MM-DD} | initial | — |
+| {…} | … | yes/no |

skilldrop_cli/data/packs/stakeholder-comms/skills/guide-builder/templates/design-walkthrough.md

@@ -0,0 +1,72 @@
+# {System / feature} — How it works
+
+**Who this is for:** {e.g. "an engineer joining the payments team" / "an adjacent team integrating with us"}
+**After reading, you'll be able to:** {concrete capability — "trace a checkout request end-to-end and know which service owns each step"}
+**Status:** describes the system as built on {YYYY-MM-DD}. For *why we chose this design*, see {link to ADRs / design-doc}.
+
+## The mental model
+
+{One paragraph or one diagram. The single idea a reader must hold to understand everything below — e.g. "Every write goes through the command bus; reads come straight from a denormalized view. Nothing reads the write tables directly."}
+
+```
+{Optional ASCII or Mermaid sketch — or link to an architecture-diagrams output. Keep it to the load-bearing boxes and arrows, not every box.}
+```
+
+## Components
+
+What each piece does and why it exists — not how to deploy it.
+
+| Component | Responsibility | Why it's separate |
+|---|---|---|
+| {name} | {one line — what it owns} | {what would break if it were merged into its neighbour} |
+| {…} | … | … |
+
+## How a {request / event / job} flows through
+
+Trace one representative path step by step. This is the heart of the walkthrough.
+
+1. **{Entry point}** — {what happens, which component, what data} → `{file or module:fn}`
+2. **{Next hop}** — {…} → `{file:fn}`
+3. **{…}** — {…}
+4. **{Result}** — {what the caller gets back / what side effect lands}
+
+> Trace it yourself: {how to watch this flow live — a log query, a trace ID, a debug endpoint}.
+
+## Key design decisions (and why)
+
+The non-obvious choices a reader will otherwise undo by accident.
+
+- **{Decision}** — {why; what was rejected}. {Link to the ADR if one exists.}
+- **{Decision}** — {…}
+
+## Data & state
+
+- **Source of truth:** {where the canonical data lives}
+- **Derived / cached:** {what's a projection of it, and how it's kept in sync}
+- **What's NOT persisted:** {e.g. "session state is in memory; a restart drops it — by design"}
+
+## Where the code lives
+
+| Concern | Path | Notes |
+|---|---|---|
+| {entry points / routes} | `{path}` | {…} |
+| {core logic} | `{path}` | start here when reading |
+| {data layer} | `{path}` | … |
+| {tests worth reading first} | `{path}` | the integration tests document the contract |
+
+## Making common changes
+
+How to do the things a new contributor will need in week one.
+
+- **Add a {new endpoint / event / field}:** {the 2–4 places to touch, in order}
+- **Change {common thing}:** {…}
+
+## Gotchas / sharp edges
+
+- ⚠️ {Non-obvious constraint that will bite — "the queue is at-least-once; handlers must be idempotent"}
+- ⚠️ {…}
+
+## Glossary
+
+- **{Term}** — {definition in this system's context, not the generic one}
+- **{Term}** — {…}

skilldrop_cli/data/packs/stakeholder-comms/skills/guide-builder/templates/setup-guide.md

@@ -0,0 +1,109 @@
+# {Project / component} — Setup guide
+
+**Goal:** {one sentence — the end state, e.g. "Run the API locally with a seeded database and answer a request on `localhost:3000`."}
+**Time:** ~{N} minutes
+**You'll have at the end:** {concrete artifact — "a running server, a seeded DB, and a passing health check"}
+
+## Placeholders used in this guide
+
+Replace these everywhere they appear. Nothing else is a placeholder.
+
+| Placeholder | What to put | Where to get it |
+|---|---|---|
+| `<YOUR_API_KEY>` | {what it is} | {where to obtain it} |
+| `<DB_PASSWORD>` | {what it is} | {…} |
+
+## Prerequisites
+
+Check each before starting — a failed setup is almost always a missing prerequisite.
+
+| Need | Version | Check it | If missing |
+|---|---|---|---|
+| {Node / Python / Docker / …} | `>= {x.y}` | `node --version` | {install link / command} |
+| {…} | … | `…` | … |
+
+## Steps
+
+### 1. {Imperative — e.g. "Clone the repo and enter it"}
+
+```bash
+git clone {repo-url} && cd {repo-dir}
+```
+
+**You should see:** {what success looks like — e.g. "a `package.json` in the directory: `ls package.json`"}
+
+### 2. {Imperative — e.g. "Install dependencies"}
+
+```bash
+{exact command — e.g. `npm ci`}
+```
+
+**You should see:** {e.g. "`added 412 packages` with no errors"}
+
+### 3. {Imperative — e.g. "Configure environment"}
+
+```bash
+cp .env.example .env
+# then set:
+#   API_KEY=<YOUR_API_KEY>
+#   DB_PASSWORD=<DB_PASSWORD>
+```
+
+**You should see:** {e.g. "`.env` exists and has no remaining `<…>` placeholders: `grep '<' .env` returns nothing"}
+
+### 4. {Imperative — e.g. "Start dependencies"}
+
+```bash
+{e.g. `docker compose up -d postgres`}
+```
+
+**You should see:** {e.g. "`docker compose ps` shows postgres as `healthy`"}
+
+### 5. {Imperative — e.g. "Run migrations and seed"}
+
+```bash
+{e.g. `npm run db:migrate && npm run db:seed`}
+```
+
+**You should see:** {e.g. "`Migrations complete (3 applied)` and `Seeded 12 rows`"}
+
+### 6. {Imperative — e.g. "Start the service"}
+
+```bash
+{e.g. `npm run dev`}
+```
+
+**You should see:** {e.g. "`Listening on http://localhost:3000`"}
+
+## Verify it works
+
+One end-to-end check that proves the whole setup, not just the last step.
+
+```bash
+{e.g. `curl -s localhost:3000/health`}
+```
+
+**Expected:** {e.g. `{"status":"ok","db":"connected"}`}
+
+If you get this, you're done.
+
+## Troubleshooting
+
+| Symptom | Likely cause | Fix |
+|---|---|---|
+| {exact error text} | {what's actually wrong} | {command or step to fix} |
+| `ECONNREFUSED ...:5432` | Postgres not up yet | Re-run step 4; wait for `healthy` |
+| {…} | … | … |
+
+## Teardown
+
+```bash
+{e.g. `docker compose down -v`}
+```
+
+Removes {what — "containers and the local volume; your `.env` is left intact"}.
+
+## Next steps
+
+- {Where to go now — "Run the test suite: `npm test`"}
+- {Link to the design walkthrough or API reference for this project, if one exists}

skilldrop_cli/data/packs/trackers/pack.json

@@ -0,0 +1,61 @@
+{
+  "description": "For leads and PMs who run work in Jira, Linear or GitHub Projects: load a PRD into the tracker, triage the backlog, write the weekly status report, and check the tracker still matches the doc, all from an export or an MCP tool, with the numbers computed rather than estimated.",
+  "display_name": "Trackers",
+  "keywords": ["jira", "linear", "github-projects", "backlog", "status-report", "triage", "prd"],
+  "links": {
+    "documentation": "https://sananthanarayan.github.io/skilldrop/packs/trackers/"
+  },
+  "maintainers": [
+    {
+      "name": "sananthanarayan"
+    }
+  ],
+  "first-value": {
+    "audience-posture": "non-technical",
+    "prerequisites": [
+      "A CSV or JSON export of your backlog from Jira, Linear or GitHub, or a tracker MCP tool installed",
+      "Python 3.9 or later, for the counting scripts"
+    ],
+    "starter-task": "Triage your backlog before the next refinement session",
+    "starter-prompt": "Here's our backlog exported from Jira: ./backlog.csv. Refinement is Thursday. Find the duplicates, tell me what isn't ready to pull and why, and propose an order for what we take next. Anything without an update in 30 days counts as stale.",
+    "verification": "backlog-triage runs its script and reports exact counts (duplicate pairs, items with no owner or no acceptance criteria, stale and oversized items), names each duplicate pair with why they match, gives a reason for every position in the ordering, and ends with a change list you can apply.",
+    "recovery": "If the counts say \"n/a\", the script didn't find a column: rerun it with --map, e.g. --map owner=\"Team Lead\". If backlog-triage doesn't activate, ask for it by name (\"use backlog-triage\")."
+  },
+  "requires": ["core"],
+  "journey": {
+    "when": "A PRD has been agreed and the work is about to live in the tracker for weeks, and you want the tracker, the backlog and the weekly update to stay honest.",
+    "you_bring": [
+      "the PRD or brief, ideally with numbered requirements",
+      "which tracker you use, and where the team reads the doc",
+      "a CSV or JSON export of the tracker, or a tracker MCP tool",
+      "the reporting period and what was planned for it"
+    ],
+    "time": "About 20 minutes for the import, then 10 to 15 minutes a week",
+    "steps": [
+      {
+        "skill": "tracker-brief-sync",
+        "you_do": "Hand over the PRD and name your tracker.",
+        "you_get": "A checked import file (Jira CSV, mapped CSV or gh commands) with one epic per goal and one story per requirement, each with acceptance criteria and a link back to its section.",
+        "decide": "Import as is, or adjust the mapping first."
+      },
+      {
+        "skill": "backlog-triage",
+        "you_do": "Before refinement, give it a fresh export of the backlog.",
+        "you_get": "Exact counts, confirmed duplicate pairs, what isn't ready and why, priority conflicts, a reasoned ordering and a change list.",
+        "decide": "Which changes to apply, and who owns the unowned items."
+      },
+      {
+        "skill": "team-status-report",
+        "you_do": "Each week, give it the export, the period, the plan, and anything the tracker doesn't show about blockers.",
+        "you_get": "A one-screen report: shipped, in progress, blocked with blocker and owner, slipped against plan, risks and asks, with a RAG status and the rule that set it."
+      },
+      {
+        "skill": "tracker-brief-sync",
+        "you_do": "Mid-build or before launch, give it the PRD and a fresh export.",
+        "you_get": "A drift report: requirements with no issue, issues with no requirement, issues pointing at removed sections, and issues for Won't-have items, each with both ways to resolve it.",
+        "decide": "Change the tracker, or change the doc."
+      }
+    ],
+    "you_end_with": "A tracker that traces back to the PRD, a groomed backlog, a weekly report built from counted numbers, and a record of where the plan and the work have drifted apart."
+  }
+}

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

@@ -0,0 +1,116 @@
+---
+name: backlog-triage
+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?".
+---
+
+# backlog-triage
+
+You take a whole backlog, not one ticket, and turn it into a short list of changes someone can
+apply before refinement: which items are duplicates, which can't be pulled yet and why, which
+have gone stale, which are too big, where the priorities contradict each other, and what order
+to work in. A script does the counting so the numbers are exact; you do the reading and the
+judgment. Works from a CSV or JSON export, or from issues fetched through a Jira, Linear or
+GitHub MCP tool.
+
+## How to respond
+
+1. **Ask once for what's missing.** You need the export (a file path, or permission to fetch the
+   open issues through the tracker's MCP tool). Offer defaults so the user can reply "go":
+
+   > Before I triage, send these. Anything you skip, I'll use the default shown:
+   > 1. **The export:** a CSV or JSON file, or say which project to fetch via MCP.
+   > 2. **Stale after:** *Default: 30 days without an update.*
+   > 3. **Too big to schedule:** *Default: an estimate above 8 points, or size XL.*
+   > 4. **Anything with a fixed date** (a contract, a regulator, an event)?
+   > 5. **Who decides priority**, so I know whom the questions go to?
+
+   Export routes for each tracker are in [`reference.md`](reference.md).
+
+2. **Run the script on the export.**
+
+   ```bash
+   # Claude Code
+   python3 "${CLAUDE_SKILL_DIR}/scripts/triage_backlog.py" backlog.csv --as-of 2026-10-01 -o triage-findings.md --changes changes.csv
+   # Other IDEs (from the skill folder)
+   python3 scripts/triage_backlog.py backlog.csv --as-of 2026-10-01 -o triage-findings.md --changes changes.csv
+   ```
+
+   It prints which columns it mapped and which checks it skipped for lack of a column. If it
+   mapped the wrong column, rerun with `--map owner="Team Lead"`. Tracker-by-tracker column names
+   are in the field-mapping table in [`reference.md`](reference.md).
+
+3. **Confirm each duplicate candidate by reading both descriptions.** The script matches titles
+   only. For each pair, say whether it's the same work and why, and which item survives (the one
+   with the owner, the acceptance criteria, the evidence, or the most recent activity). Reject
+   look-alikes that differ ("Export invoices" vs "Import invoices"). Then look for reworded
+   duplicates the script can't see, among items that share a label or component.
+
+4. **Turn missing fields into readiness.** An item with no owner or no acceptance criteria isn't
+   ready to pull, whatever its priority. Don't write the criteria yourself unless asked; flag the
+   gap. Items over the size limit go to `user-story-splitter` before they're scheduled.
+
+5. **Treat staleness by priority.** A low-priority item untouched for months is a close
+   candidate. A high-priority item untouched for months is a priority question for the user, not
+   a close.
+
+6. **Resolve priority conflicts as proposals.** Use the script's mechanical conflicts (top
+   priority but unowned or stale, duplicates at different priorities, too much at the top) and
+   add any you see from reading. Propose a change with its reason. Never change a priority
+   silently.
+
+7. **Propose an ordering** for open, not-started items using the ordering method in
+   [`reference.md`](reference.md): fixed external date, then users currently harmed, then
+   ready-to-pull, then stated value against size. Give each position its reason and say whether
+   the item is ready. Leave in-progress items where they are.
+
+8. **Emit with [`templates/triage-report.md`](templates/triage-report.md)**: summary counts,
+   confirmed duplicates, the ordering, priority conflicts, the change list, and the questions only
+   the user can answer (owners, dates, who wants a stale item). The counts are the script's; if
+   you counted anything yourself, say how.
+
+**Non-interactive runs** (subagent, CI, headless): with no export and no MCP access, emit
+`BLOCKED: need the backlog export (CSV or JSON) or tracker access` and stop. With an export, use
+the defaults above and list each assumption at the top of the report.
+
+## Useful references in this skill
+
+- [`reference.md`](reference.md) — export routes, the field-mapping table for Jira, Linear and GitHub, how each check works, priority ranks, the ordering method, the change-list actions
+- [`templates/triage-report.md`](templates/triage-report.md) — the report skeleton
+- [`scripts/triage_backlog.py`](scripts/triage_backlog.py) — the mechanical checks (stdlib, Python 3.9+)
+- [`examples/northwind-checkout-triage.md`](examples/northwind-checkout-triage.md) — a 20-issue Jira export, the script's real output, and the finished triage
+- [`examples/northwind-backlog.csv`](examples/northwind-backlog.csv) — the sample export used in the example
+
+## Quality bar
+
+- **Numbers come from the data.** Counts, ages and estimates are the script's output or a stated count from the export, never an estimate.
+- **Every duplicate names the pair and why.** Which two keys, what makes them the same work, and which one survives.
+- **Readiness is explicit.** Each item in the ordering says whether it can be pulled today, and if not, what's missing.
+- **Each position in the ordering has a reason** tied to the ordering method, not "feels important".
+- **Priority changes are proposals,** each with the facts behind it, addressed to whoever owns priority.
+- **The change list can be applied as written:** key, change, reason, one row per action.
+- **Nothing is invented.** No owner, date, estimate or customer count that isn't in the export or the user's message.
+
+## When to use this skill
+
+- ✅ Before backlog refinement or sprint planning, to clean a backlog of dozens or hundreds of items
+- ✅ Finding duplicate and near-duplicate tickets across a project
+- ✅ "What should we pull next?" with a reason for each pick
+- ✅ Taking over a backlog from another team and finding what's stale or unowned
+
+## When NOT to use this skill
+
+- ❌ One bug report to turn into a ticket; use `bug-triage`
+- ❌ Splitting one epic or large item into stories; use `user-story-splitter` (this skill hands oversized items to it)
+- ❌ A weekly status update for stakeholders; use `team-status-report`
+- ❌ Creating issues from a PRD, or checking the tracker against the doc; use `tracker-brief-sync`
+
+## Anti-patterns to avoid
+
+- ❌ **Closing on title similarity alone.** "Export invoices as PDF" and "Import invoices from PDF" score high and are different work.
+- ❌ **Estimating counts.** "About a third of the backlog is stale" when the script gave you the exact number.
+- ❌ **Putting an unready item first** because it's marked Highest. Put its readiness work first instead.
+- ❌ **Closing high-priority stale items.** That's a question for the priority owner, not a tidy-up.
+- ❌ **Writing acceptance criteria nobody asked for** and presenting them as the team's.
+- ❌ **A ranking with no reasons.** If you can't say why item 3 is above item 4, it isn't an ordering.
+- ❌ **Silently re-prioritising.** Every priority change is a proposal in the change list.
+- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.

skilldrop_cli/data/packs/trackers/skills/backlog-triage/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Triage our Jira backlog export and find the duplicates",
+    "should_trigger": true
+  },
+  {
+    "query": "We have 200 tickets in Linear, half of them stale. Which should we close and what should we pull next?",
+    "should_trigger": true
+  },
+  {
+    "query": "Groom this backlog CSV before sprint planning: missing owners, missing acceptance criteria, things too big to schedule",
+    "should_trigger": true
+  },
+  {
+    "query": "Find near-duplicate issues in our GitHub project and propose a priority order",
+    "should_trigger": true
+  },
+  {
+    "query": "A customer says checkout is broken on mobile sometimes. Turn this into a proper bug ticket",
+    "should_trigger": false
+  },
+  {
+    "query": "Break this guest-checkout epic into user stories with acceptance criteria",
+    "should_trigger": false
+  },
+  {
+    "query": "Write the weekly status report for the checkout team from this Jira export",
+    "should_trigger": false
+  },
+  {
+    "query": "Draft a PRD for guest checkout from this brief",
+    "should_trigger": false
+  }
+]

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

@@ -0,0 +1,30 @@
+{
+  "skill_name": "backlog-triage",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Here's the Northwind checkout backlog exported from Jira: examples/northwind-backlog.csv. Refinement is Thursday. Find the duplicates, tell me what isn't ready, and give me an order for what we pull next. Anything untouched for 30 days counts as stale.",
+      "assertions": [
+        "Runs the triage script (or states the counts from the export) rather than estimating counts",
+        "Each duplicate names both keys, why they are the same work, and which one survives",
+        "Rejects or questions candidates that are similar in title but different work, rather than closing every flagged pair",
+        "Each item in the proposed ordering has a reason and says whether it is ready to pull",
+        "Oversized items are handed to user-story-splitter rather than scheduled as is",
+        "Priority changes are presented as proposals with the facts behind them, not applied silently",
+        "Ends with a change list of key, change and reason",
+        "Does not invent owners, dates, estimates or customer counts not in the export"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Acme's platform team has 340 open GitHub issues. I ran gh issue list --json number,title,body,state,assignees,labels,updatedAt > issues.json. We don't use estimates or a priority field, just labels like p1/p2. Clean it up.",
+      "assertions": [
+        "Notes that the estimate and priority columns are missing and that the oversized and priority checks are skipped or mapped from labels",
+        "Uses --map or label-based priority rather than guessing priorities",
+        "Reports staleness from updatedAt with exact day counts",
+        "Confirms duplicates by reading descriptions, not title similarity alone",
+        "Does not invent a priority or estimate for items that have none"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/trackers/skills/backlog-triage/evals/files/1/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."