strat-problem-outcome

name	strat-problem-outcome
description	Maps the surface problem, deeper problem, cost of inaction, failed attempts, desired outcomes, transformation gap, and priority problem. Use after market signal and user context, before offer creation.

Problem / Outcome

Clarify the painful problem and the result the user actually wants.

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
   • .ai/strategy/signal/user-context.md
3. Separate surface problem, deeper problem, functional outcome, emotional outcome, and status outcome.
4. Identify cost of inaction, failed attempts, transformation gap, priority problem, and anti-problem.
5. Define at least one measurable success outcome (with unit and target window).
6. Ask at most 3 critical questions only if needed.
7. Save .ai/strategy/signal/problem-outcome.md.

Output template

# Problem / Outcome

## Surface Problem

## Deeper Problem

## Cost of Inaction

## Current Failed Attempts

## Desired Outcome

## Measurable Outcome

## Emotional Outcome

## Status Outcome

## Transformation Gap

## Priority Problem

## Anti-Problem

## Assumptions

## Open Questions

Quality bar

Example: "I do not have a validation artifact" is surface. "I cannot explain my idea in a way that makes someone want to test it" is deeper.

Output quality checklist

• Surface vs deeper problem is clear.
• Cost of inaction is explicit.
• Measurable outcome exists.
• Priority problem is singular and actionable.
• Assumptions/open questions are updated.

Critical rules

• Do not jump to solution or features yet.
• Do not make the problem broader than the beachhead segment.