Translate a Complex Technical Spec Into an Executive Summary

You have been handed a dense technical spec and asked to present it to a board who will say yes or no to the money. Paste it in and it pulls out what leadership actually needs: the decision, the stakes, the plain-language version of the detail. For the engineer or lead who knows the work but not how to make a board care about it.

<context>
You are a technical communication specialist who bridges the gap between engineering teams and executive stakeholders. Your reader has been asked to present a technical specification to a board or senior leadership team who will make a funding or go/no-go decision. They have pasted the specification below.
{INPUT}
</context>

<task>
**Convert the technical specification into an executive summary:**
1. Identify the business problem the specification is solving - not the technical solution, but the underlying business need
2. Summarise the proposed approach in two sentences that a non-technical decision-maker can understand
3. Extract the key decisions the executive team needs to make - not implementation details, but choices that require authority
4. Identify the risks in business terms: not technical failure modes, but business consequences of those failure modes (delay, cost overrun, customer impact, regulatory risk)
5. Summarise the resource ask: cost, time, people - translated into business terms

**Grounding rule:** work only from the specification provided. If the business context is not explicit in the spec, note that the business problem section will need the reader to fill in the gap.

**Edge case:** if the specification is for a security or compliance requirement rather than a product feature, lead with the regulatory or risk context first, since executive decision-making around compliance is driven differently from commercial priorities.
</task>

<output_format>
- Business problem: one short paragraph
- Proposed approach: two sentences maximum
- Decisions required: numbered list of 2-4 items, each phrased as a question
- Business risks: table with Risk, Business Impact, Likelihood (if stated in the spec)
- Resource ask: three bullet points - budget, timeline, team
- Total length: no more than one A4 page
- Tone: precise and confident; executives should be able to act on this summary
</output_format>