Repository navigation
docs(rfc): conductor skips the in-chat task board on a board tab - #18620
Conversation
|
@bolichen97 could you take a look when you have a moment? This RFC narrows the Crew Mode milestone rule you added in #16088, so it needs your on-record OK before it lands. The reason comes from Crew Mode users: the conductor's Dashboard tab (goal-board / work-kanban) already draws the full task board, live from the work ledger, so the full in-chat "Task board" at every milestone shows every task twice. What stays the same:
Section 5 explains why I read this as keeping your 2026-10-02 decision (the tab is the live board). The review lanes read it as a narrowing that needs a superseding entry. If you agree with the change, a short "OK" here is enough, and I will add that superseding decision entry citing your comment. If you would rather keep the in-chat board everywhere, I will close both PRs. Thank you. |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS The RFC decides for itself that it fits Bolin Chen's recorded decision ("reports with a live task board … in every chat"), yet narrows that rule without the maintainer signing off. Watch
[DESIGN-REVIEWED] abc9aea Description read[DESCRIPTION-READ] bf7aaa9dc4ec33c75dc8fb122e6ed1646d9f0073c120f96b0349797a07622367 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
6c8d4ca to
abc9aea
Compare
|
Note for reviewers, from the user who raised this: the point is to NOT GENERATE the board, which saves output tokens, not to hide one after it is drawn. The rule is a generation-time rule in the conductor prompt. On a board tab (goal-board / work-kanban) the model never writes the "Task board" widget or the task-dashboard artifact, so there is no client-side suppression, filter or hide anywhere. The motivation is both costs: the reader sees every task twice, and each milestone spends output tokens on a widget plus an artifact update the tab already shows. Section 3 now says this explicitly (head abc9aea). The intro widget and the "Needs you" line stay. Still waiting on @bolichen97's on-record OK before the implementation (#18608) moves. |
|
This is a RFC doc, also synced offline about this change to avoid duplicate dashboard. |
Problem / Motivation
Goal: Record the decision that a conductor whose Dashboard tab shows the task board stops drawing a second full copy of it in the chat, so its implementation can land.
The First Principles lane blocked #18608 as a product-shape change with no RFC on the base branch: it changes what
kirocrew-conductordraws in chat by default on one surface. Crew Mode users reported the in-chat "Task board" at every milestone as a duplicate of the Dashboard tab'sgoal-board.Why it matters
Without the decision on main the implementation cannot pass First Principles, and Crew Mode chats keep repeating a full table the reader already has one tab away.
Not a goal
docs/decisions/2026-10-02-conductor-introduces-itself-in-every-chat.md; section 5 of the RFC explains why the change keeps it.What changed (motivation → approach → change)
docs/request-for-change/rfc-conductor-chat-board-on-tab.md: the RFC, statusin-progress, implementation #18608. It states the problem, the two-branch rule (keyed on the[DASHBOARD]block naminggoal-board/work-kanban), why "a block exists" is the wrong key (project-reportfallback), thetask-dashboardartifact disposition, risks, and how it squares with Bolin Chen's recorded decision.docs/request-for-change/README.md: one index row.@bolichen97 — this records a change to the Crew Mode milestone rule you added in #16088. Your review is requested.
Backwards compatibility
Compatible: documentation only.
Removes nothing: adds one RFC file and one index row.
Tests
N/A — docs only;
scripts/docs-lint.shpasses locally.Manual verification
N/A — docs only.
Related Issues
Implementation: #18608. Follows #16088.
Checklist
Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.