Enrich Your Context
💎 Product Management OS only — This guide is for users who purchased the Product Management Operating System ($499). Free skills don't include context files.
You Already Have Context
Your context files are pre-filled from checkout. This page is for going deeper — enriching your context so outputs are even more tailored.
The Context Files
| File | What It Contains | How to Improve It |
|---|---|---|
company.md | Company name, mission, stage, priorities | Add quarterly goals, team size, key metrics |
product.md | Product name, description, features | Add specific features, technical details, current state |
personas.md | Target users, JTBD, frustrations | Add real quotes from research, specific behaviors |
competitors.md | Competitive landscape | Add win/loss reasons, feature comparisons |
goals.md | This quarter's priorities | Update as priorities shift |
backlog.md | Feature ideas and requests | Add new ideas as they come in |
Two Ways to Enrich Context
Option 1: Edit Directly
Open any context file and add details. More specific = better outputs.
Before:
## Target User
Product managers at tech companies
After:
## Target User
Solo PMs — the only product manager at a startup (50-200 employees).
They handle discovery, specs, roadmapping, and stakeholder communication alone.
Often report directly to CEO. Stretched thin, making decisions with incomplete information.
Key frustrations:
- "I don't have time to do proper research"
- "Every stakeholder wants something different"
- "I'm constantly context-switching"
Option 2: Drop Docs and Let Claude Extract
Have existing product docs? Don't rewrite them — let Claude extract the good stuff.
Step 1: Drop files into your workspace folders
| Folder | What to Drop |
|---|---|
context/inputs/ | Pitch decks, PRDs, strategy docs, one-pagers |
discovery/inputs/ | Interview transcripts, survey results, support tickets |
strategy/inputs/ | Competitive intel, battle cards, market analysis |
Step 2: Ask Claude to enhance context
Can you read the files in context/inputs/ and enhance my context files with relevant information?
Step 3: Review and approve — Claude shows what it found and asks before updating.
What Makes Good Context?
| Generic | Specific |
|---|---|
| "We have competitors" | "Main competitors: Notion (collaboration), Linear (eng focus), Asana (enterprise)" |
| "Users want it faster" | "Users complain about 3+ seconds load time on dashboard" |
| "B2B SaaS" | "PLG B2B SaaS, $49/seat/month, 500 paying customers" |
Real quotes beat descriptions. Instead of "Users find onboarding confusing," add actual quotes from research.
Keep it current. Update context quarterly or when something major changes — new competitor, feature launch, strategy pivot.
You're ready! Start using your skills — try /prd-generator or /executive-update-generator. Changes to context files take effect immediately.