Brainstack Scopes
Brainstack is the product umbrella. Two scopes ship as skills:
| Scope |
Skill |
Living documents |
Typical commands |
| Engineer |
engineer-brain |
BRAIN.md |
sync, update, quarterly, reflect, scan, doctor |
| Team |
team-brain |
Supabase memories + cache/<KEY>.json (+ optional md export) |
onboard, attach, remember, correct, history, restore, recall, breakdown, watch, broadcast-topic |
flowchart TB
subgraph Product["Brainstack"]
CORE[Shared core]
subgraph Eng["engineer-brain"]
PB[BRAIN.md]
end
subgraph Team["team-brain"]
TB[TEAM.md]
CACHE["cache/KEY.json"]
SB[(Supabase memories)]
J[(Jira identity)]
MCP[MCP tools]
end
end
CORE --> Eng
CORE --> Team
PB -.->|never uploaded| Team
J --> SB
SB --> CACHE
MCP --> SB
Principles
- Skills = scopes; commands = verbs.
- Personal brain stays personal — never uploaded to Team Brain.
- One initiative → one Jira key (cache + optional
initiatives/<KEY>.md).
- Collaborative memory: Jira identity + Supabase SoT + local cache; md is export.
- Agent loop (mandatory in Cursor):
recall before research on a key; remember after durable findings (source_ref); correct / history / restore on human pushback; breakdown consumes recall.
- Joiners need invite + Jira key + crew’s URL/anon (
onboard); repo ships placeholders in supabase/project.public.env — each crew brings their own project.
Demo walkthrough
- Admin:
bootstrap --team "Spike Crew" --admin "Alice" … (or manual migrate + register) — see supabase/README.md
- Admin: share the printed invite + URL + anon bundle
- Teammate: put crew URL/anon locally →
onboard <invite> "Name" YOU_JIRA_TICKET_HERE
- Agents/
remember / recall / breakdown (or MCP tools)
- Optional: wire mcp/team-brain; Cursor installs
team-brain.mdc always-on rule
/engineer-brain sync still personal-only