Seller Success Group
The guiding question for this context file
"What is true of every product line and product within this business unit?"
Every piece of information you include should be answerable with "yes, this applies to everything in this branch." If it only applies to some children, it belongs lower down the tree. If it repeats something already in a parent file, leave it out.
What to include
- ✓The unit's mission — the specific problem space or customer segment it owns
- ✓The customers or users this unit serves — be specific about whether they are consumers, dealers, internal teams, etc.
- ✓The metrics this unit is accountable for — the KPIs that define whether the unit is succeeding
- ✓Shared principles or constraints that govern how all products in this unit are built and operated
- ✓Key dependencies — other units, platforms, or external systems that all products in this unit rely on
- ✓The unit's position in the wider business — how it fits into the overall value chain
- ✓Any specific compliance, safety, or quality standards that apply to everything this unit ships
What to avoid
- ✕Product-specific features, designs, or roadmap items — those belong in their own context files
- ✕Team structures or individual responsibilities — these change and agents don't need them
- ✕Anything that only applies to one product line within the unit
Examples of good context sentences
"The Buyer Success Group owns the end-to-end buyer journey from first search to completed purchase. Every product we build must be evaluated against its impact on buyer conversion and satisfaction."
"All products in this unit operate on consumer-facing surfaces. Privacy by design and GDPR compliance are non-negotiable requirements for everything we ship."
General principles
🌲
Tree-aware: Agents receive all ancestor files too. Don't repeat what's already above you in the tree.
⏱
Stable, not live: Write things that stay true for months. Roadmap items, sprint tasks, and current incidents belong elsewhere.
🤖
Agent-first: Write as if briefing a capable colleague who has never worked here. Be explicit; don't assume implied knowledge.