team-memory
Team Memory
Why this exists
While you work, context is rich. Decisions, rejected paths, root causes, the "we tried X and it didn't work because Y" — all of it lives in your head and in the conversation transcript. Then the session ends and that context dies.
The next teammate (human or AI) reads the code and the git log, but those only capture what changed, not why. They re-discover the same dead ends. They re-debug the same root causes. They suggest the same approach you already rejected.
/team-memory is REM sleep for the team. It consolidates the rich in-session context into a durable, git-tracked memory file every team member can read — and every future AI agent can grep before suggesting a path you've already walked.
Directory boundary
team-memory/MEMORY.md lives at the repo root and is intentionally separate from:
- Claude's auto-memory (
~/.claude/projects/.../memory/) — personal, agent-specific CLAUDE.md/AGENTS.md— project instructions, not history- Personal notes, conversation transcripts, or agent preferences
This file is project-scoped team history only. It belongs to the team, not to any individual agent or user.
More from iankiku/forwward-teams
medic
(forwward) Interprets medical records, clinical notes, FHIR data, and advises on medical data UI with OCR interpretation, clinical summarization, and drug interaction flags. Triggers on patient records, clinical data, medical PDFs, health-tech products, or medical data presentation.
40ceo
(forwward) Provides CEO-level strategic leadership frameworks for vision, OKRs, hiring, fundraising, resource allocation, and pivot decisions. Triggers on company strategy, growth direction, team scaling, investor relations, or any high-level business decision.
32finance
(forwward) Models unit economics, burn rate, projections, pricing, and revenue forecasting with startup-specific frameworks. Triggers on CAC, LTV, burn rate, runway, pricing analysis, financial models, or any CFO-level financial question.
31legal
(forwward) Drafts terms of service, privacy policies, contracts, IP assignments, and open source licensing after gathering industry and jurisdictional context. Triggers on legal documents, terms, privacy policies, contracts, compliance, licensing, or any legal drafting need.
30team-lead
(forwward) Orchestrates multi-agent engineering and business teams by analyzing tasks, selecting team shapes, assigning specialist roles, and coordinating parallel agent work with skill dispatch. Triggers on tasks needing 2+ agents, feature dev with frontend + backend, quality audits, research sprints, bug hunts, or any work that benefits from parallel specialization.
30data
(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.
28