strat-market-signal

name	strat-market-signal
description	Identifies whether a raw product, SaaS, devtool, community, course, method, or service idea has enough reachable market signal to continue. Use at the beginning of Pi Strategy before user, offer, MVP, or build work.

Market Signal

Identify whether there is a reachable segment with relevant pain, urgency, and capacity to act.

Workflow

1. Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md; apply language policy, core rules, conventions, and stage gate criteria.
2. Read steering docs if present:
   • .ai/steering/product-principles.md
   • .ai/steering/marketing-principles.md
   • .ai/steering/decision-rules.md
   • .ai/steering/anti-patterns.md
3. Establish workspace directories under .ai/strategy/signal/ and update .ai/strategy/index.md if useful.
4. Gather the idea, presumed audience, creator context, constraints, and validation goal.
5. If context is insufficient, ask at most 3 critical questions. Otherwise proceed with explicit assumptions.
6. Narrow broad segments. Do not accept vague groups like "devs", "entrepreneurs", or "people who want productivity" without a beachhead.
7. Name at least 1–3 existing alternatives in the segment.
8. Classify evidence strength (Strong/Medium/Weak) for key claims.
9. Save .ai/strategy/signal/market-signal.md.

Output template

# Market Signal

## Idea Summary

## Market Category

## Initial Segment

## Market Signal

### Pain Intensity

### Urgency

### Buying Power

### Accessibility

### Existing Alternatives

### Market Awareness

### Market Sophistication

## Recommended Beachhead Segment

## Why This Segment

## Risks

## Assumptions

## Open Questions

## Next Step

Quality bar

• Segment is specific and reachable.
• User and buyer are not confused.
• Buying power and access channels are considered.
• Existing alternatives are named.
• Weak signal is flagged instead of overvalidated.

Output quality checklist

• Segment is narrow and reachable.
• Pain/urgency/buying power are explicit.
• 1–3 alternatives are named.
• Assumptions and open questions are updated.
• Evidence strength is classified.

Critical rules

• Do not create offer, MVP, downstream deliverables, or implementation code.
• Do not claim market validation from enthusiasm alone.
• Always list assumptions and open questions.