codex-orchestrator 2.0.18 → 2.0.19

package/internal-workflow/skills/to-tickets/SKILL.md

@@ -15,7 +15,7 @@ ticket contains only its local observable outcome, scope, blockers, proof, and
 Parent link. The approved ticket body plus Parent PRD is the final execution
 authority; no later planning pass is inserted.
 
-`$to-tickets` owns complete whole-packet semantic review, one fresh final review
+`$to-tickets` owns complete whole-packet `$plan-review`, one fresh final review
 after any consolidated repair, one explicit user approval, serialized
 publication, reconciliation, and tracker read-back.
 
@@ -46,10 +46,6 @@ outcome and blocking relationship. Risk strengthens proof and review focus; it
 does not create tickets. Merge steps that share one owner, release, and
 validation path.
 
-Do not publish a child whose outcome is only transient evidence or a tracker
-comment. Resolve that discovery before compiling the executable graph, or make
-the required durable result a committed artifact.
-
 Where repository evidence proves a small prefactor is required, "Make the
 change easy, then make the easy change." Keep it inside the same vertical
 outcome unless it is independently verifiable and genuinely blocks later work.
@@ -145,12 +141,12 @@ an explicit blocking discovery outcome. The expected review verdict must be
 
 ### 4. Run one fresh semantic packet review
 
-After the complete packet satisfies the freeze conditions, launch exactly one
-fresh `standards_reviewer` without history
+After the complete packet satisfies the freeze conditions, invoke
+`$plan-review` with exactly one fresh `plan_reviewer` without history
 (`fork_context=false` on V1; `fork_turns="none"` on V2). Begin with
-`Assigned role: standards_reviewer`, provide the full authority and packet, and
-apply all three lenses in the same activation: source fidelity, ticket
-executability, and minimum solution and scope conservation.
+`Assigned role: plan_reviewer`, provide the full authority and packet, and apply
+all three lenses in the same activation: source fidelity, ticket executability,
+and minimum solution and scope conservation.
 
 - **Source fidelity:** every product claim, decision, scope boundary,
   consequence, and blocker is grounded in the source; no behavior or ownership
@@ -193,17 +189,21 @@ whole-packet review and must not stop after representative findings. Capture a
 non-empty fresh child identity and wait for that same child. Do not split the
 lenses across children and do not launch the delivery Standards review.
 
-After `NEEDS_WORK`, repair all verified blockers together and sweep the
-complete packet for every defect class they expose. Do not review intermediate
-repair edits. If a blocker exposes unfinished inventory, authority, or
-composition, return to drafting and pass the freeze conditions again. Once the
-complete revised packet satisfies the freeze conditions, launch one fresh
-final whole-packet reviewer without prior review history. A same-context or
-findings-only recheck cannot approve. Further review is justified only by a
-remaining material blocker; optional hardening, broader proof, stylistic
-refinement, or requirements without authority do not reopen the review cycle.
-Missing or failed review blocks publication; product-changing repairs return
-to the user.
+When review returns a plan-changing `QUESTION`, return it through Plan to the
+user and stop without revising or publishing the packet. Resume only after the
+answer becomes authority and the complete packet is settled again.
+
+After `NEEDS_WORK` with verified blockers, repair all blockers together and
+sweep the complete packet for every defect class they expose. Do not review
+intermediate repair edits. If a blocker exposes unfinished inventory,
+authority, or composition, return to drafting and pass the freeze conditions
+again. Once the complete revised packet satisfies the freeze conditions,
+launch one fresh final whole-packet `plan_reviewer` without prior review
+history. Use one fresh reviewer per settled revision; a same-context recheck
+cannot approve. Further review is justified only by a remaining material
+blocker; optional hardening, broader proof, stylistic refinement, or
+requirements without authority do not reopen the review cycle. Missing or
+failed review blocks publication; product-changing repairs return to the user.
 
 ### 5. Get one explicit approval
 

package/internal-workflow/skills/to-tickets/evals/evals.json

@@ -128,6 +128,31 @@
       "prompt": "UI acceptance requires dynamic content absent from the proposed API or DTO.",
       "expected": ["reject the packet until an existing or authorized data contract supplies the content"],
       "forbidden": ["let the UI invent the data", "add a new owner solely for proof"]
+    },
+    {
+      "id": "final-packet-uses-plan-review-once",
+      "prompt": "Compile an approved PRD into a complete publish-ready Parent and multi-ticket packet.",
+      "expected": [
+        "do not review the intermediate PRD",
+        "invoke one fresh plan-review over the complete frozen packet",
+        "cover source fidelity, ticket executability, and minimum solution in that review"
+      ],
+      "forbidden": [
+        "invoke standards_reviewer for planning review",
+        "review both the PRD and final packet"
+      ]
+    },
+    {
+      "id": "plan-review-question-returns-to-user",
+      "prompt": "The final packet review raises an unresolved ownership question but finds no verified blocker.",
+      "expected": [
+        "return the question through Plan to the user",
+        "resume only after the answer becomes authority and the packet is settled again"
+      ],
+      "forbidden": [
+        "guess the answer",
+        "repair or publish the packet"
+      ]
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-orchestrator",
-  "version": "2.0.18",
+  "version": "2.0.19",
   "description": "Reusable GitHub Issues runner for Codex.",
   "type": "module",
   "license": "MIT",