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.
Product context: users, strategy, positioning, constraints, north star metric.
Created by /teach-acumen
End-to-end workflow map per persona — extension points, friction, expansion opportunities.
Created by /teach-acumen · Updated by /workshop
Behavioral personas grounded in real usage patterns, not demographics.
Maintained by /persona
Living competitor map: who they are, what they ship, where they're strong and weak.
Maintained by /scout
Feature inventory: what exists, what's healthy, what's decaying, what's missing.
Maintained by /features
Per-persona value delivery mapped to usage and north star metrics.
Maintained by /value
Data source config: analytics, database, backlog — how skills pull real data.
Created by /teach-acumen
Point-in-time outputs from diagnostic and ideation skills.
Generated by /diagnose, /measure, /workshop
Value Chain — the backbone
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.