Based on the provided input (brief, notes, chat, document), generate a structured mission document that follows Appunite’s mission-command format, optimized for *problem-solving and execution clarity*.

Apply these principles:
- Use consulting techniques (root cause, iceberg theory, value-based framing, outcome alignment)
- Think in **MECE structures** and outcome-first logic
- Highlight **bold** any ambiguity, missing metrics, weak ownership, or soft intent
- Structure the output for asynchronous communication and autonomous execution

Use input at the end of the prompt to fill gaps in the final document. Remember that the mission is created by two people - the Leader and the Mission Owner. 

**Only fill in sections where input provides clear context**—do not assume or invent where gaps exist.

## This is what the context mission should include.

### **Title (Leader)**
Short, outcome-driven, clearly describing the strategic or tactical objective.

*Examples:*
- “Define GTM Playbook for Fintech Segment”
- “Deliver First 1000 Users for MVP”
- “Reduce Build Time by 30% Before September”

### **Context (Leader)**
Ground the mission in shared understanding. Include:
- Current state and pain
- Strategic opportunity or risk
- *Why now*
    
    Keep it **concise and non-generic**. If missing, mark gaps: **e.g., unclear why we’re solving this now**
    

### **Problem We’re Solving (Leader)**
Frame the root cause—not just the symptom. Include upstream blockers, business risks, or customer pains.

Use 5 Whys or Iceberg Theory logic.

### **Intent (Leader)**
State clearly what success looks like. Use a **SMART goal or outcome metric**.

If missing KPIs or timeframe, **bold** them.

### **HOW (Mission Owner)**
Outline your *initial approach plan*.
- List actions with owners and time horizons
- Use bullets or step-by-step flow
- Keep this section current—outdated versions move to “Changelog”

### **Underlying Problems to Solve (Mission Owner)**
List sub-problems the team will need to solve (e.g., unclear ICP, poor message-market fit, unclear funnel).

Helps to surface risks early.

If vague or missing, highlight: **What are the blockers?**

### **Definition of Success (Mission Owner)**
Set measurable leading + lagging indicators. Must include:

- Completion criteria
- Due date
- Metrics
    
    *Example:*
    
- **By Aug 15** At least **50% of test group** responds positively CAC under $30 Sales-ready assets handed off to GTM team

## **Enforce Final Output Format**
Each generated mission should follow this structure:

---

# Title

# The Challenge

*Share a context, task, constraints, success metrics according to [this](<https://www.notion.so/Quest-8a0692c3edb64f848f6c9a3750dc8c2a?pvs=21>) manual. This part is prepared by person that defines quest.* 

### Context
*Provide background information, relevant history, and key situational factors that frame the current challenge. Why is this task important, and what broader goals or projects does it contribute to?*

### Objective
*Clearly state what the quest should achieve. This should be a concise description of the desired outcome—what needs to be done, built, solved, or delivered.*

### Constraints
*Define the limitations the person responsible for the quest should operate under, such as resources (time, budget, team capacity), specific tools or methods required, or any external factors that may affect delivery.*

### Success metrics
*How you will measure success of this quest in 1-3 months from now?*

### Control loops
*Set up how often, and in what form, the person responsible for this quest will check in with you. Include any structured feedback moments, deliverable checkpoints, or adjustments based on early results.*

# The Approach
*The part is prepared by person that will be responsible for quest.*

---

## Input