- /catchup — pull latest code from main and get a product-friendly summary of what changed, without losing .acumen/ context
- Total skill count: 20
Your PRDs, decks, and strategy docs are too far from the codebase. Acumen defines a set of skills & context building for product people to craft & thrive with AI harness right from the codebase.
Decisions are made in docs, slides, and chat — disconnected from the codebase where the truth is.
Acumen fixes this by embedding product craft where the building happens — skills that read your codebase and an organised knowledge layer before they write a single line.
Each skill is a focused product operation — grounded in your codebase and knowledge layer, not generic prompting.
One-time setup that gathers product context for your project and saves it to .acumen.md. It guides you through exploring the codebase, asking product-focused questions about users, market, business model, strategy, and metrics, then synthesizes findings into persistent context.
/teach
/teach after the pivot to B2B
Acumen closes the distance with persistent context files that live in your repo, versioned alongside code. Every skill reads them before it writes. The more you use Acumen, the sharper the output gets.
The value chain maps each persona's full job end-to-end. It answers: where do we bring value, where is the user on their own, and where are the expansion opportunities? Eight skills read it. Three maintain it.
| Step | Our role | Skills that use it |
|---|---|---|
| Identify the problem | None | /diagnose, /workshop |
| Choose a tool | Assist | /orientation, /scout |
| Set up & configure | Own | /increment, /measure |
| Do the core job | Own | /increment, /defensibility |
| Evaluate results | Assist | /measure, /diagnose |
| Share & collaborate | None | /workshop, /roadmap |
Example value chain. Yours is generated from your product's actual workflow by /teach-acumen.
Acumen follows the agents.md spec. Drop the skills into your AI tool and go.
Use any coding agent that supports the agents.md spec. It works with read-only access rights.
# One command, auto-detects your tool
npx skills add VGrss/acumen
# One-time product context /teach-acumen # Then let the skills guide you /diagnose /orientation /workshop
Each skill suggests the next one. Just follow the flow.
The stack is collapsing. Product «» Design «» Developer: all become Builders with a speciality.
Every profile benefits from reinforcing their Product Acumen.
npx skills add VGrss/acumen for auto-detection, or copy the .agents and .claude directories into your project root./update-acumen from within your AI tool, or run npx skills update. Your .acumen.md and context files are preserved..claude/skills/ contains the symlinks. For Cursor, ensure agents.md is enabled..acumen.md with your product's context. Without it, skills still work but produce less targeted output.