From 9f35442a413c477b48f9a7ec7169541c230b262d Mon Sep 17 00:00:00 2001 From: Hare Date: Tue, 9 Jun 2026 09:06:32 +0900 Subject: [PATCH] ticket: route return-to-planning policy --- .../item.md | 4 +- .../thread.md | 60 +++++++++++++++++++ 2 files changed, 62 insertions(+), 2 deletions(-) diff --git a/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/item.md b/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/item.md index f5aa7e60..363b9c55 100644 --- a/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/item.md +++ b/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/item.md @@ -6,9 +6,9 @@ status: 'open' kind: 'task' priority: 'P1' labels: ['ticket', 'orchestrator', 'planning', 'workflow', 'prompt'] -workflow_state: 'queued' +workflow_state: 'inprogress' created_at: '2026-06-08T07:17:22Z' -updated_at: '2026-06-09T00:04:21Z' +updated_at: '2026-06-09T00:06:25Z' assignee: null queued_by: 'workspace-panel' queued_at: '2026-06-09T00:04:21Z' diff --git a/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md b/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md index 9b509eda..d517b0f4 100644 --- a/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md +++ b/.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md @@ -65,4 +65,64 @@ Intake refinement completed. Ticket has enough intent, acceptance criteria, bind Ticket を `workspace-panel` が queued にしました。 +--- + + + +## State changed + +Accepted queued implementation after reading the Ticket, current Orchestrator routing workflow guidance, workspace state, visible Pod/worktree state, and the recently merged orchestration-plan/tool changes. No active implementation worktree is present; the requested change is bounded to routing prompt/workflow guidance and tests/resources. + +--- + + + +## Decision + +Routing decision: implementation_ready + +Evidence checked: +- Ticket body and acceptance criteria for `orchestrator-return-to-planning-context-policy`. +- Current `.yoi/workflow/ticket-orchestrator-routing.md`, including existing `return_to_planning`, `implementation_ready`, and queued acceptance sections. +- Current workspace/worktree state after merging and cleaning up the previous TUI/composer work. +- Visible Pod state: no active sibling coder/reviewer for earlier work remains. +- Recent merged context: `replace-intake-state-with-planning`, `ticket-orchestration-plan-tool`, and queued-routing behavior already require explicit queued acceptance and durable evidence. +- `TicketOrchestrationPlanQuery` is documented in the workflow, but this current orchestrator session's tool list does not expose the newly merged tool, so there was no callable plan-query surface to inspect for this Ticket. + +Reason: +- The Ticket has concrete requirements and acceptance criteria. +- The change is policy/prompt/workflow guidance, not a broad runtime redesign. +- Current workflow text already contains some related clauses, so implementation should be a bounded tightening: make the evidence/context requirement explicit, ensure risky-but-specified Tickets can proceed, and add/adjust focused validation. + +IntentPacket: + +Intent: +- Strengthen Orchestrator routing guidance so returning ready/queued Tickets to `planning` requires concrete missing information/decision evidence after bounded project-context checks, not just Ticket text or risk flags. + +Binding decisions / invariants: +- Do not reintroduce a separate readiness/preflight state or lane. +- Do not change Ticket workflow states or transition semantics. +- Do not make every queued Ticket require broad repository archaeology. +- Risk flags and risky domains are context lookup and reviewer-focus signals, not automatic stop gates. +- If returning to planning, the routing record must include the concrete missing decision/information, context checked, why implementation latitude is insufficient, and the next planning question/action. +- If no concrete missing item remains after bounded context checks, a risky-but-specified Ticket should proceed as implementation_ready with IntentPacket invariants, escalation conditions, and reviewer focus. +- Keep the change in maintained routing workflow/prompt/resource docs and focused validation; avoid runtime scheduler/orchestration refactors. + +Implementation latitude: +- Coder may update `.yoi/workflow/ticket-orchestrator-routing.md`, resource prompts/workflows, and tests that validate workflow/prompt guidance. +- If there is no existing prompt-resource test harness, coder may add a narrow text validation test in the most appropriate existing crate, or document why focused grep/resource validation is the right evidence. +- Include or reference an example equivalent to `allow-spawnpod-child-workspace-cwd`: authority-adjacent but specified work should proceed with reviewer focus rather than return to planning solely because it touches authority/scope/Pod concerns. + +Escalate if: +- Implementation requires changing Ticket backend workflow_state semantics. +- Existing tests/resources imply a conflicting policy that must be resolved by human decision. +- A broad prompt/workflow templating redesign would be needed instead of a narrow guidance update. + +Validation: +- Focused workflow/prompt validation or tests covering: risky but specified Ticket -> implementation-ready; genuinely missing decision -> return to planning; risk flag alone is insufficient. +- `git diff --check`. +- `cargo run -q -p yoi -- ticket doctor`. +- `cargo check --workspace` if code/tests are touched. +- `nix build .#yoi` if resources/tests/package inputs are touched. + ---