Repository navigation
docs: add rfc for crewmate guides, change cards and mate - #18326
Conversation
Record the product owner's 2026-10-08 decision, taken after the team review, so the First Principles lane can read it from the base branch when #18301 and #18317 change default mounts and first-visit landing. Part 1: one read-or-offer MCP server, kirocrew-guide, mounted for the kirocrew template, its crewmates, worker and dashboard sessions. Guides highlight the real control and change cards apply only on the user's press, from a dashboard turn the user sent; trust-root areas are answered in words only. Part 2: Kiro Crew creates one ordinary crewmate, Mate, once. It opens first on the Crewmates page while never chatted with, writes its own welcome, and renames itself through rename_self. default stays the shared fallback crew. The document amends sections of rfc-crewmates-launch, rfc-crewmate-greeting and rfc-crewmates-chatted-list rather than editing those accepted documents. The index gains its row and audit note.
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
dc0f5a2 to
b623320
Compare
Design Review (Opus 5.5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS The RFC makes Mate's model-written kickoff the first thing a new user sees on the Crewmates page, but says nothing about what happens when that model turn fails. Watch
[DESIGN-REVIEWED] b623320 Description read[DESCRIPTION-READ] 209f0f7b04dcc9e0741eb93644765d0be6566bd9abf14191c41af717b8585c13 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 |
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: |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Opus 5.5 Review — ✅ no blocking findingsReviewed Review detailsOne advisory finding, no merge block: the RFC's list of managed MCP servers leaves one out. FINDING — docs/request-for-change/rfc-crewmate-guides-and-mate.md:180 — the "Exists today" bullet says [OPUS-REVIEWED] b623320 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: Record the product decision behind #18301 and #18317 on main, so their First Principles review can read it from the base branch.
#18301 (platform guides and change cards) and #18317 (Mate, a first crewmate) change product shape: a default-mounted guide server, a crewmate Kiro Crew creates for everyone, a new first landing on the Crewmates page, and a model-written first welcome. The accepted crewmate RFCs say otherwise in places, so both PRs are blocked on "product-shape change without accepted RFC".
Why it matters
Without this record on main, both implementation PRs stay blocked, and the next reader of the crewmate RFCs would find decisions that no longer describe the product.
Not a goal
What changed (motivation → approach → change)
A new RFC,
docs/request-for-change/rfc-crewmate-guides-and-mate.md, statusaccepted, records the product owner's decision of 2026-10-08 after the team review:kirocrew-guideMCP server that only reads or offers. Default-mounted for thekirocrewtemplate, its crewmates, worker and dashboard sessions; granted by exact tool name under the governance ceiling. Change cards apply only on the user's press; widening cards also need an acknowledgement tick. Trust-root areas are answered in words only. Only a dashboard turn the user sent may start a guide or a card. The rules live in tool text, not in an agent prompt.rename_self.defaultstays the shared fallback crew and is listed only once its thread has a message.rfc-crewmates-launch.md(§4 screens 02 and 08),rfc-crewmate-greeting.md(§6) andrfc-crewmates-chatted-list.md(§3 landing order), and lists the rejected alternatives.docs/request-for-change/README.mdgains the index row and an audit sentence.Backwards compatibility
Compatible: documentation only; no code, config or on-disk format changes.
Tests
scripts/docs-lint.shpasses.Manual verification
N/A -- documentation only. Each "Exists today" claim was checked against main at
4f9c5697b9.Screenshots / video
Why no screenshot: documentation only; no UI change.
Related Issues
Part of #18300
Part of #18315
Pattern harvest
Not generalizable: a docs-only PR.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement