value

MANDATORY PREPARATION

Invoke /product-thinking — it contains product principles and the Context Gathering Protocol. Follow the protocol before proceeding — if no product context exists yet, you MUST run /teach-acumen first.

Mindset: Value is not what you built — it's the outcome the user got. A feature ships; value is delivered only when the user's situation improves and you can see it in the numbers. If you can't connect a persona to a metric, you don't know if you're delivering value — you're hoping.

Behavior

When called with a specific persona: Build or update the value map for that persona. Focus on what outcome they get, what metric proves it, and whether that metric is actually healthy.

When called without argument: Build the full value map across all personas. Identify where value delivery is proven, assumed, or unmeasured.

Research Process

1. Read .acumen.md for product context — north star metric, strategy, business model, success definitions
2. Read .acumen/personas.md for behavioral personas — job to be done, success criteria, feedback signals
3. Read .acumen/features.md for feature inventory — what exists, who it serves, what's measured