shaping-writing-pitches

To write a project pitch document from shaping artifacts, you need to synthesize upstream inputs like the Context Brief, Problem Frame, and Architecture Sketch into a structured narrative that clearly communicates the proposed solution and its rationale to decision-makers.

The best way to present a shaped solution to an executive betting table is to generate a concise pitch document that articulates the problem, outlines the solution using breadboard notation, and explicitly defines the required investment, scope boundaries, and no-gos.

To prevent scope creep during project pitch handoff, explicitly define the project appetite, identify potential rabbit holes, list no-gos, and document open questions within the pitch to manage expectations and align implementation teams on boundaries.

Generating a persuasive project pitch without a completed Risk Register and Domain Scenarios is not recommended, as the skill synthesizes these specific upstream artifacts to ensure the narrative fully communicates the shaped solution, its rationale, and boundaries.

A project pitch narrative for efficient implementation handoff should include a compelling problem statement, a structured solution description with key design decisions, and clear scope definitions covering appetite and open questions to ensure team alignment.