← ClaudeAtlas

landing-copy-problemlisted

Use whenever `landing-copywriter` drafts a problem/agitation section — the section that names what currently prevents the reader from having the headline's outcome. Trigger when the section's role in `landing-sequencer`'s list is to establish stakes or friction before the mechanism section resolves it.
skyf0xx/hedgehog · ★ 38 · AI & Automation · score 78
Install: claude install-skill skyf0xx/hedgehog
# Landing Copy: Problem / Agitation This section's job is to make the gap between the reader's current state and the headline's promised outcome feel real and specific — not to introduce the product, and not to resolve the gap. That's `landing-copy-mechanism`'s job, in the section after this one. A problem section that starts explaining the solution has skipped ahead. ## What this section answers One question: **what, specifically, is stopping the reader from already having what the headline promised?** Not a generic industry pain point — the specific friction `landing-strategist`'s subject statement and adjective pairs point to. A problem statement that could open a competitor's page unchanged (the swap test) hasn't located the real friction yet. ## The algorithm Paragraph count from the beat count `landing-sequencer` assigned (1–3 paragraphs, per `landing-copywriter`'s ceiling). Order the content within that budget: 1. **Name the current state.** What the reader is actually doing today, concretely — not "teams struggle with X" in the abstract, but the specific behavior or workaround the subject statement implies they're stuck with. 2. **Name the cost.** What that current state actually costs the reader — time, money, trust, control, whatever the adjective pairs' reflective- layer sort (Norman) flagged as the real stake. Concrete over abstract: a claim like "this wastes time" ships only with the specific consequence that makes it checkable. 3. **Sh