strat-brief

name	strat-brief
description	Consolidates all Pi Strategy artifacts into the final handoff file .ai/strategy/handoff/strategy-brief.md for downstream SDD, build, or go-to-market packages. Use after acquisition-path.

Strategy Brief

Create the final strategy handoff that another agent or package can consume without losing context.

Workflow

1. Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
2. Read all available artifacts:
   • .ai/strategy/signal/*
   • .ai/strategy/offer/*
   • .ai/strategy/gtm/*
3. Verify readiness checklist from the shared reference.
4. Enforce readiness gate from quality-gates.md.
5. Set status to one of: Ready for Handoff, Needs Research, Needs Decision, Not Ready.
6. Consolidate decisions, constraints, risks, do-not-invent items, and open questions.
7. Add a final pass/fail checklist showing each readiness criterion.
8. Save .ai/strategy/handoff/strategy-brief.md.

Output template

# Strategy Brief

## Status

Draft / Ready for Handoff / Needs Research / Needs Decision

## Product / Offer Name

## One-Line Summary

## Audience

## Market Signal

## User Context

## Problem

## Desired Outcome

## Product Offer

## Value Equation

### Dream Outcome

### Perceived Likelihood of Achievement

### Time Delay

### Effort & Sacrifice

## Offer Stack

## Unique Mechanism

## MVP Scope

### MVP Type

### Primary Workflow

### Input

### Output

### Moment of Value

### Included

### Excluded

### Validation Metric

## Proof System

### Available Proof

### Missing Proof

### Proof Plan

### Claims We Can Support

### Claims We Cannot Support

## Message System

### Positioning

### Main Promise

### Headline Candidates

### Key Claims

### Objections

### Words To Use

### Words To Avoid

## Acquisition Path

### Primary CTA

### Secondary CTA

### Funnel Path

### Measurement Events

## Strategic Decisions

## Constraints

## Risks

## Do Not Invent

## Open Questions

## Ready For

- [ ] Downstream planning
- [ ] MVP build planning
- [ ] User interviews
- [ ] Waitlist
- [ ] Demo
- [ ] Sales call

Critical rules

• The brief must be complete enough for a downstream package to start without asking everything again.
• Do not create downstream deliverables, implementation code, presentation direction, or fake proof.
• Do not mark Ready for Handoff if any required gate fails.
• Do not mark Ready for Handoff if offer, MVP, proof plan (or existing proof), message, or acquisition path is missing or generic.