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

ticket: record planning state coder delegation

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-08 17:38:47 +09:00
parent cb234b86ad
commit 109e991ffb
No known key found for this signature in database
2 changed files with 24 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-225448-replace-intake-state-with-planning/item.md
View File

@ -8,7 +8,7 @@ priority: P1
labels: [ticket, workflow-state, orchestrator, panel, intake, planning]
workflow_state: 'inprogress'
created_at: 2026-06-07T22:54:48Z
updated_at: '2026-06-08T08:37:22Z'
updated_at: '2026-06-08T08:37:56Z'
assignee: null
legacy_ticket: null
queued_by: 'workspace-panel'

23
.yoi/tickets/open/20260607-225448-replace-intake-state-with-planning/thread.md
View File

@ -159,3 +159,26 @@ Critical risks / reviewer focus:
Accepted queued implementation after reading the Ticket, workspace state, and workflow-state code map. This acceptance precedes worktree creation and coder/reviewer Pod spawning.
---
<!-- event: plan author: orchestrator at: 2026-06-08T08:37:56Z -->
## Plan
Implementation routing accepted and worktree created.
Worktree plan:
- Branch: `replace-intake-state-with-planning`
- Worktree: `.worktree/replace-intake-state-with-planning`
- Base: `cb234b8 ticket: route planning workflow-state replacement`
- Scope: replace user-facing workflow-state `intake` with planning terminology, remove standalone preflight/needs_preflight routing concepts, and update tests/docs/prompts/panel/tool behavior.
Delegation plan:
- Spawn sibling coder Pod with write scope limited to `.worktree/replace-intake-state-with-planning`.
- Coder should run commands from the child worktree; current live Orchestrator may not yet expose the newly merged `SpawnPod.cwd` schema until restart, so the task packet still includes explicit `cd` instructions.
- Coder must not edit main-workspace `.yoi` / Ticket / workflow / docs records, and must not create generated memory/local/runtime/secret-like files.
- Reviewer will be spawned read-only after coder reports diff/commits and validation evidence.
Stop/completion policy:
- Because the human authorized cleanup after completion, this Orchestrator will proceed through reviewer approval, merge-completion validation, Ticket close, Pod stop, worktree removal, and branch deletion if the branch is approved and merge authority remains clear.
---