Build Brief

Translate a validated idea into a structured implementation handoff. Not a full PRD — a scoped brief covering what to build, in what order, with what data, and how to know it works. One file, everything a coding agent needs, nothing it does not.

This skill bridges the gap between "should I build this?" (founder-skills pipeline) and "build this" (coding agent). The output is designed to be handed directly to gstack /autoplan, Claude Code, or any other implementation agent.

Input Dependencies

Read ALL files from ./founder-outputs/ before proceeding:

• verdict-output.md — must show BUILD (required)
• startup-canvas-output.md — problems, UVP, features, pricing, key metric
• customer-archetype-output.md — who uses this, their workflow, their pain
• scope-output.md — what is in/out of scope
• assumption-map-output.md — riskiest assumptions to validate first
• pretotype-output.md — validation experiments and success criteria
• pressure-test-output.md — demand evidence and JTBD framing
• battle-cards-output.md — competitive positioning

If verdict-output.md is missing or does not show BUILD, tell the user to run /verdict first. If it shows KILL or PIVOT, recommend /pivot-paths instead.