Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: record return planning implementation

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-09 09:20:08 +09:00
parent 03c3218dc7
commit 427a919077
No known key found for this signature in database
2 changed files with 35 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/item.md
View File

@ -8,7 +8,7 @@ priority: 'P1'
labels: ['ticket', 'orchestrator', 'planning', 'workflow', 'prompt']
workflow_state: 'inprogress'
created_at: '2026-06-08T07:17:22Z'
updated_at: '2026-06-09T00:07:10Z'
updated_at: '2026-06-09T00:19:47Z'
assignee: null
queued_by: 'workspace-panel'
queued_at: '2026-06-09T00:04:21Z'

34
.yoi/tickets/open/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md
View File

@ -147,3 +147,37 @@ Routing context:
- This Ticket is now the active routed implementation work.
---
<!-- event: implementation_report author: orchestrator at: 2026-06-09T00:19:47Z -->
## Implementation report
Coder implementation completed and is ready for sibling review.
Coder Pod:
- `coder-orchestrator-return-to-planning-context-policy`
- Commit: `8576615 workflow: tighten orchestrator planning return policy`
- Worktree status before review: clean branch `orchestrator-return-to-planning-context-policy`
- Stopped after collecting output to reclaim delegated worktree scope.
Implementation summary:
- Tightened Orchestrator routing workflow so returning `ready` / `queued` Tickets to `planning` requires concrete missing decision/information evidence after bounded project-context checks.
- Clarified risk flags / risky domains / authority-adjacent work as context lookup, IntentPacket invariant, reviewer-focus, and escalation signals rather than automatic stop gates.
- Added risky-but-specified guidance and an `allow-spawnpod-child-workspace-cwd`-style example for proceeding with reviewer focus when work is specified.
- Updated related planning/preflight and multi-agent workflow wording plus work-item docs.
Changed files:
- `.yoi/workflow/ticket-orchestrator-routing.md`
- `.yoi/workflow/ticket-preflight-workflow.md`
- `.yoi/workflow/multi-agent-workflow.md`
- `docs/development/work-items.md`
Coder validation reported passed:
- Focused workflow/prompt text validation for risky-but-specified -> implementation_ready, genuinely missing decision -> return_to_planning, and risk flag alone insufficient.
- `git diff --check`
- `cargo run -q -p yoi -- ticket doctor`
- `nix build .#yoi`
Coder did not run `cargo check --workspace` because only docs/workflow resources changed.
---