teach-acumen
Gather product context for this project, then persist it for all future sessions.
Step 1: Explore the Codebase
Before asking questions, thoroughly scan the project to discover what you can:
- README and docs: Project purpose, target audience, stated goals
- Database schema: Models, relationships, what data matters
- API routes and actions: What the product actually does, core workflows
- Analytics / tracking: What's measured today, event names, funnels
- Existing specs or PRDs: Past decisions, constraints, product language
- Package.json / config: Dependencies that hint at product capabilities (payments, auth, notifications, etc.)
Note what you've learned and what remains unclear.
Step 2: Ask Product-Focused Questions
Ask the user directly. Focus only on what you couldn't infer from the codebase:
More from vgrss/acumen
features
Build and maintain a lightweight feature inventory. Use after shipping, when planning, or to understand the current product surface.
9measure
Check KPI health — what's working, what's not, where to dig deeper. Suggests /workshop for opportunities. Use for metric reviews, health checks, or when something feels off in the numbers.
9diagnose
Find current problems in the product based on data, value delivery for main personas, and current features. Suggests /workshop for ideation on solutions.
9scout
Build and maintain a living competitor map. Supports both quick scans and deep competitive analysis. Use when entering a new market, a competitor launches something, before scoping a feature, or for strategic positioning decisions.
9persona
Build and maintain behavioral personas grounded in real user patterns. Use when launching, after user research, or when user understanding feels stale.
9narrate
Write product communication for a specific audience, including when stakes are high and stakeholders disagree. Use for exec summaries, eng briefs, customer announcements, or tradeoff negotiations.
9