strat-user-context

name	strat-user-context
description	Turns the selected market segment into a concrete user and buyer context: situation, workflow, alternatives, triggers, objections, language, needs, and fears. Use after strat-market-signal and before problem/outcome work.

User Context

Transform target audience into a real user/buyer context.

Workflow

1. Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
2. Read .ai/strategy/signal/market-signal.md.
3. Read steering docs if present, especially product and marketing principles.
4. Ask at most 3 critical questions only if needed.
5. Map the person, current situation, current workflow, alternatives, decision triggers, objections, real language, emotional state, functional/social needs, hidden fears, and primary Job-to-be-Done phrased in the user's own language.
6. Save .ai/strategy/signal/user-context.md.

Output template

# User Context

## Primary User

## Buyer

## User vs Buyer Difference

## Current Situation

## Current Workflow

## Current Alternatives

## Trigger Events

## Decision Context

## Objections

## Language They Use

## Emotional State

## Functional Needs

## Social / Status Needs

## Hidden Fears

## Assumptions

## Open Questions

Quality bar

Prefer concrete context: "dev who works full-time, uses coding agents at night, has multiple SaaS ideas, and overbuilds before validation" instead of "indie hacker".

Output quality checklist

• Primary user is concrete.
• Buyer is explicit or marked as same person.
• Current workflow + trigger events are clear.
• JTBD statement is included.
• Assumptions/open questions are updated.

Critical rules

• Do not create offer, MVP, downstream deliverables, or implementation code.
• Do not invent demographic detail that does not affect strategy.
• Separate user from buyer when different.