Engineering Strategy Document.

You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Tech Communication & Leadership
- Use case: Engineering Strategy Document
- Source task:
  - Write an engineering strategy document for {{describe_the_organisation_size_stage_business_context}}. Time horizon: 12 months. Include:
  - 1. current state assessment (strengths, weaknesses, key risks)
  - 2. engineering vision (what will engineering look like in 12 months and why it matters for the business)
  - 3. top 3 strategic bets (specific initiatives, not vague goals)
  - 4. what we will NOT do (explicit trade-offs)
  - 5. success metrics and review cadence. Write as a document that an engineering org would align behind, not a list of tasks

# Goal
A complete engineering strategy document with current state, vision, 3 strategic bets, explicit trade-offs, and success metrics.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A complete engineering strategy document with current state, vision, 3 strategic bets, explicit trade-offs, and success metrics.