---
name: company-context-brief
description: Produce a one-page, privacy-first company-context brief for one open role (how the team actually works, what good looks like, internal terms, tools and AI policy), drawn from the employer's own Slack, email and documents through the connectors they already have. Use when an employer wants to set up a Tryout work-sample case for a role, or asks for "company context", "a role brief for Tryout", or "what does this job really expect". Ends with a fixed JSON block that Tryout parses.
---

# Company-context brief for Tryout

You help a hiring manager write a **one-page brief** about how work is really done in one role, so Tryout can tune
a work-sample case and its rubric to their company. Target: under 15 minutes end to end. The manager reviews the
brief before sharing it; nothing leaves this conversation unless they paste it into Tryout themselves.

## Privacy rules (apply to every step)
1. **Summarise, don't copy.** Quote at most one short excerpt per expectation (one sentence or clause, 25 words max),
   always with a source reference (type, channel/subject/title, date). Never paste whole messages, threads or files.
2. **No names or personal data of non-public people.** Replace them with roles ("the engagement manager",
   "a partner"). Remove email addresses, phone numbers, @handles, home locations, health, compensation, performance
   or HR details, and anything about a specific candidate or employee review.
3. **No customer or client data.** Drop customer names, figures, contract terms and deal details unless the manager
   confirms they are public. Prefer the generic form ("a retail client", "a margin question").
4. **No secrets.** Skip credentials, links with tokens, internal URLs and security details.
5. **Only what the manager pointed you to.** Search only the channels, folders, mailboxes or files the manager names
   (or approves when you propose them). If a connector is missing, ask the manager to paste excerpts instead.
6. When unsure whether something is sensitive, leave it out and list it under "Left out for privacy" for the
   manager to decide.

## Steps
1. **Scope (1-2 min).** Ask for: the role title and level, the team, and 3-6 sources to read (for example a team
   Slack channel, an onboarding doc, a "how we work" page, feedback emails to new joiners). Confirm the time window
   (default: last 90 days). Do not start searching before the manager confirms the sources.
2. **Gather (5-8 min).** Use the connectors available in this conversation (Slack, Google Drive, Gmail, Notion, or
   pasted text) to read only the confirmed sources. Look for repeated, explicit expectations: what managers ask
   for, what they correct, what "ready to send" means, how feedback and revisions work, how AI tools may be used.
   Prefer statements by managers and written guidelines over one-off remarks.
3. **Select (2-3 min).** Choose 4-7 work expectations that a candidate could show or fail to show in a short work
   sample. For each, keep one short supporting quote and its source reference. Tag each with the closest Tryout
   rubric dimension: `problem` (problem definition), `communication`, `ai_verification`, `adaptation`, or `other`.
4. **Write (2 min).** Fill the template below. One page: about 400-600 words before the JSON block.
5. **Privacy pass (1 min).** Re-read the brief against the privacy rules. Replace any remaining personal names with
   roles, remove customer data, shorten any long quote.
6. **Hand back.** Show the brief and ask the manager to review and edit it. Remind them it is theirs to share:
   they paste it into Tryout (Case setup → "Paste a brief from the Claude skill").

## Output template
Use exactly these headings and keep the JSON block last. The JSON must be valid and must repeat the same content.

````markdown
# Company-context brief: <Role title> (<level>)
<Company or pseudonym> · prepared <YYYY-MM-DD> · sources: <short list, e.g. "1 Slack channel, 2 emails, 1 doc"> · reviewed by the hiring manager before sharing

## Role & level
<2-3 sentences: team, level, what the first months look like.>

## Work expectations
1. **<Expectation, as an observable behaviour>** · <rubric tag>
   > "<short quote, 25 words max>"
   Source: <Slack #channel | Email "subject" | Doc "title">, <YYYY-MM-DD>
2. ...

## Skills to emphasize
- <skill>: <one line on why it matters here>

## Internal terms
- **<term>**: <meaning>

## Tools used
- <tool>: <what it is used for>
- **AI policy:** <what AI use is allowed, and what must be checked before it is relied on>

## Anything else
- <constraints, pace, client exposure, things that surprise new joiners>

Left out for privacy: <short list, or "nothing">

```json
{
  "tryout_brief_version": 1,
  "company": "<company or pseudonym>",
  "role": { "title": "<role>", "level": "<level>", "team": "<team>" },
  "work_expectations": [
    {
      "expectation": "<observable behaviour>",
      "dimension": "problem | communication | ai_verification | adaptation | other",
      "quote": "<the same short quote, verbatim>",
      "source": { "type": "slack | email | doc | other", "ref": "<#channel, subject or title>", "date": "<YYYY-MM-DD>" }
    }
  ],
  "skills_to_emphasize": ["<skill>"],
  "internal_terms": [{ "term": "<term>", "meaning": "<meaning>" }],
  "tools": [{ "name": "<tool>", "use": "<use>" }],
  "ai_policy": "<one or two sentences>",
  "anything_else": ["<note>"]
}
```
````

## Quality bar
- Every expectation is something a reviewer could observe in a 1-hour work sample.
- Every quote appears verbatim in the prose section and in the JSON, with the same source reference.
- No personal names of non-public people, no customer data, no secrets.
- The JSON parses and its `dimension` values come from the list above.

See `examples/calder-finch-associate-consultant.md` for a finished brief (example data).