DevDoc Refiner: Clarity Brief Architect

It's Monday afternoon. Your team shipped the new API section last week, and the Slack thread is already a mess — three engineers saying the examples are confusing, a PM asking why the onboarding flow wasn't updated, and a customer success rep forwarding a support ticket about something that should have been obvious from the docs. You open the listing. You stare at it. You know something's wrong. You don't know where to start.

The damage: you make a change, but it's the wrong change. The clearest problem gets skipped because it wasn't the loudest complaint. Two weeks later the same friction points resurface, the ticket queue hasn't moved, and the docs are longer but no clearer. Iteration without prioritization is just churn with extra steps.

The fix is not a style guide or a peer review checklist. Those tools surface opinions — they don't tell you which gaps are costing you conversions, which unclear sentences are generating the most support load, or which sections need a complete rewrite versus a single sentence fix.

This skill gives you a focused, repeatable clarity workflow. It analyzes your listing context, ranks every improvement by actual impact, and delivers concise rollout guidance you can act on today — not after another round of committee feedback.

What you get: SKILL.md — the complete clarity analysis protocol with structured sequences for diagnosing, prioritizing, and addressing documentation gaps. SETUP_GUIDE.md — step-by-step instructions for deploying this workflow against your existing listing or doc environment. EXAMPLES.md — worked examples showing before-and-after clarity briefs across different listing types and complexity levels. CHANGELOG.md — version history documenting protocol refinements and how the prioritization logic has evolved. External dependency: None. Runs entirely within your agent's context.