skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/trackers/skills/team-status-report/examples/northwind-week-40.csv

@@ -0,0 +1,16 @@
+Issue key,Issue Type,Summary,Status,Priority,Assignee,Created,Updated,Resolved,Due date,Inward issue link (Blocks),Labels
+CHK-102,Story,Save card for future purchases,In Review,High,Tom Okafor,05/Jun/26 11:20 AM,30/Sep/26 2:45 PM,,30/Sep/26,,payments
+CHK-103,Bug,Apple Pay button missing on Safari 17,Done,High,Lena Fischer,12/Aug/26 8:01 AM,29/Sep/26 4:10 PM,29/Sep/26 4:10 PM,30/Sep/26,,bug
+CHK-105,Story,Show delivery date estimate on the cart page,Done,Medium,Lena Fischer,01/Sep/26 9:00 AM,26/Sep/26 11:00 AM,26/Sep/26 11:00 AM,30/Sep/26,,cart
+CHK-107,Task,Update PCI self-assessment questionnaire,Blocked,Highest,Aisha Bello,03/Sep/26 9:30 AM,30/Sep/26 8:40 AM,,30/Sep/26,SEC-88,compliance
+CHK-112,Story,One-click reorder from order history,In Progress,High,Aisha Bello,15/Sep/26 1:30 PM,30/Sep/26 11:00 AM,,02/Oct/26,,growth
+CHK-113,Task,Add fraud score to order admin view,Done,Highest,Tom Okafor,10/Sep/26 10:00 AM,25/Sep/26 6:00 PM,25/Sep/26 6:00 PM,25/Sep/26,,payments
+CHK-116,Story,Persist cart across devices for signed-in users,In Progress,Medium,Lena Fischer,04/Sep/26 9:00 AM,30/Sep/26 4:00 PM,,30/Sep/26,,cart
+CHK-119,Story,Accessibility fixes on the payment form,To Do,High,,21/Sep/26 9:00 AM,24/Sep/26 9:00 AM,,30/Sep/26,,a11y
+CHK-121,Bug,Discount line rounds to wrong penny on mixed-VAT carts,Done,High,Marco Rossi,23/Sep/26 10:00 AM,24/Sep/26 3:00 PM,24/Sep/26 3:00 PM,,,bug
+CHK-122,Task,Rotate PSP API keys,Done,Medium,Tom Okafor,20/Sep/26 9:00 AM,28/Sep/26 10:00 AM,28/Sep/26 10:00 AM,28/Sep/26,,payments
+CHK-123,Story,Order history pagination,Blocked,Medium,Marco Rossi,10/Sep/26 9:00 AM,22/Sep/26 2:00 PM,,02/Oct/26,API-412,growth
+CHK-124,Story,Gift card balance check,Won't Do,Low,,02/Sep/26 9:00 AM,27/Sep/26 9:00 AM,27/Sep/26 9:00 AM,30/Sep/26,,
+CHK-114,Story,Klarna pay-later option,To Do,Highest,,20/Aug/26 2:00 PM,22/Aug/26 9:00 AM,,,,payments
+CHK-108,Story,Promo code field on checkout,Done,Medium,Lena Fischer,10/May/26 2:00 PM,20/Jun/26 5:00 PM,20/Jun/26 5:00 PM,19/Jun/26,,checkout
+CHK-125,Task,Load test checkout for Black Friday,In Progress,High,Marco Rossi,22/Sep/26 9:00 AM,30/Sep/26 5:00 PM,,16/Oct/26,,perf

skilldrop_cli/data/packs/trackers/skills/team-status-report/examples/northwind-weekly-status.md

@@ -0,0 +1,160 @@
+# Example: Northwind checkout, week ending 30 September
+
+The user's message:
+
+> Weekly status for the checkout team, 24–30 Sept, for Dana (head of e-commerce) and the
+> payments steering group. Export attached: `northwind-week-40.csv`. Context the export doesn't
+> have: SEC-88 is the security team's pen-test report, which the PCI questionnaire needs; they
+> told us it lands 3 Oct. API-412 is the platform team's paginated order-history endpoint, no
+> date yet. Black Friday code freeze is 6 Nov.
+
+The export is [`northwind-week-40.csv`](northwind-week-40.csv): 15 Jira issues with `Resolved`,
+`Due date` and `Inward issue link (Blocks)` columns. There's no sprint file, so the plan is
+"items due in the period".
+
+## Step 1: run the script
+
+```bash
+python3 scripts/status_counts.py examples/northwind-week-40.csv \
+  --from 2026-09-24 --to 2026-09-30 -o status-numbers.md --json status-numbers.json
+```
+
+## Step 2: the script's output, unedited
+
+```markdown
+# Status numbers: 2026-09-24 to 2026-09-30
+
+Source: northwind-week-40.csv · 15 items · plan: items due between 2026-09-24 and 2026-09-30
+Columns used: key='Issue key', title='Summary', status='Status', owner='Assignee', priority='Priority', created='Created', updated='Updated', resolved='Resolved', due='Due date', blocker='Inward issue link (Blocks)', labels='Labels'
+
+## Suggested RAG: Red
+
+Rule: Red if plan completion < 60% or >= 2 planned items blocked; Amber if completion < 85%, any planned item blocked, or a High-or-above planned item slipped; otherwise Green.
+- Red: plan completion 50% is below 60%
+- Amber: 1 planned item is blocked
+- Amber: 3 High-or-above planned item(s) slipped: CHK-102, CHK-107, CHK-119
+
+| Measure | Count |
+|---|---:|
+| Shipped in period | 5 |
+| In progress | 4 |
+| Blocked | 2 |
+| Planned to finish by 2026-09-30 | 8 |
+| Planned and done | 4 (50%) |
+| Slipped (planned, not done) | 4 |
+| Shipped but not in plan | 1 |
+
+## Shipped
+
+| Key | Title | Owner | Done |
+|---|---|---|---|
+| CHK-103 | Apple Pay button missing on Safari 17 | Lena Fischer | 2026-09-29 |
+| CHK-105 | Show delivery date estimate on the cart page | Lena Fischer | 2026-09-26 |
+| CHK-113 | Add fraud score to order admin view | Tom Okafor | 2026-09-25 |
+| CHK-121 | Discount line rounds to wrong penny on mixed-VAT carts | Marco Rossi | 2026-09-24 |
+| CHK-122 | Rotate PSP API keys | Tom Okafor | 2026-09-28 |
+
+## In progress
+
+| Key | Title | Owner | Status |
+|---|---|---|---|
+| CHK-102 | Save card for future purchases | Tom Okafor | In Review |
+| CHK-112 | One-click reorder from order history | Aisha Bello | In Progress |
+| CHK-116 | Persist cart across devices for signed-in users | Lena Fischer | In Progress |
+| CHK-125 | Load test checkout for Black Friday | Marco Rossi | In Progress |
+
+## Blocked
+
+| Key | Title | Owner | Blocker | Last update |
+|---|---|---|---|---|
+| CHK-107 | Update PCI self-assessment questionnaire | Aisha Bello | SEC-88 | 2026-09-30 |
+| CHK-123 | Order history pagination | Marco Rossi | API-412 | 2026-09-22 |
+
+## Slipped (planned, not done by 2026-09-30)
+
+| Key | Title | Owner | Status | Priority | Due |
+|---|---|---|---|---|---|
+| CHK-102 | Save card for future purchases | Tom Okafor | In Review | High | 2026-09-30 |
+| CHK-107 | Update PCI self-assessment questionnaire | Aisha Bello | Blocked | Highest | 2026-09-30 |
+| CHK-116 | Persist cart across devices for signed-in users | Lena Fischer | In Progress | Medium | 2026-09-30 |
+| CHK-119 | Accessibility fixes on the payment form | (none) | To Do | High | 2026-09-30 |
+
+## Risk candidates
+
+- CHK-107 (Update PCI self-assessment questionnaire): planned for this period and blocked
+- CHK-119 (Accessibility fixes on the payment form): planned for this period with no owner
+- CHK-114 (Klarna pay-later option): top priority (Highest) and not started
+
+## Work in progress by owner (in progress + blocked)
+
+| Owner | Items |
+|---|---:|
+| Aisha Bello | 2 |
+| Marco Rossi | 2 |
+| Lena Fischer | 1 |
+| Tom Okafor | 1 |
+
+```
+
+## Step 3: the report
+
+Every number is from the output above. The blocker descriptions and dates come from the
+user's message, and are marked where the export didn't have them.
+
+```markdown
+# Checkout team status: 24–30 September 2026
+
+**Status: Red.** Rule: plan completion below 60% is Red. We finished 4 of the 8 items due this
+week (50%). One of the four that slipped is blocked; three are High or Highest priority.
+
+## Shipped (5)
+
+- CHK-113 Fraud score in the order admin view (Tom Okafor), 25 Sep
+- CHK-105 Delivery date estimate on the cart page (Lena Fischer), 26 Sep
+- CHK-122 Rotated PSP API keys (Tom Okafor), 28 Sep
+- CHK-103 Apple Pay button fixed on Safari 17 (Lena Fischer), 29 Sep
+- CHK-121 Discount rounding fix on mixed-VAT carts (Marco Rossi), 24 Sep. Unplanned: came in
+  as a bug on 23 Sep.
+
+## Slipped against plan (4 of 8 due)
+
+| Item | Owner | Where it is | Priority |
+|---|---|---|---|
+| CHK-107 PCI self-assessment questionnaire | Aisha Bello | Blocked by SEC-88 | Highest |
+| CHK-102 Save card for future purchases | Tom Okafor | In review | High |
+| CHK-119 Accessibility fixes on the payment form | No owner | Not started | High |
+| CHK-116 Persist cart across devices | Lena Fischer | In progress | Medium |
+
+No new dates are given here: the export has none, and the owners haven't supplied them.
+
+## Blocked (2)
+
+| Item | Owner | Blocked by | Expected |
+|---|---|---|---|
+| CHK-107 PCI questionnaire | Aisha Bello | SEC-88, the security team's pen-test report | 3 Oct (security team, per user) |
+| CHK-123 Order history pagination | Marco Rossi | API-412, the platform team's paginated endpoint; no update since 22 Sep | No date |
+
+## In progress (4)
+
+CHK-102 Save card (in review), CHK-112 One-click reorder, CHK-116 Persist cart, CHK-125
+Black Friday load test (due 16 Oct).
+
+## Risks
+
+- **CHK-119 accessibility fixes have no owner and were due this week.** It's High priority
+  and hasn't started.
+- **CHK-114 Klarna is Highest priority and not started,** with no owner.
+- **The Black Friday code freeze is 6 Nov** (per user). CHK-125's load test is due 16 Oct, which
+  leaves three weeks to act on what it finds.
+
+## Asks
+
+1. **Security team:** confirm SEC-88 lands on 3 Oct, so CHK-107 can be finished.
+2. **Platform team:** a date for API-412. CHK-123 has been waiting since 22 Sep.
+3. **Dana:** name an owner for CHK-119 this week.
+4. **Dana:** confirm CHK-114 Klarna is still Highest. Nobody is assigned to it.
+```
+
+What the report left out: a "% on track" or velocity figure (the export can't support one), a
+reason for CHK-102 sitting in review (not in the data), and new dates for the slipped items
+(none given).

skilldrop_cli/data/packs/trackers/skills/team-status-report/manifest.json

@@ -0,0 +1,33 @@
+{
+  "name": "team-status-report",
+  "version": "0.1.1",
+  "description": "Write a weekly team status report from tracker data (Jira, Linear or GitHub Projects, via CSV, JSON or an MCP tool) — shipped, in progress, blocked with the blocker and owner, slipped against plan, risks and asks — with every number computed from the data by a stdlib script, never estimated, and a RAG status that states the rule that set it. Use when the user wants a weekly status update, sprint report or stakeholder update from the tracker, or says \"write this week's status report\", \"are we on track?\".",
+  "entrypoint": "SKILL.md",
+  "deps": {
+    "npm": [],
+    "pip": []
+  },
+  "env": {
+    "required": [],
+    "optional": []
+  },
+  "related": [
+    "backlog-triage",
+    "decision-log",
+    "exec-summary"
+  ],
+  "tags": [
+    "status-report",
+    "weekly-update",
+    "jira",
+    "linear",
+    "github-projects",
+    "rag",
+    "stakeholder-update"
+  ],
+  "permissions": {"network": [], "commands": [], "files": "named-paths"},
+  "model": {
+    "tier": "standard",
+    "rationale": "A script computes every count and the suggested RAG; the model writes plain-language summaries, attributes outside facts and frames risks and asks. Bounded writing over computed numbers."
+  }
+}

skilldrop_cli/data/packs/trackers/skills/team-status-report/reference.md

@@ -0,0 +1,92 @@
+# team-status-report reference
+
+## Getting the data
+
+Export every issue touched in the period, plus everything that was due in it. Done items need
+a resolved date, or "shipped" can't be counted properly.
+
+| Tracker | Route | Columns to include |
+|---|---|---|
+| Jira | Issue search, e.g. `project = CHK AND (updated >= -14d OR duedate <= endOfWeek())` → Export → CSV (all fields) | Resolved, Due date, Sprint, `Inward issue link (Blocks)` for blockers |
+| Linear | Export CSV from workspace settings, or fetch the team's issues for the cycle through the Linear MCP | Completed, Due date, Cycle |
+| GitHub | `gh issue list --state all --search "updated:>=2026-09-24" --limit 500 --json number,title,state,assignees,labels,closedAt,updatedAt,milestone > issues.json` | closedAt; the milestone works as the plan with `--sprint` |
+| GitHub Projects | `gh project item-list <number> --owner <org> --format json`, or the view's CSV export if your view offers it | Status, Iteration, any date field you use as a due date |
+| Any tracker via MCP | Ask the agent to fetch the issues and save them as JSON | Same fields as above, whatever they're called |
+
+## Field mapping
+
+Matched case-insensitively; first match wins. Override with `--map field="Your Column"`.
+
+| Field | Jira CSV | Linear | GitHub | Used for |
+|---|---|---|---|---|
+| key | Issue key | ID / identifier | number | Naming items |
+| title | Summary | Title | title | Naming items (required) |
+| status | Status | Status / state | state / Status | Bucketing (required) |
+| owner | Assignee | Assignee | assignees | Blocked owner, WIP by owner, unowned risks |
+| priority | Priority | Priority (names or 0–4) | Priority field or labels | Slipped High items, risk candidates |
+| resolved | Resolved | Completed / completedAt | closedAt | Shipped in period |
+| updated | Updated | Updated / updatedAt | updatedAt | Fallback for shipped; last update on blocked items |
+| due | Due date | Due date | a date field | Default plan |
+| sprint | Sprint | Cycle | milestone / Iteration | Plan with `--sprint` |
+| blocker | Blocked by, `Inward issue link (Blocks)`, `Custom field (Flagged)` | Blocked by | (label `blocked` + a note) | Blocker shown on blocked items |
+| labels | Labels | Labels | labels | A `blocked` label marks an item blocked |
+
+## Buckets
+
+| Bucket | Rule |
+|---|---|
+| Done | Status is Done, Closed, Resolved, Complete(d), Released, Shipped or Merged |
+| Dropped | Canceled, Duplicate, Won't Do, Won't Fix, Obsolete. Not counted as shipped, and removed from the plan |
+| Blocked | Status Blocked, On Hold, Impeded or Waiting; or a `blocked` label; or a value in the blocker column |
+| Not started | To Do, Backlog, Open, New, Triage, Ready, Selected for Development, Planned, Unstarted |
+| In progress | Anything else (In Progress, In Review, QA, …) |
+| Shipped in period | Done, with a resolved date inside `--from`..`--to` |
+
+If your workflow has other status names, check the script's bucket counts against the board
+before you trust them, and tell the user which statuses fell into "in progress" by default.
+
+## The plan
+
+"Slipped" only means something against a plan. The plan is the set of items that were meant
+to be done by the end of the period:
+
+| Source | Flag | Use when |
+|---|---|---|
+| A list of keys | `--plan-file plan.txt` | You have the sprint commitment or the list from last week's report |
+| A sprint, cycle or milestone | `--sprint "CHK Sprint 14"` | The sprint ends inside the reporting period |
+| Due dates | (default) | The team sets due dates; items due inside the period are the plan |
+
+Slipped = planned and not done by the period end. Plan completion = planned-and-done ÷ planned.
+Shipped work that wasn't in the plan is reported separately, never added to the completion
+rate. With no plan source the script says so, and the report must say "no plan to measure
+against" rather than implying the team is on track.
+
+## The RAG rule
+
+The script suggests a RAG status and prints every condition that fired:
+
+| Colour | Default condition | Flag |
+|---|---|---|
+| Red | Plan completion below 60% | `--red-below` |
+| Red | 2 or more planned items blocked | `--red-blocked` |
+| Amber | Plan completion below 85% | `--amber-below` |
+| Amber | Any planned item blocked | — |
+| Amber | Any High-or-above planned item slipped | — |
+| Green | None of the above | — |
+
+The highest colour that fired wins. If the team already has a RAG rule, set the thresholds to
+match it and say so. If the user wants to overrule the computed colour, report both: "Computed
+Red (completion 50%); reported Amber because …". Never change the colour without saying why.
+
+## What counts as a risk
+
+The script lists mechanical candidates: planned items that are blocked, planned items with no
+owner, and top-priority items not yet started. Add risks from the user's context (a fixed date,
+a dependency on another team), each with what it threatens and by when. A risk without a
+consequence is just a worry.
+
+## What counts as an ask
+
+An ask names who, what, and by when: "Platform team: a date for API-412 by Friday". Each ask
+should unblock a blocked item, staff an unowned one, or settle a priority. Without an owner and
+a date it's a wish.