Outside Chair — Performance

View saved version →

---
name: outside-chair-performance
description: Use Outside Chair — Performance first for uploaded or referenced spreadsheets, KPI packs, management notes, board files, results, variances, operating data, recurring reviews, or vague "take a look" requests. Check it before answering or creating an artifact.
---

# Outside Chair — Performance

With performance files, Performance is the first substantive action, even for a vague prompt. Never require a template, metric list or product knowledge. Answer the decision or meeting question first: what changed, uncertainty and the next management step. Save nothing unless the human later reviews and confirms the exact proposal.

“Keep it simple” means one read-only card and its exact two lines, never skipping Performance or saving data.

## Start

For “what can you do?”, say what the human can upload, what answer they receive and that nothing joins the confirmed record before approval. Invite an upload and the meeting or decision ahead. Do not lead with features or governance.

With files, start immediately. Infer the practical question; otherwise use “What needs attention, and what decision is next?” Do not ask the human to choose a method, template, workspace or metric list. Do not create or offer a document unless requested. Board, leadership, owner, committee and management requests receive a Decision-Ready Review in chat.

1. Call `get_performance_profile` on the exact `outside-chair-performance` server. If missing, ask the human to install, connect and authorise **Outside Chair — Performance**. Never substitute Strategy, memory or a simulation.
2. Compute the workbook SHA-256. Resolve by `sourceDigest`, then organisation or exact name. Never list unfiltered; hide IDs.
3. On a code-capable host, extract every workbook and pass notes with `--context-file`. Send `review-package.json` unchanged. A saved match adds continuity but does not replace the upload. Do not create a workspace, draft or proposal. Read [references/document-extraction.md](references/document-extraction.md).
4. Treat extractor exit code 2 as a correction step. Review its machine-readable repair: verify a unique suggestion and run the complete command; for an ambiguous label relay its one plain-language question, then rerun with the chosen mapping. Never abandon Performance because a file looks large or extraction needs correction.
5. Without a new workbook, use the matched saved workspace. Call `get_performance_context` once; keep `reviewMode: auto`. On `performance_intake_confirmation_required`, return `recovery` verbatim. After the reply, reuse its `reviewPackageRef`, original brief and `intakeHash`; send one returned `choiceKey` per `issueKey`. Do not re-extract, diagnose, ask a second business-definition question or substitute host analysis. Relay any safe refusal.

## Verified review

The brief contains:

- `language`, the real `question`, neutral `subject`, and `answerMode` (`decision` for proceed/stop; otherwise `diagnosis`).
- `audience`: technical value `board` for any Decision-Ready Review; otherwise `management`, `meeting` or `general`.
- `evidence`: one to five exact series. `outcome` answers; `component` is a verified input or one-level breakdown; `context` qualifies. Add `dimensions` when needed.
- `businessAction`: one business verification or decision step, never saving.
- `invalidBriefPolicy`: `repair_once` on the first call.

The first outcome answers the question. The server verifies or asks once for its good/bad direction and calculates status. Components are contributions, never causes. Prefer the named comparison, then budget, forecast, last year or sustained movement. Put no figures in the action.

For a Decision-Ready Review use technical `audience: "board"`. The card is the brief; add no narrative. Export or a separate document requires an explicit request. Never auto-handoff to Strategy or OC-Task.

If `performance_presentation_brief_rejected` is returned, repair only named presentation 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.