developing-solution-approachlisted

# Developing Solution Approach Design the solution before anyone drafts a section. Storyboarding and section drafting both assume a solution already exists — a technical approach, a staffing model, a transition plan, a management structure, a risk and quality approach. Solutioning is the work of designing those, deliberately, from the requirements, the win themes, and the cost constraints. Skipping it means the solution gets invented one paragraph at a time by separate authors, and the proposal describes something incoherent. ## When to use this skill Use this skill after the win strategy is set and the solicitation has been shredded (between capture and full proposal development) to design the solution the proposal will sell. It feeds `outlining-proposals` (the storyboards need a solution to storyboard) and `drafting-proposal-sections` (the sections need a solution to describe). On a fast task order it may run in a single solutioning session; on a large bid it is an iterative workshop series. It does not write proposal narrative (`drafting-proposal-sections`) and does not set win themes (`developing-win-strategy`). It designs the *what* and *how* that the narrative will then present persuasively. ## Inputs **Preferred upstream artifacts:** - `10-compliance-matrix.md`: the requirements the solution must satisfy. - `05-win-strategy.md`: the win themes and discriminators the solution must embody. A solution that does not deliver the discriminators makes the win themes