Design Team Slack → SOP Converter

### Prompt: Design Team Slack → SOP Converter

**Context**
- **Input**: A raw export of a Slack thread (markdown or plain‑text) that discusses a design process (e.g., handoff to developers, accessibility review, component library updates). Include the timestamps, usernames, and any attached files/links.
- **Goal**: Produce a concise, step‑by‑step Standard Operating Procedure (SOP) that can be copied directly into Notion, Confluence, or a markdown‑based wiki.
- **Audience**: New designers, developers, and product managers who need a clear, repeatable process.

**Task**
1. **Extract Steps** – Identify each distinct action or decision point in the conversation.
2. **Assign Roles** – Map each step to a responsible role (e.g., Designer, Front‑end Engineer, QA, Product Owner).
3. **Add Timeline** – Suggest a realistic time estimate or deadline for each step (e.g., "24‑48 h", "by next sprint kickoff").
4. **Include References** – Pull out any linked design files, Figma URLs, or documentation and embed them as markdown links.
5. **Format Output** – Render a clean SOP table followed by an optional narrative summary.

**Output Format**
```markdown
# SOP: <Descriptive Title>

| # | Step | Owner | Timeframe | Resources |
|---|------|-------|-----------|-----------|
| 1 | <Action description> | <Role> | <Estimate> | <Links> |
| 2 | … | … | … | … |

**Narrative Summary** (optional):
- Brief overview of why this SOP exists.
- Key success criteria.
```

**Quality Bar**
- All steps must be atomic (one action per row).
- Role names must match common team titles (Designer, Engineer, PM, QA, etc.).
- Timeframes expressed in hours/days or sprint milestones; avoid vague terms like "soon".
- Every resource link must be a valid markdown hyperlink.
- No duplicate steps.

**Constraints**
- Limit the SOP to a maximum of 12 steps.
- Keep the total length under 800 words.
- Preserve any critical compliance or accessibility notes verbatim.
- If the thread lacks sufficient detail for a step, insert a placeholder: "[Details needed]" and flag it in the **Resources** column.

**Example Call**
```
You are a design operations specialist. Convert the following Slack export into an SOP.
---
[Slack export goes here]
---
```

**Tips for Best Results**
- Provide the full thread, not just a snippet.
- Mention the preferred SOP title if you have one.
- If you need a specific output format (e.g., CSV), add that instruction after the main request.