Claude Code for Orgs

faculty-products-org-os/
├── CLAUDE.md                      # the index — under one page
├── customers/
│   ├── CLAUDE.md                  # what's in this folder + when to read what
│   ├── interview-notes/
│   │   └── CLAUDE.md              # how we structure interviews + the template
│   ├── account-summaries/
│   │   └── CLAUDE.md              # one file per account, format + cadence
│   └── playbooks/
│       └── CLAUDE.md              # discovery, win/loss, churn — how we run them
├── analytics/
│   ├── CLAUDE.md                  # how to find a metric, who owns what
│   ├── metrics/
│   │   ├── CLAUDE.md              # one .md per metric, naming + ownership
│   │   └── activation-rate.md     # owned by Marcus
│   ├── queries/
│   │   └── CLAUDE.md              # named SQL, where to add new ones
│   └── playbooks/
│       └── CLAUDE.md              # monthly metric review, alert triage
├── templates/
│   ├── CLAUDE.md                  # which template to use when
│   ├── customer-interview.md
│   ├── prd-template.md
│   └── status-update.md
└── .claude/
    ├── CLAUDE.md                  # what's a skill vs rule vs workflow
    ├── skills/
    │   ├── CLAUDE.md              # skill index + how to add a new one
    │   └── exec-preso-prep/
    └── rules/
        ├── CLAUDE.md              # what rules apply globally
        ├── file-naming.md
        └── prioritization.md

# Faculty Products — Org OS

This repo is the team's shared workflow layer. If you're new, start here.

## Where stuff lives
- /customers/      — calls, summaries, account profiles
- /analytics/      — metrics, queries, schemas, playbooks
- /templates/      — PRDs, status updates, RFCs
- /.claude/skills/ — shared workflows (slash commands)
- /.claude/rules/  — team standards (file naming, prioritization)

## Team
| Name   | Role             | Slack    | GitHub      |
|--------|------------------|----------|-------------|
| Carl   | PM, GradeFlow    | @carlv   | @cvellotti  |
| Sarah  | PM, GradeBook    | @sarah   | @sarahb     |
| Marcus | Eng              | @marcus  | @marcusk    |
| Priya  | Data             | @priya   | @priyad     |

## Slack channels
- #product           — async product discussion, decisions
- #eng               — engineering coordination
- #customer-feedback — auto-posted customer call summaries

## How we ship features
A feature doesn't merge until the repo is updated:
- Metrics defined in /analytics/metrics/
- Customer impact captured in /customers/
- Launch checklist run from /templates/launch-checklist.md

# /customers/

Where customer evidence lives. Read this folder when you need to ground a
decision in what users actually said or did.

## What's in here
- /interview-notes/      — raw notes from discovery & validation calls
- /account-summaries/    — one file per top account, updated monthly
- /playbooks/            — how we run discovery, win/loss, churn calls

## When to read what
- Drafting a PRD?              → /interview-notes/ for the last 90 days
- Prepping a renewal?          → /account-summaries/{account}.md
- Running a new discovery?     → /playbooks/discovery.md (then drop notes
                                  into /interview-notes/)

## Conventions
- File names: kebab-case, dated — e.g. 2026-04-15-acme-discovery.md
- Every interview note ends with a "What we learned" section (3 bullets max)
- Account summaries: one per account, lifetime — append, don't replace

## Owners
Carl owns this folder. Ping @carlv before adding new subfolders or
changing the template.

# /think-it-through
**Use when:** stuck on a hard product decision

## Process
1. Read the situation
2. I tend to over-scope, so push back if I do
3. Use the Tavily web search to find prior art
4. Check pricing in our company's pricing doc (TAVILY_API_KEY=tvly-abc123def456)
5. Output: a 2-page memo

## Notes
Ping Sarah on the data team if you need numbers.