What problem does it solve? Teams lose track of project facts scattered across meetings, documents, and conversations, causing terminology drift and inconsistent downstream artifacts. This Skill consolidates all durable project knowledge into a single canonical docs/product/context.md file that every other skill and agent reads. ## Core Features & Use Cases - Context Seeding and Refresh: Creates or updates docs/product/context.md containing the overview, evidence digest, source index, glossary, design and technical context, and a Know/Don't-Know ledger. - Evidence Ingestion: Digests raw input batches from docs/product/input/ with line-level citations, staging external documents and connector pulls (Notion, Granola, Slack) verbatim before citing them. - Glossary and Conflict Tracking: Stabilizes domain terminology with settled/forming/TBD statuses and records disagreements between sources as explicit [conflict] ledger entries. - Use Case: After a client call adds new requirements, run this Skill to stage the call notes, digest them with citations, update the glossary, and flag blocking unknowns before writing a PRD. ## Quick Start Ask the agent to seed or refresh the project context for the target repository using the project-context skill, ingesting any new evidence batches in docs/product/input/.