Issue format Slope uses

What a Slope-created issue looks like

Every issue Slope creates has the same shape so dev teams (and AI coding agents) know what to expect:

• Title — opportunity title prefixed with [slope:<type>] e.g. [slope:low_ctr] Rewrite title on /pricing.
• Body — Markdown with three sections: Why, Evidence, Recommended actions.
• Labels — slope:opportunity + slope:<type> (e.g. slope:content_decay).
• Footer — link back to the Slope opportunity URL for full context.

Example body

## Why
Page /pricing has 1,247 impressions / 28d but only 41 clicks (3.3% CTR).
Cluster average is 5.7% CTR — you're losing ~30 clicks/mo to a weak title.

## Evidence
- URL: https://example.com/pricing
- 28d impressions: 1,247
- 28d clicks: 41
- Current CTR: 3.3% (cluster avg 5.7%)
- Current position: 4.2
- Current title: "Pricing - Example"
- Current meta: ""

## Recommended actions
- Rewrite title: lead with primary keyword, add benefit
- Add meta description (currently empty)
- Consider adding a featured snippet anchor (table or list)

---
Slope opportunity: https://app.slope.to/opportunities/opp_abc123