skilldrop-cli 0.9.0 → 0.9.2

package/skills/user-story-splitter/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Split this epic into user stories",
+    "should_trigger": true
+  },
+  {
+    "query": "Break this feature down into independently shippable slices",
+    "should_trigger": true
+  },
+  {
+    "query": "Turn this PRD section into stories with Gherkin acceptance criteria",
+    "should_trigger": true
+  },
+  {
+    "query": "What's the right build order for these stories?",
+    "should_trigger": true
+  },
+  {
+    "query": "Write the product requirements document for this feature",
+    "should_trigger": false
+  },
+  {
+    "query": "Write the test plan covering these acceptance criteria",
+    "should_trigger": false
+  },
+  {
+    "query": "Plan the phased rollout of this schema change",
+    "should_trigger": false
+  },
+  {
+    "query": "Turn this bug report into an actionable ticket",
+    "should_trigger": false
+  }
+]

package/skills/user-story-splitter/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill_name": "user-story-splitter",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Split this epic into shippable stories: 'Customers can save their cart, return later on any device, and check out with a saved payment method.'",
+      "assertions": [
+        "Every story is demoable to a non-engineer — a story whose demo is 'look at this database table' is re-cut as a vertical slice",
+        "Every acceptance criterion is pass/fail without interpretation and written in Gherkin",
+        "Acceptance criteria are concrete enough that a tester who has not seen the epic can verdict them",
+        "Dependencies between stories are stated, and a recommended build order follows from them",
+        "Stories are independently shippable rather than layered horizontally (all backend, then all frontend)"
+      ]
+    }
+  ]
+}