skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Turn this PRD into Jira epics and stories as a CSV I can import",
+    "should_trigger": true
+  },
+  {
+    "query": "Create GitHub issues from this brief, each linked back to the section it came from",
+    "should_trigger": true
+  },
+  {
+    "query": "Does our Linear project still match the PRD? Find tickets with no requirement and requirements with no ticket",
+    "should_trigger": true
+  },
+  {
+    "query": "Load the guest checkout requirements into our tracker with acceptance criteria and labels",
+    "should_trigger": true
+  },
+  {
+    "query": "Draft a PRD for guest checkout from these interview notes",
+    "should_trigger": false
+  },
+  {
+    "query": "Break the guest checkout epic into thin vertical slices with a build order",
+    "should_trigger": false
+  },
+  {
+    "query": "Find duplicates and stale items in our Jira backlog",
+    "should_trigger": false
+  },
+  {
+    "query": "Summarise the guest checkout PRD in one page for the leadership team",
+    "should_trigger": false
+  }
+]

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/evals/evals.json

@@ -0,0 +1,31 @@
+{
+  "skill_name": "tracker-brief-sync",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Turn examples/prd-guest-checkout.md into Jira epics and stories we can import. Link each one back to the PRD; the wiki copy is https://wiki.northwind.example/checkout/prd-guest-checkout.",
+      "assertions": [
+        "Shows the mapping from doc sections to epics and stories before or alongside the spec",
+        "Creates one epic per goal and one story per M/S/C requirement",
+        "Creates no issue for R7 (Won't have) or the non-goals, and lists them as not created",
+        "Every story has Given/When/Then acceptance criteria that restate the requirement without adding behaviour",
+        "Every item's description ends with a Source line linking to the wiki URL and the section ID",
+        "Runs the export with --doc so the spec is checked, and hands over a Jira CSV with import steps",
+        "Reports the PRD's open question as unresolved rather than turning it into a ticket with a guessed answer",
+        "Does not invent requirements, numbers or reasons not in the PRD"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Here's our Jira export for guest checkout (examples/tracker-after-two-weeks.csv). Does the tracker still match the PRD (examples/prd-guest-checkout.md)?",
+      "assertions": [
+        "Reports R3 as a doc section with no live issue, noting CHK-205 was cancelled",
+        "Reports CHK-209 as an issue for a Won't-have requirement (R7)",
+        "Reports CHK-211 as pointing at R8, which the PRD does not have",
+        "Reports CHK-210 as an issue with no doc section",
+        "For each item gives both resolutions (change the tracker or change the doc) rather than assuming the tracker is wrong",
+        "Flags CHK-207 as linked only by mention and asks for its Source line to be restored"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/evals/files/1/examples/prd-guest-checkout.md

@@ -0,0 +1,53 @@
+# PRD: Checkout without an account
+
+**Status:** in review · **Owner:** Product, checkout · **Date:** 2026-09-15
+**Binding constraint:** fixed deadline (Black Friday code freeze, 6 Nov) `[reported by head of e-commerce]`
+
+## Problem
+
+Shoppers who reach checkout without an account must create one before they can pay. In August,
+38% of sessions that reached the sign-up step ended there `[data: funnel report, Aug 2026]`.
+
+## Users
+
+**Primary:** first-time shoppers arriving from paid social on mobile — job-to-be-done: buy the
+item they clicked on in one sitting.
+**Secondary (explicitly deprioritized):** returning shoppers who already have an account.
+
+## Goals
+
+| # | Goal | We'll know it worked when |
+|---|---|---|
+| G1 | More first-time shoppers complete checkout | Sign-up-step drop-off falls from 38% to under 20% within 4 weeks of launch |
+| G2 | Guest orders can be supported like account orders | Support can find a guest order from the email address alone |
+
+## Requirements
+
+| ID | Requirement (testable, solution-free) | MoSCoW | Maps to goal |
+|---|---|---|---|
+| R1 | A shopper can pay without creating an account, giving only an email address and delivery details | M | G1 |
+| R2 | A guest shopper receives an order confirmation email with a link to track the order | M | G1 |
+| R3 | After paying, a guest shopper is offered an account, pre-filled from the order, which they can decline | S | G1 |
+| R4 | Support staff can look up a guest order by email address in the admin tool | M | G2 |
+| R5 | Guest orders are flagged in fraud screening with the same score shown for account orders | M | G2 |
+| R6 | A guest shopper can return an item by entering their order number and email | S | G2 |
+| R7 | Saved cards for guest shoppers | W | G1 |
+
+**Won't have (this version):**
+- Saved cards for guests (R7) — needs an account to attach the card to; revisit after launch.
+
+## Non-goals (minimum 3 — the scope-creep firewall)
+
+- **Social login** — a different fix for the same drop-off; measure guest checkout first.
+- **Merging guest orders into an account created later** — useful, but not needed to hit G1.
+- **Guest checkout in the mobile app** — the app already keeps shoppers signed in.
+
+## Open questions
+
+| Question | Owner | Needed by |
+|---|---|---|
+| Does the PSP need an account ID for 3-D Secure on guest payments? | Payments lead | 2026-09-25 |
+
+## Assumptions log
+
+- [assumption] Guest shoppers' emails are kept for 2 years, the same as account orders — challenge at privacy review.

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/evals/files/2/examples/prd-guest-checkout.md

@@ -0,0 +1,53 @@
+# PRD: Checkout without an account
+
+**Status:** in review · **Owner:** Product, checkout · **Date:** 2026-09-15
+**Binding constraint:** fixed deadline (Black Friday code freeze, 6 Nov) `[reported by head of e-commerce]`
+
+## Problem
+
+Shoppers who reach checkout without an account must create one before they can pay. In August,
+38% of sessions that reached the sign-up step ended there `[data: funnel report, Aug 2026]`.
+
+## Users
+
+**Primary:** first-time shoppers arriving from paid social on mobile — job-to-be-done: buy the
+item they clicked on in one sitting.
+**Secondary (explicitly deprioritized):** returning shoppers who already have an account.
+
+## Goals
+
+| # | Goal | We'll know it worked when |
+|---|---|---|
+| G1 | More first-time shoppers complete checkout | Sign-up-step drop-off falls from 38% to under 20% within 4 weeks of launch |
+| G2 | Guest orders can be supported like account orders | Support can find a guest order from the email address alone |
+
+## Requirements
+
+| ID | Requirement (testable, solution-free) | MoSCoW | Maps to goal |
+|---|---|---|---|
+| R1 | A shopper can pay without creating an account, giving only an email address and delivery details | M | G1 |
+| R2 | A guest shopper receives an order confirmation email with a link to track the order | M | G1 |
+| R3 | After paying, a guest shopper is offered an account, pre-filled from the order, which they can decline | S | G1 |
+| R4 | Support staff can look up a guest order by email address in the admin tool | M | G2 |
+| R5 | Guest orders are flagged in fraud screening with the same score shown for account orders | M | G2 |
+| R6 | A guest shopper can return an item by entering their order number and email | S | G2 |
+| R7 | Saved cards for guest shoppers | W | G1 |
+
+**Won't have (this version):**
+- Saved cards for guests (R7) — needs an account to attach the card to; revisit after launch.
+
+## Non-goals (minimum 3 — the scope-creep firewall)
+
+- **Social login** — a different fix for the same drop-off; measure guest checkout first.
+- **Merging guest orders into an account created later** — useful, but not needed to hit G1.
+- **Guest checkout in the mobile app** — the app already keeps shoppers signed in.
+
+## Open questions
+
+| Question | Owner | Needed by |
+|---|---|---|
+| Does the PSP need an account ID for 3-D Secure on guest payments? | Payments lead | 2026-09-25 |
+
+## Assumptions log
+
+- [assumption] Guest shoppers' emails are kept for 2 years, the same as account orders — challenge at privacy review.

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/evals/files/2/examples/tracker-after-two-weeks.csv

@@ -0,0 +1,30 @@
+Issue key,Issue Type,Summary,Status,Assignee,Labels,Labels,Description
+CHK-201,Epic,Checkout without an account,In Progress,Priya Nair,guest-checkout,,"Let first-time shoppers pay without creating an account.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G1)"
+CHK-202,Epic,Support and safety for guest orders,To Do,Priya Nair,guest-checkout,,"Guest orders can be found, screened and returned like account orders.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G2)"
+CHK-203,Story,Pay as a guest with email and delivery details,In Progress,Tom Okafor,guest-checkout,checkout,"As a first-time shopper, I can pay without creating an account.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R1)"
+CHK-204,Story,Order confirmation email for guest orders,To Do,Lena Fischer,guest-checkout,notifications,"As a guest shopper, I get a confirmation email with a tracking link.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R2)"
+CHK-205,Story,Offer an account after a guest order,Canceled,,guest-checkout,growth,"Cancelled in planning: growth team will run this as an experiment later.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R3)"
+CHK-206,Story,Find guest orders by email in the admin tool,To Do,Aisha Bello,guest-checkout,ops,"As a support agent, I can find a guest order from the shopper's email address.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R4)"
+CHK-207,Story,Fraud score on guest orders,To Do,Tom Okafor,guest-checkout,payments,"Reuse the CHK-113 scoring for guest orders, per R5 in the PRD."
+CHK-208,Story,Guest returns with order number and email,To Do,,guest-checkout,returns,"As a guest shopper, I can start a return with my order number and email.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R6)"
+CHK-209,Story,Save card for guest shoppers,To Do,Tom Okafor,guest-checkout,payments,"Sales asked for this for repeat guests.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R7)"
+CHK-210,Story,Klarna for guest orders,Backlog,,guest-checkout,payments,"Make sure Klarna shows on the guest flow too."
+CHK-211,Task,3-D Secure exemption handling for guest payments,In Progress,Tom Okafor,guest-checkout,payments,"Answer from the PSP: guest payments need the exemption flag.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R8)"

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/examples/guest-checkout-spec.json

@@ -0,0 +1,98 @@
+{
+  "doc": "prd-guest-checkout.md",
+  "doc_url": "https://wiki.northwind.example/checkout/prd-guest-checkout",
+  "items": [
+    {
+      "id": "E1",
+      "type": "epic",
+      "title": "Checkout without an account",
+      "description": "Let first-time shoppers pay without creating an account. Goal: sign-up-step drop-off from 38% to under 20% within 4 weeks of launch.",
+      "labels": ["guest-checkout"],
+      "source": "G1"
+    },
+    {
+      "id": "E2",
+      "type": "epic",
+      "title": "Support and safety for guest orders",
+      "description": "Guest orders can be found, screened and returned like account orders.",
+      "labels": ["guest-checkout"],
+      "source": "G2"
+    },
+    {
+      "id": "S1",
+      "type": "story",
+      "parent": "E1",
+      "title": "Pay as a guest with email and delivery details",
+      "description": "As a first-time shopper, I can pay without creating an account, so I can buy in one sitting.",
+      "acceptance_criteria": [
+        "Given a shopper with no account at checkout, when they choose Continue as guest, then they can pay after entering only an email address and delivery details",
+        "Given a guest payment succeeds, then no account is created"
+      ],
+      "labels": ["guest-checkout", "checkout"],
+      "source": "R1"
+    },
+    {
+      "id": "S2",
+      "type": "story",
+      "parent": "E1",
+      "title": "Order confirmation email for guest orders",
+      "description": "As a guest shopper, I get a confirmation email with a tracking link, so I know the order went through.",
+      "acceptance_criteria": [
+        "Given a guest order is placed, then a confirmation email is sent to the address given within 5 minutes",
+        "The email contains a link that shows the order's tracking status without signing in"
+      ],
+      "labels": ["guest-checkout", "notifications"],
+      "source": "R2"
+    },
+    {
+      "id": "S3",
+      "type": "story",
+      "parent": "E1",
+      "title": "Offer an account after a guest order",
+      "description": "As a guest shopper, I'm offered an account pre-filled from my order after paying, and I can decline.",
+      "acceptance_criteria": [
+        "Given a guest order is confirmed, then the confirmation page offers to create an account with email and address pre-filled",
+        "Given the shopper declines, then no account is created and they aren't asked again for this order"
+      ],
+      "labels": ["guest-checkout", "growth"],
+      "source": "R3"
+    },
+    {
+      "id": "S4",
+      "type": "story",
+      "parent": "E2",
+      "title": "Find guest orders by email in the admin tool",
+      "description": "As a support agent, I can find a guest order from the shopper's email address.",
+      "acceptance_criteria": [
+        "Given a guest order exists for an email address, when support searches that address in the admin tool, then the order is listed"
+      ],
+      "labels": ["guest-checkout", "ops"],
+      "source": "R4"
+    },
+    {
+      "id": "S5",
+      "type": "story",
+      "parent": "E2",
+      "title": "Fraud score on guest orders",
+      "description": "Guest orders go through fraud screening and show the same score as account orders.",
+      "acceptance_criteria": [
+        "Given a guest order, then the admin order view shows a fraud score computed the same way as for account orders"
+      ],
+      "labels": ["guest-checkout", "payments"],
+      "source": "R5"
+    },
+    {
+      "id": "S6",
+      "type": "story",
+      "parent": "E2",
+      "title": "Guest returns with order number and email",
+      "description": "As a guest shopper, I can start a return with my order number and email.",
+      "acceptance_criteria": [
+        "Given a delivered guest order, when the shopper enters the order number and the email used, then they can start a return",
+        "Given a mismatched order number and email, then no order details are shown"
+      ],
+      "labels": ["guest-checkout", "returns"],
+      "source": "R6"
+    }
+  ]
+}

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/examples/guest-checkout-sync.md

@@ -0,0 +1,151 @@
+# Example: guest checkout, from PRD to Jira and back
+
+Two runs on one PRD. First the user asks for Jira-ready issues from the PRD. Two weeks later
+they ask whether the tracker still matches the doc.
+
+Files:
+- [`prd-guest-checkout.md`](prd-guest-checkout.md): a PRD in prd-draft's shape, with goals G1–G2
+  and requirements R1–R7 (R7 is Won't have)
+- [`guest-checkout-spec.json`](guest-checkout-spec.json): the issues spec written from the PRD
+- [`tracker-after-two-weeks.csv`](tracker-after-two-weeks.csv): the Jira export two weeks later
+
+## Run 1: PRD to issues
+
+> "Turn this PRD into Jira epics and stories. Link each back to its section. The wiki copy is at
+> https://wiki.northwind.example/checkout/prd-guest-checkout."
+
+**Mapping, before writing the spec.** One epic per goal, one story per requirement:
+
+| Doc section | Becomes | Why |
+|---|---|---|
+| G1 | Epic E1 "Checkout without an account" | Goal; R1–R3 map to it |
+| G2 | Epic E2 "Support and safety for guest orders" | Goal; R4–R6 map to it |
+| R1–R6 | Stories S1–S6 under their goal's epic | One testable requirement each; the acceptance criteria restate the requirement's observable behaviour |
+| R7 | Nothing | Won't have. Listed under "Not created" so nobody adds it later by mistake |
+| Non-goals, open question | Nothing | Not work. The open question about 3-D Secure goes back to the user as an unresolved dependency |
+
+The spec is [`guest-checkout-spec.json`](guest-checkout-spec.json). Then:
+
+```bash
+python3 scripts/brief_sync.py export examples/guest-checkout-spec.json --target jira \
+  --doc examples/prd-guest-checkout.md -o guest-checkout-jira.csv
+```
+
+Script output, unedited:
+
+```text
+wrote guest-checkout-jira.csv: 8 items (2 epics, 6 others)
+```
+
+First three rows of the CSV, unedited:
+
+```csv
+Issue Id,Parent Id,Issue Type,Summary,Description,Labels,Labels
+1,,Epic,Checkout without an account,"Let first-time shoppers pay without creating an account. Goal: sign-up-step drop-off from 38% to under 20% within 4 weeks of launch.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G1)",guest-checkout,
+2,,Epic,Support and safety for guest orders,"Guest orders can be found, screened and returned like account orders.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G2)",guest-checkout,
+3,1,Story,Pay as a guest with email and delivery details,"As a first-time shopper, I can pay without creating an account, so I can buy in one sitting.
+
+Acceptance criteria:
+- Given a shopper with no account at checkout, when they choose Continue as guest, then they can pay after entering only an email address and delivery details
+- Given a guest payment succeeds, then no account is created
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R1)",guest-checkout,checkout
+```
+
+The spec check catches mistakes before anything reaches the tracker. Here's the same spec with
+five deliberate errors (a story with no criteria, a missing parent, a Won't-have source, a
+section that isn't in the doc, a label with a space):
+
+```text
+spec has 5 problem(s):
+  - S1: a story needs acceptance_criteria
+  - S2: parent 'E9' is not an item in the spec
+  - S3: source 'R7' is marked Won't have in the doc
+  - S4: source 'R12' is not a section in the doc
+  - S5: label 'guest checkout' has a space; Jira labels can't
+```
+
+The script exits 1 and writes nothing.
+
+**What the user gets back:** the CSV, the mapping table above, and:
+
+- **Import steps:** in Jira's CSV importer, map `Issue Id` and `Parent Id` so stories land under
+  their epics, and map both `Labels` columns to Labels.
+- **Not created:** R7 (Won't have), the three non-goals.
+- **Unresolved:** the PRD's open question (does the PSP need an account ID for 3-D Secure on
+  guest payments?) may add work to R1. No issue was created for it, because the doc doesn't
+  define any.
+
+## Run 2: drift, two weeks later
+
+> "Here's the Jira export for guest checkout. Does it still match the PRD?"
+
+```bash
+python3 scripts/brief_sync.py drift --doc examples/prd-guest-checkout.md \
+  --export examples/tracker-after-two-weeks.csv -o drift.md
+```
+
+Script output, unedited:
+
+```markdown
+# Drift: prd-guest-checkout.md vs tracker-after-two-weeks.csv
+
+9 sections in the doc (6 need an issue, 1 marked Won't have) · 11 issues in the export (1 canceled or duplicate, ignored)
+Sections are IDs matching `R\d+`.
+
+| Drift | Count |
+|---|---:|
+| Doc sections with no issue | 1 |
+| Issues with no doc section | 1 |
+| Issues pointing at a section the doc doesn't have | 1 |
+| Issues for a Won't-have requirement | 1 |
+
+## Doc sections with no issue
+
+- R3 (S): After paying, a guest shopper is offered an account, pre-filled from the order, which they can decline
+
+## Issues with no doc section
+
+- CHK-210 Klarna for guest orders (Backlog, Story)
+
+## Issues pointing at a section the doc doesn't have
+
+- CHK-211 3-D Secure exemption handling for guest payments: points at R8
+
+## Issues for a Won't-have requirement
+
+- CHK-209 Save card for guest shoppers: R7 is Won't have in the doc
+
+## Coverage
+
+| Section | MoSCoW | Issues |
+|---|---|---|
+| G1 | - | CHK-201 (In Progress) |
+| G2 | - | CHK-202 (To Do) |
+| R1 | M | CHK-203 (In Progress) |
+| R2 | M | CHK-204 (To Do) |
+| R3 | S | - |
+| R4 | M | CHK-206 (To Do) |
+| R5 | M | CHK-207 (To Do) |
+| R6 | S | CHK-208 (To Do) |
+| R7 | W | CHK-209 (To Do) |
+
+Linked by mentioning the ID rather than a Source line (check these): CHK-207
+
+```
+
+**What the user gets back,** after reading the four flagged issues:
+
+| Drift | Item | What happened | Fix |
+|---|---|---|---|
+| Doc section with no issue | R3 (Should) | CHK-205 was cancelled: "growth team will run this as an experiment later" | Either move R3 to Won't have in the PRD, or reopen CHK-205. The doc and the tracker currently disagree |
+| Issue for a Won't-have requirement | CHK-209 Save card for guest shoppers | Added because "Sales asked for this"; the PRD rules it out | Close CHK-209, or change R7 in the PRD first. Scope changes go through the doc |
+| Issue pointing at a missing section | CHK-211 3-D Secure exemption (In Progress) | Points at R8, which the PRD doesn't have. Its description answers the PRD's open question | Add the answer and a requirement to the PRD, then relink CHK-211 |
+| Issue with no doc section | CHK-210 Klarna for guest orders | Not in the PRD | Ask whether Klarna-on-guest is in scope. If yes, add a requirement; if not, move it out of the epic |
+| Linked by mention | CHK-207 | Its Source line was deleted; it mentions R5 | Restore the line: `Source: …#requirements (R5)` |
+
+R1, R2, R4, R5 and R6 each have exactly one live issue.

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/examples/prd-guest-checkout.md

@@ -0,0 +1,53 @@
+# PRD: Checkout without an account
+
+**Status:** in review · **Owner:** Product, checkout · **Date:** 2026-09-15
+**Binding constraint:** fixed deadline (Black Friday code freeze, 6 Nov) `[reported by head of e-commerce]`
+
+## Problem
+
+Shoppers who reach checkout without an account must create one before they can pay. In August,
+38% of sessions that reached the sign-up step ended there `[data: funnel report, Aug 2026]`.
+
+## Users
+
+**Primary:** first-time shoppers arriving from paid social on mobile — job-to-be-done: buy the
+item they clicked on in one sitting.
+**Secondary (explicitly deprioritized):** returning shoppers who already have an account.
+
+## Goals
+
+| # | Goal | We'll know it worked when |
+|---|---|---|
+| G1 | More first-time shoppers complete checkout | Sign-up-step drop-off falls from 38% to under 20% within 4 weeks of launch |
+| G2 | Guest orders can be supported like account orders | Support can find a guest order from the email address alone |
+
+## Requirements
+
+| ID | Requirement (testable, solution-free) | MoSCoW | Maps to goal |
+|---|---|---|---|
+| R1 | A shopper can pay without creating an account, giving only an email address and delivery details | M | G1 |
+| R2 | A guest shopper receives an order confirmation email with a link to track the order | M | G1 |
+| R3 | After paying, a guest shopper is offered an account, pre-filled from the order, which they can decline | S | G1 |
+| R4 | Support staff can look up a guest order by email address in the admin tool | M | G2 |
+| R5 | Guest orders are flagged in fraud screening with the same score shown for account orders | M | G2 |
+| R6 | A guest shopper can return an item by entering their order number and email | S | G2 |
+| R7 | Saved cards for guest shoppers | W | G1 |
+
+**Won't have (this version):**
+- Saved cards for guests (R7) — needs an account to attach the card to; revisit after launch.
+
+## Non-goals (minimum 3 — the scope-creep firewall)
+
+- **Social login** — a different fix for the same drop-off; measure guest checkout first.
+- **Merging guest orders into an account created later** — useful, but not needed to hit G1.
+- **Guest checkout in the mobile app** — the app already keeps shoppers signed in.
+
+## Open questions
+
+| Question | Owner | Needed by |
+|---|---|---|
+| Does the PSP need an account ID for 3-D Secure on guest payments? | Payments lead | 2026-09-25 |
+
+## Assumptions log
+
+- [assumption] Guest shoppers' emails are kept for 2 years, the same as account orders — challenge at privacy review.

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/examples/tracker-after-two-weeks.csv

@@ -0,0 +1,30 @@
+Issue key,Issue Type,Summary,Status,Assignee,Labels,Labels,Description
+CHK-201,Epic,Checkout without an account,In Progress,Priya Nair,guest-checkout,,"Let first-time shoppers pay without creating an account.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G1)"
+CHK-202,Epic,Support and safety for guest orders,To Do,Priya Nair,guest-checkout,,"Guest orders can be found, screened and returned like account orders.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#goals (G2)"
+CHK-203,Story,Pay as a guest with email and delivery details,In Progress,Tom Okafor,guest-checkout,checkout,"As a first-time shopper, I can pay without creating an account.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R1)"
+CHK-204,Story,Order confirmation email for guest orders,To Do,Lena Fischer,guest-checkout,notifications,"As a guest shopper, I get a confirmation email with a tracking link.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R2)"
+CHK-205,Story,Offer an account after a guest order,Canceled,,guest-checkout,growth,"Cancelled in planning: growth team will run this as an experiment later.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R3)"
+CHK-206,Story,Find guest orders by email in the admin tool,To Do,Aisha Bello,guest-checkout,ops,"As a support agent, I can find a guest order from the shopper's email address.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R4)"
+CHK-207,Story,Fraud score on guest orders,To Do,Tom Okafor,guest-checkout,payments,"Reuse the CHK-113 scoring for guest orders, per R5 in the PRD."
+CHK-208,Story,Guest returns with order number and email,To Do,,guest-checkout,returns,"As a guest shopper, I can start a return with my order number and email.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R6)"
+CHK-209,Story,Save card for guest shoppers,To Do,Tom Okafor,guest-checkout,payments,"Sales asked for this for repeat guests.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R7)"
+CHK-210,Story,Klarna for guest orders,Backlog,,guest-checkout,payments,"Make sure Klarna shows on the guest flow too."
+CHK-211,Task,3-D Secure exemption handling for guest payments,In Progress,Tom Okafor,guest-checkout,payments,"Answer from the PSP: guest payments need the exemption flag.
+
+Source: https://wiki.northwind.example/checkout/prd-guest-checkout#requirements (R8)"

skilldrop_cli/data/packs/trackers/skills/tracker-brief-sync/manifest.json

@@ -0,0 +1,41 @@
+{
+  "name": "tracker-brief-sync",
+  "version": "0.1.0",
+  "description": "Turn a brief or PRD (such as prd-draft output) into tracker-ready epics and issues — title, description, acceptance criteria, labels and a link back to the doc section — as a CSV for Jira, a mapped CSV for other importers, or gh commands for GitHub; and in reverse, report drift between the doc and the tracker (issues with no section, sections with no issue, issues for Won't-have requirements). Use when the user wants to load a PRD into Jira, Linear or GitHub, says \"create tickets from this brief\", or asks \"does the tracker still match the PRD?\".",
+  "entrypoint": "SKILL.md",
+  "deps": {
+    "npm": [],
+    "pip": []
+  },
+  "env": {
+    "required": [],
+    "optional": []
+  },
+  "related": [
+    "backlog-triage",
+    "prd-draft",
+    "user-story-splitter"
+  ],
+  "handoff": [
+    {
+      "to": "user-story-splitter",
+      "when": "a requirement is too large for one story",
+      "purpose": "Slice it into independently shippable stories before it goes into the spec.",
+      "fallback": "If user-story-splitter is absent, create one story for the requirement and list it under 'needs splitting' in the hand-over."
+    }
+  ],
+  "tags": [
+    "prd",
+    "jira",
+    "linear",
+    "github-projects",
+    "import",
+    "traceability",
+    "drift"
+  ],
+  "permissions": {"network": [], "commands": [], "files": "named-paths", "notes": "The github target writes a shell script of gh commands for the user to run; it runs nothing itself."},
+  "model": {
+    "tier": "standard",
+    "rationale": "Maps doc sections to items and writes acceptance criteria that restate requirements; a script checks the spec, writes the import file and computes drift. Bounded transformation with a deterministic check."
+  }
+}