PEAK Review Cowork Project — Setup Kit

This is a working system, run since April 2026, that builds a PEAK evidence bank automatically. It collects evidence from your work tools continuously, so when the Lattice window opens you write your self-assessment from a stocked, source-cited evidence bank instead of trying to remember February.

Setup is five minutes of clicks, then one pasted prompt. The prompt interviews you for everything it needs — and where it can, it looks the answers up in your own tools so you confirm instead of hunt. At the end it creates the daily automation itself.

Part 1 — Manual setup (~5 minutes; the only part Claude can't do for you)

1. Create a folder on your computer, e.g. FY27 PEAK Review. This folder — not chat memory, not project knowledge — will be the system of record.
2. Save THIS kit file into that folder. The setup prompt reads it as its build spec — skip this and step one of the prompt fails.
3. In the Claude desktop app, create a new Cowork project and connect that folder to it.
4. Connect your connectors (Settings → Connectors, your own accounts): Asana (or your task tracker), Slack, Gmail, Google Calendar, Atlassian (Jira + Confluence), Granola or Zoom if you use one. Prune to what you actually use — every connected source gets scanned, so dead sources waste every refresh.

Part 2 — The setup prompt (paste into your first conversation in the project)

First run — full setup. Work through this in order, and don't guess anything
you can ask me or look up.

1. READ THE KIT: Read PEAK_Evidence_Bank_Setup_Kit.md in this folder. Parts
   4–6 are your build spec: the instructions template, the daily-scan spec,
   and the operating lessons. Follow them.

2. TEST CONNECTIONS: Probe every connected source with one small query each
   (Asana, Slack, Gmail, Calendar, Jira/Confluence, Granola/Zoom — whatever
   exists). Show me a one-line ✓/✗ table. If something essential is broken,
   stop and tell me how to fix it before going further.

3. INTERVIEW ME — in batches, deriving what you can from my own data instead
   of making me hunt for it:
   a. Identity: my full name, exact job title (as it appears in Lattice), team,
      manager's name and work email, location/timezone, and British or American
      spelling. Read my Slack member ID from the connection yourself if you
      can; otherwise tell me how to copy it from my Slack profile.
   b. Mandate: one sentence stating what I OWN, as scope, not tasks. Push back
      if I give you a task list — Lesson 7 in the kit explains why this
      sentence matters more than it looks.
   c. Sources: propose my key Asana projects by looking at where my completed