To run this task you must have the following required information:

> Feature idea or problem to address. Audience (stakeholders, engineering, executives). Level of detail needed (one-pager vs feature brief).

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Brief Writing Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/product.brief.guide.md` (Get the brief templates and guidance)

2. [Read Human-Style Prose]: Read the documentation in: `./skills/sauna/[skill_id]/references/shared.prose.style.md` (Reference for clear writing)

3. Gather context from the user. A good brief needs:

1. **The Problem/Opportunity**
   - What problem or opportunity are we addressing?
   - Who experiences this?
   - What's the impact of not addressing it?

2. **The Proposed Approach**
   - What's the high-level solution direction?
   - What are the must-have capabilities?

3. **Success Criteria**
   - How will we know this worked?
   - What metrics matter?

4. **Constraints**
   - Timeline or deadline?
   - Resource limitations?
   - Dependencies?

5. **Audience & Format**
   - Who will read this? (determines detail level)
   - One-pager (quick alignment) or feature brief (more structure)?

Check `./documents/product/profile.yaml` for existing product/user context.
Ask for any missing critical inputs before drafting.


4. Draft the brief using the appropriate template from the guide:

For one-pagers:
1. Keep it to a single page—ruthlessly prioritize
2. Lead with the problem and its impact
3. Make requirements scannable (bullet format)
4. Include clear next steps

For feature briefs:
1. Include user story for clarity
2. Be explicit about scope (in and out)
3. Make requirements verifiable
4. Note risks and dependencies

Both formats:
- Be specific, not generic ("page load < 2s" not "improved performance")
- Quantify impact where possible
- List open questions honestly—don't fake certainty

Output the complete brief in markdown format.


5. After presenting the brief:
- Ask if any sections need expansion or different emphasis
- Offer to convert to full PRD if they need more detail
- If new competitive insights, user research, or product positioning
  was developed during this task, offer to update `./documents/product/profile.yaml`:
  "I captured some context about [topic]—want me to add this to your
  product profile for future reference?"