@kaddo/cli 3.57.0 → 3.58.0

package/dist/index.js

@@ -2232,6 +2232,8 @@ validation (how to test it), definition of done, open questions and dependencies
 - Do not expand scope without explicit confirmation.
 - Do not create mega Work Items \u2014 split when it covers multiple outcomes.
 - Keep acceptance criteria testable.
+- This skill refines scope and acceptance criteria but does not approve implementation readiness.
+  Readiness requires human confirmation through \`kaddo ready\` or the MCP \`mark_work_item_ready\` action.
 
 ## Quality checklist
 
@@ -2637,9 +2639,9 @@ var RESPONSIBILITY_MATRIX = {
     agent: "work-item-agent",
     responsibleFor: ["Work Item refinement"],
     produces: ["knowledge/delivery/work-items/"],
-    canSuggest: ["implementation-agent"],
+    canSuggest: ["kaddo ready", "mark_work_item_ready", "implementation-agent"],
     cannotSuggest: ["branches", "commits", "pull requests", "code"],
-    next: ["implementation-agent"]
+    next: ["kaddo ready (human review)", "implementation-agent"]
   },
   "implementation-agent": {
     agent: "implementation-agent",
@@ -3652,7 +3654,16 @@ and \`blocked\` as active work; \`completed\` and \`archived\` are historical kn
 
 ## Handoff
 
-When the Work Item is refined and ready to build, **hand off to the implementation-agent**.
+After refining a Work Item, **do not mark it ready automatically**. If the Work Item appears
+complete (acceptance criteria, validation, code globs, domains all present, open questions
+resolved), recommend human review and the ready transition:
+
+- **CLI:** \`kaddo ready <WI-ID>\`
+- **MCP:** \`mark_work_item_ready({ id: "<WI-ID>" })\`
+
+The transition to \`ready\` requires explicit human confirmation. Only after a human marks the
+Work Item as ready should it be handed off to the implementation-agent.
+
 You do **not** suggest branches, commits or pull requests \u2014 implementation (including any Git
 branch suggestion) is the implementation-agent's responsibility, and only by respecting the
 project Git strategy. Your job ends at a clear, traceable Work Item that **states how to test it**.
@@ -8904,6 +8915,7 @@ function buildDeliveryState(dir) {
   return {
     phase: "",
     draft_work_items: byState("draft"),
+    refined_draft_work_items: wis.filter((w) => w.lifecycle === "draft" && w.rawFrontmatter.refined_by).length,
     ready_work_items: byState("ready"),
     in_progress_work_items: byState("in-progress"),
     blocked_work_items: byState("blocked"),
@@ -9031,6 +9043,17 @@ function resolveNextStep(dir, now = /* @__PURE__ */ new Date()) {
   const secondary = buildSecondaryRecommendations(st);
   const roadmap = roadmapSignal(dir);
   if (roadmap !== "has-candidates" && st.draft_work_items > 0) {
+    if (st.refined_draft_work_items > 0) {
+      return {
+        id: "review-work-item",
+        phase: "Active Delivery",
+        label: "Review the refined draft Work Item and mark it ready with `kaddo ready`.",
+        command: "kaddo ready",
+        mcpAction: "kaddo_mark_work_item_ready",
+        reason: `There ${st.refined_draft_work_items === 1 ? "is" : "are"} ${st.refined_draft_work_items} refined draft Work Item${st.refined_draft_work_items === 1 ? "" : "s"} awaiting human review.`,
+        ...secondary.length ? { secondary } : {}
+      };
+    }
     return {
       id: "refine-work-item",
       phase: "Active Delivery",
@@ -9836,7 +9859,8 @@ function mapNextStepId(id) {
     "refine-product": "define-product",
     "refine-capabilities": "discover-capabilities",
     "refine-current-state": "describe-architecture",
-    "refine-codebase": "describe-architecture"
+    "refine-codebase": "describe-architecture",
+    "review-work-item": "refine-work-item"
   };
   return MAP[id] ?? id;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kaddo/cli",
-  "version": "3.57.0",
+  "version": "3.58.0",
   "description": "Knowledge Driven Development toolkit",
   "license": "MIT",
   "repository": {