Approve a PRD laid out from one structured document #2

Closed
opened 2026-10-27 13:34:12 +00:00 by sam · 0 comments
Owner

The feasibility prd step returns the PRD as structured fields (title, problem, solution, files, acceptance, non_goals, diff_estimate, risks). human.approve takes them as its document: the plan text (approval message, forge, implement mission) and the approval card's layout are both rendered from it, so what is approved is what implement is handed. Replaced a separately generated OpenUI view, which could drift from the plan.

Acceptance criteria

A feasibility run's approval card lays out the PRD's fields; its plan text carries the same content; a task without a document shows its plan text.

Notes

Landed in the commit replacing 18191531. Verified: table test for human.approve's document, every shipped workflow parses, card renders and falls back in headless Chromium (scratch harness). Not yet verified: a live feasibility run. Close after that run.

Close reason

Feature is in the tree and covered: workflow.approve renders plan text and stores plan_document from the prd result (control_steps.go, plan_document.go), PlanDocument.vue lays out the fields with plan-text fallback, shipped feasibility.yaml wires document: {{ steps.prd.result }} -> implement, and TestApprovePlanDocument + shipped-definition parse test pass; the remaining 'live feasibility run' is a manual e2e check, not missing code.


Imported from beads archie-core-11uab.1 · GitHub #1849 · type feature · priority P3 · created 2026-10-25 · closed 2026-10-27

The feasibility prd step returns the PRD as structured fields (title, problem, solution, files, acceptance, non_goals, diff_estimate, risks). human.approve takes them as its document: the plan text (approval message, forge, implement mission) and the approval card's layout are both rendered from it, so what is approved is what implement is handed. Replaced a separately generated OpenUI view, which could drift from the plan. ### Acceptance criteria A feasibility run's approval card lays out the PRD's fields; its plan text carries the same content; a task without a document shows its plan text. ### Notes Landed in the commit replacing 18191531. Verified: table test for human.approve's document, every shipped workflow parses, card renders and falls back in headless Chromium (scratch harness). Not yet verified: a live feasibility run. Close after that run. ### Close reason Feature is in the tree and covered: workflow.approve renders plan text and stores plan_document from the prd result (control_steps.go, plan_document.go), PlanDocument.vue lays out the fields with plan-text fallback, shipped feasibility.yaml wires document: {{ steps.prd.result }} -> implement, and TestApprovePlanDocument + shipped-definition parse test pass; the remaining 'live feasibility run' is a manual e2e check, not missing code. --- _Imported from beads `archie-core-11uab.1` · GitHub #1849 · type feature · priority P3 · created 2026-10-25 · closed 2026-10-27_
sam self-assigned this 2026-10-27 13:34:12 +00:00
sam closed this issue 2026-10-27 13:34:12 +00:00
sam added the lowfeature labels 2026-11-12 15:51:27 +00:00
sam added a new dependency 2026-11-14 14:45:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#2