prd.md 1.58 KB

Edit Raw Blame History


The graphlemon Work Node (planner) workflow completed successfully (1 agent, ~155s, 0 errors). It produced a PRD draft: "控制台导航栏「当前项目」上下文" — adding a persistent current-project context to the console nav bar across all pages except #/setup. Key points:


Nav bar shows the current project's name (fetched via existing GET /api/projects/:project_id), clickable to jump to #/projects for switching.
Adds a 4-bucket task status summary (done / running / pending / attention, mapping the 10 raw task statuses) next to the project name, computed client-side from GET /api/tasks?project_id=... — no new backend aggregation endpoint.
done/pending buckets link to #/tasks?status=<value> with the status filter pre-selected; running/attention (multi-status buckets) link to unfiltered #/tasks since v_task_board's filter is single-select (explicitly out of scope to change).
Requires a new capability in render() (frontend/app.js) to parse ?key=value query strings on hash routes — doesn't exist today.
Nav refresh piggybacks on the existing hashchange listener, no new event plumbing needed.
Flags docs/sdd/02-V-界面与交互.md's "导航栏右侧" section as stale (references v_project_setup instead of the actual v_project_list/#/projects mechanism) and calls out that follow-up doc sync as a required post-landing step.
Explicitly scopes out: WebSocket-pushed live refresh of the summary, multi-status filter UI, backend pagination.


No code was written — this is the Planner's PRD artifact, presumably feeding into a Coder task next.