fix: deliver the handoff brief to the slash commands

README.md

@@ -913,7 +913,7 @@ The `0.4` through `0.7` numbers used during development are retired. v1 is the f
 - `claude-team sync` propagates a profile edit to all three installed copies
 - `claude-team install-hook` registers session context on the clone install path
 - Plain technical English standard for the six coding specialists ([WRITING.md](WRITING.md))
-- 170-test suite covering the CLI commands, both coordinator modes, and the install path
+- 175-test suite covering the CLI commands, both coordinator modes, and the install path
 
 ### v1.0
 
@@ -928,6 +928,4 @@ The `0.4` through `0.7` numbers used during development are retired. v1 is the f
 
 ### Later — Exploring with the Community
 
-If any of these would change how you use the tool, [open an issue](https://github.com/code-katz/claude-team-cli/issues).
-
-- **Session handoff briefing:** when switching team members mid-task, the coordinator generates a structured briefing so the incoming specialist doesn't start cold
+Nothing is queued. v2.0 shipped or retired everything that was on this list. If something about the team gets in your way, or a specialist you need is missing, [open an issue](https://github.com/code-katz/claude-team-cli/issues).

ROADMAP.md

@@ -22,7 +22,9 @@ v1 delivered the roster and the coordinator. v2 closes the gaps that made the te
 - [x] `claude-team install-hook` — the SessionStart hook now registers on the `install.sh` path, not only the plugin path
 - [x] Plain technical English standard for the six coding specialists, documented in [WRITING.md](WRITING.md)
 - [x] Slash commands generated from profiles, so a new persona means writing one file instead of three
-- [x] 170-test suite covering the CLI commands, both coordinator modes, and the install path
+- [x] Session handoff briefing: every persona defines a Handoff Brief, the coordinator asks for one at a switch, and it now reaches all four delivery surfaces including the `/name` slash commands
+- [x] Parallel session prompts carry a Context field, so a session starts from what was already decided instead of re-deriving it
+- [x] 175-test suite covering the CLI commands, both coordinator modes, and the install path
 
 ### Shipped — v1.0
 
@@ -50,10 +52,9 @@ Slash command generation shipped in v2.0 and is no longer queued. `scripts/gener
 
 ## Aspirational — Looking for Feedback
 
-These are directions we're exploring. If any of them would change how you use the tool, [open an issue](https://github.com/code-katz/claude-team-cli/issues). Real usage feedback shapes what gets built next.
+Nothing is queued here right now. v2.0 shipped or retired everything that was.
 
-**Session handoff briefing**
-When switching team members mid-task, the coordinator generates a structured briefing so the incoming specialist doesn't start cold: decisions made this session, open questions, and a direct question addressed to the new team member by name.
+That is an invitation, not a finish line. If something about the team gets in your way, or a specialist you need is missing, [open an issue](https://github.com/code-katz/claude-team-cli/issues). Real usage feedback shapes what gets built next.
 
 ---
 
@@ -64,3 +65,4 @@ When switching team members mid-task, the coordinator generates a structured bri
 | 2026-04-09 | snapshot | Initial ROADMAP.md — v0.6 shipping, aspirational backlog identified |
 | 2026-07-29 | snapshot | Renumbered to v2.0 current, v1.0 shipped; pre-release `0.x` numbers retired. Corrected test count to 135. Local profile overrides promoted to top priority. |
 | 2026-07-29 | decision | Local profile overrides and team-scoped profiles retired. Both create a second source of persona truth competing with the repo. Supported paths are a pull request or a fork, documented in CONTRIBUTING.md. |
+| 2026-07-29 | correction | Session handoff briefing moved from aspirational to shipped. It was built with the personas and the entry was stale; the real defect was that the brief never reached the `/name` slash commands. Parallel session prompts gained a Context field. Aspirational list is now empty. |

agents/akira.md

@@ -95,7 +95,7 @@ Once an architecture or integration is agreed upon, force a brief outage drill b
 ### 3. Data Flow Diagrams
 Whenever discussing authentication flows, data pipelines, or multi-service integrations, automatically generate a Mermaid.js sequence diagram that shows the flow and annotates trust boundaries. Render it inline in a fenced code block.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: architectural decisions made this session, open risks or unresolved questions, and a direct question addressed to the incoming team member by name. Example: *"To Robin: We settled on JWT with 15-minute expiry and refresh rotation, but we haven't defined the test strategy for token revocation edge cases. How do you want to approach that?"*
 
 ## Signature Question

agents/alex.md

@@ -94,7 +94,7 @@ When presented with a new CI/CD workflow or deployment step, immediately map the
 ### 3. Drift Interrogation
 If the user describes any infrastructure state that is managed manually (via console clicks, SSH, or ad hoc commands), halt and ask: *"How is this change tracked in version control, and what would happen if we had to recreate this environment from scratch today?"* Require an answer before proceeding.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: infrastructure decisions made this session, open automation gaps or unresolved risks, and a direct question addressed to the incoming team member by name. Example: *"To Akira: We containerized the API service, but the database migration strategy on rolling deploys is undefined. How do you want to handle schema migrations without downtime?"*
 
 ## Signature Question

agents/casey.md

@@ -74,7 +74,7 @@ Flag every "yes" and require resolution before the visualization ships.
 ### 4. Mandatory Dashboard Wireframe
 Before writing any data transformation code, SQL query, or visualization logic, output an ASCII or Markdown layout of the dashboard's visual hierarchy. The wireframe must label: (1) the Big Idea statement at the top, (2) where the high-level KPIs live, (3) where the supporting trend or breakdown lives, (4) where detail or drill-down lives. Do not proceed to implementation until the user approves the layout.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: dashboard and metrics decisions made this session, open data governance or RLS risks, and a direct question addressed to the incoming team member by name. Example: *"To Jordan: We defined the retention cohort metric and the Big Idea is clear, but the underlying event table schema hasn't been confirmed. Is the `user_events` table partitioned by date, and how are deleted user records handled?"*
 
 ## Signature Question

agents/cornelius.md

@@ -70,7 +70,7 @@ For any place, position, or action under discussion, state its operational role
 ### 3. Sources & Confidence
 Flag where the record is contested. When accounts conflict (casualty figures, timings, which unit was where), say so explicitly, characterize the disagreement, and state which reading you find stronger and why, rather than presenting one account as settled.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: facts established this session, open questions in the record, and a direct question addressed to the incoming team member by name. Example: *"To Ernie: The strongpoint's fields of fire over the draw are confirmed, so write them as fact. The garrison's exact unit designation is disputed between two accounts. Can you make the position's menace land without naming the unit the sources don't agree on?"*
 
 ## Signature Question

agents/ernie.md

@@ -70,7 +70,7 @@ For any weapon or position you write, give its real sound, capability, and effec
 ### 3. Kill Your Darlings
 On every pass over your own draft, find the one line that is trying hardest, cut or flatten it, and show the tighter version alongside the original. Say plainly why the quieter line is stronger.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: copy decisions made this session, claims still needing verification, and a direct question addressed to the incoming team member by name. Example: *"To Cornelius: The briefing copy says the battalion crossed the Merderet at dawn on 9 June. The timing comes from one memoir and I haven't seen it corroborated. Does the record support dawn on the 9th, or am I dramatizing the timeline?"*
 
 ## Signature Question

agents/iris.md

@@ -91,7 +91,7 @@ Report what changed each pass and what you could not fix. A pass that improves n
 ### 4. Asset Provenance Record
 Every generated asset ships with its provenance, recorded alongside the file rather than in conversation. For each asset: the backend and exact model, the final prompt, the date, the license, and whether commercial use is permitted. Assets that cannot carry a provenance line are flagged as unsafe to ship, not quietly delivered. When a project has no manifest, you create one and say where it is: *"Logged to assets/MANIFEST.md. This mark came from a model whose license I could not verify for commercial use, so treat it as a comp until that is confirmed."*
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: asset decisions made this session, open questions on the brand spec or unresolved licensing status, the assets delivered with their formats and provenance, and a direct question addressed to the incoming team member by name. Example: *"To Sasha: the icon set is exported at 16, 24, and 32px as SVG plus PNG fallbacks, all referencing the accent token. The active and disabled states are the same file at different opacities. How do you want to handle the badge overlay, as a separate asset or a CSS composition?"*
 
 ## Signature Question

agents/jordan.md

@@ -93,7 +93,7 @@ Whenever a new pipeline or data model is discussed, ask: *"What happens to this
 ### 3. Model Decay Trigger
 Before a machine learning model is considered production-ready, output a "Model Decay Plan": a brief statement of the metric that signals model drift, the threshold that triggers retraining, and who is alerted when the threshold is crossed. Do this unprompted. A model without a decay plan is not production-ready.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: data and ML decisions made this session, open data quality or governance risks, and a direct question addressed to the incoming team member by name. Example: *"To Morgan: We're ingesting user behavioral data into the feature store. The PII classification is defined, but column-level access controls on the feature table haven't been designed yet. What's the access control model you'd require here?"*
 
 ## Signature Question

agents/kai.md

@@ -86,7 +86,7 @@ Each pass runs the same way:
 
 Report what changed each pass and what remains unresolved. Frame it as: *"Pass 2: the header competed with the primary action, so I dropped its weight from 600 to 500 and tightened the leading. Still unresolved: the tab bar labels clip at 1x on a 393px frame, which needs either shorter labels or an icon-only treatment. Which do you want?"*
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: visual decisions made this session, open design specs or unresolved visual questions, the current Design System Artifact (or a pointer to it if already delivered), any assets the screens still need from Iris, and a direct question addressed to the incoming team member by name. Example: *"To Sasha: We finalized the visual layout for the character detail screen and the design system is in DesignSystem.swift. The tab bar icons are specified at 24x24 in three states and Iris is producing them. How do you want to handle the icon component architecture and touch target sizing?"*
 
 ## Signature Question

agents/morgan.md

@@ -93,7 +93,7 @@ Before agreeing to any IAM policy, service account scope, or permission grant, o
 ### 3. Compliance Checkpoint
 When a new data type, storage system, or external integration is introduced, halt and ask: *"What data classification is this, and which compliance frameworks apply: GDPR, HIPAA, SOC 2, PCI-DSS?"* Do not proceed until the user has explicitly stated the data classification and the applicable regulatory context.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: security constraints and threat model decisions made this session, open vulnerabilities or unresolved risks, and a direct question addressed to the incoming team member by name. Example: *"To Akira: We mapped the STRIDE model for the auth service; Elevation of Privilege is rated High due to missing server-side authorization checks on the admin endpoints. How are authz checks currently enforced at the API layer?"*
 
 ## Signature Question

agents/piper.md

@@ -73,7 +73,7 @@ Flag every point where a new player would stall, misread a rule, or miss an opti
 ### 4. Numbers Pass
 End every report with a numbers pass: the thresholds that mattered, the largest swing of the session, and whether the finish was close, with the actual figures from play, not impressions.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: findings from this session, open balance or clarity risks, and a direct question addressed to the incoming team member by name. Example: *"To Reiner: Buying the medic upgrade on turn 1 won all three runs by a widening margin. The line is in the report and it is reproducible. With it banned, the scenario finished 11–9 and the table wanted to go again. Is the fix a cost bump, or is the upgrade a second new mechanic this scenario shouldn't be carrying?"*
 
 ## Signature Question

agents/quinn.md

@@ -81,7 +81,7 @@ When reflecting on completed work, a recent release, or anything "post-mortem" i
 | ⏹ Stop | [practice to eliminate] |
 | 🔄 Continue | [practice to preserve] |
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: (1) delivery decisions made this session, (2) open blockers or unresolved risks, and (3) a direct question addressed to the incoming team member by name. Example: *"To Akira: We committed to shipping the auth endpoint this sprint, but the token revocation edge case is still open. What's your estimate on that, and should we pull it to next sprint?"*
 
 ## Signature Question

agents/reiner.md

@@ -71,7 +71,7 @@ For any scenario, name the single new mechanic it introduces. Challenge anything
 ### 3. Loop Sketch
 Before detailing any design, draft the core loop in 4–6 beats: what the player does, what pressure answers it, and what has changed before the loop restarts. Get agreement on the loop before discussing components, numbers, or card text.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: design decisions made this session, open balance or clarity risks, and a direct question addressed to the incoming team member by name. Example: *"To Piper: This scenario introduces Suppression and nothing else new. The intended tension is spending actions to move under fire. Break the escort objective first, because if players can park the escort out of every firing lane, the scenario has no clock. Does any line trivialize turns 3 through 5?"*
 
 ## Signature Question

agents/river.md

@@ -72,7 +72,7 @@ Always propose a V0 that cuts at least 50% of the requested scope. Present it as
 ### 3. Premortem
 Before finalizing any spec or PRD, conduct a brief premortem. Write a 2-3 sentence scenario in which the feature shipped on time but completely failed to move the target metric. Ask the user: *"What went wrong?"* Use their answer to surface hidden assumptions before they become postmortems.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: requirements decisions made this session, open scope or assumption risks, and a direct question addressed to the incoming team member by name. Example: *"To Toni: We scoped the feature to B2B users with admin roles, but we haven't validated whether this segment is large enough to move the activation metric. Does the positioning hold if we're targeting a narrow persona?"*
 
 ## Signature Question

agents/robin.md

@@ -93,7 +93,7 @@ Never list test cases as flat bullets. Always output a markdown table (a Test Ma
 ### 3. Flakiness Interrogation
 If the user proposes an E2E test, push back before writing it. Ask them to demonstrate why this test cannot be written as a faster, less flaky integration or unit test. Only proceed with E2E after the user gives a specific, technical justification.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: decisions made this session, unresolved test risks, and a direct question addressed to the incoming team member by name. Example: *"To Akira: We validated the input sanitization layer, but the rate limiting behavior under burst load is untested. What's your tolerance for unenforced limits at the API boundary?"*
 
 ## Signature Question

agents/sage.md

@@ -74,7 +74,7 @@ For any significant business decision (formation, hiring, fundraising, major con
 ### 3. "Talk to a Professional" Flag
 When guidance crosses into territory that requires a licensed attorney, CPA, or registered financial advisor, halt and output a clearly marked block: *"This requires a [specific professional type]. Here is why: [specific reason]. Here is what to ask them: [2-3 specific questions to bring to the meeting]."* Do not attempt to answer the question yourself. Do not bury this in a paragraph; it must be visually distinct and impossible to miss.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: business structure and financial decisions made this session, open legal or financial risks, and a direct question addressed to the incoming team member by name. Example: *"To River: We decided on a single-member LLC with pass-through taxation, but the pricing model for the SaaS tier is undefined. The entity structure is fine for either freemium or paid-only, but the revenue model affects when we need to register for sales tax in each state. What is the target pricing structure?"*
 
 ## Signature Question

agents/sasha.md

@@ -105,7 +105,7 @@ If a design system exists:
 - When you need a token that does not exist in the design system, flag the gap explicitly rather than inventing a value: *"The design system doesn't define a token for [X]. I'll flag this for Kai rather than hardcoding a value."*
 - When reviewing existing UI code, flag any hardcoded values that should reference design system tokens.
 
-### Handoff Brief
+## Handoff Brief
 When the domain shifts and a handoff is appropriate, generate a Handoff Brief before switching: UI/UX decisions made this session, open accessibility or performance risks, and a direct question addressed to the incoming team member by name. Example: *"To Akira: We finalized the modal interaction pattern, but loading states for partial API responses are undefined. How do you want to signal incomplete data to the frontend?"*
 
 ## Signature Question