@jesdi/skills 0.0.8 → 0.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jesdi/skills",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "description": "jesdi's agent skills (content package consumed by @jesdi/skills-cli)",
   "license": "MIT",
   "repository": {

package/skills/backlog/SKILL.md

@@ -71,6 +71,17 @@ these labels (`setup` provisions them all) — never invent new ones.
 | `testing` | Test coverage, test infrastructure, flaky tests |
 | `dependencies` | Upgrading or managing third-party dependencies |
 
+**Pipeline — at most one, orthogonal to Type and Area:**
+
+Whether an issue is ready for an unattended agent to pick up. Leave both off
+when it is genuinely unclear — an unlabelled issue is simply not routed, which
+is the safe default. Dispatchers filter on `auto`; nothing else reads these.
+
+| Label | Apply when |
+|-------|-----------|
+| `auto` | Trivial, or close enough to previously automated work — suitable for the unattended agents pipeline |
+| `human-required` | Substantial fog of war remains; needs heavy human interaction before an agent can take it |
+
 ## `setup` — create the board once (idempotent)
 
 Run when `.backlog/project-meta.json` is absent or the board is being
@@ -81,7 +92,7 @@ dir.
 1. Ensure the `project` scope: `gh auth status`; if Projects calls 403, run
    `gh auth refresh -s project`.
 2. Follow `references/graphql.md` → **Setup**: create the Project, link the repo,
-   add the six fields, create the `inbox` label plus the 12 taxonomy labels
+   add the six fields, create the `inbox` label plus the 14 taxonomy labels
    (idempotent — `--force` reconciles color/description on re-runs). On a
    brand-new board the `Area`
    single-select is created with the generic default options

package/skills/backlog/references/graphql.md

@@ -47,6 +47,9 @@ gh label create security --repo <repo> --description "Vulnerabilities, auth, per
 gh label create performance --repo <repo> --description "Speed, memory, efficiency, scalability" --color f9d0c4 --force
 gh label create testing --repo <repo> --description "Test coverage, test infrastructure, flaky tests" --color 0e8a16 --force
 gh label create dependencies --repo <repo> --description "Upgrading or managing third-party dependencies" --color 0366d6 --force
+# Pipeline labels (at most one per issue; read by dispatchers)
+gh label create auto --repo <repo> --description "Suitable for the unattended agents pipeline" --color 5319E7 --force
+gh label create human-required --repo <repo> --description "Needs heavy human interaction before automation" --color B60205 --force
 
 # 5. Discover IDs to build .backlog/project-meta.json
 gh project view <projectNumber> --owner <owner> --format json   # -> id (projectId)

package/skills-manifest.json

@@ -1,11 +1,11 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-07-29T09:24:37.867Z",
+  "generatedAt": "2026-07-31T14:48:08.872Z",
   "skills": [
     {
       "name": "backlog",
-      "version": "0.1.5",
-      "hash": "sha256-427fff6fc5005849a85e750568940b52375c823a9ad26b1827890dc0cabab499",
+      "version": "0.1.6",
+      "hash": "sha256-89423260dd0d35ceb16f536c1c3bd0e5fc43a30f36861e301a7a807351645582",
       "description": "Manage a GitHub-Issues-backed backlog and a Projects-v2 work graph via five verbs. Use when the user wants to CAPTURE an idea/research thread (\"add to backlog\", \"capture this\", \"note this idea\", \"log a task\"), TRIAGE the inbox (\"triage the backlog\", \"score the inbox\"), see what to work on NEXT (\"what's next\", \"what should I work on\", \"ranked backlog\", \"next actionable task\"), LAND a finished item (\"mark done\", \"close out #N\"), or SETUP the board the first time. Ranks open issues by impact÷effort, respecting `Blocked by:` edges, so only actionable work surfaces."
     },
     {