← ClaudeAtlas

check-business-coveragelisted

Cross-feature audit — walks the project's declared business cycles (Create→Update→Delete, Subscribe→Unsubscribe, Send→Resend) and surfaces every missing counterpart. Use for a pre-release sweep across the whole product, before an external audit (GDPR, App Store Privacy), or as a quarterly completeness review. Product-level — `audit-funnel-completion` covers conversion within a single flow.
adnanmokhtar/refract · ★ 1 · AI & Automation · score 77
Install: claude install-skill adnanmokhtar/refract
# Skill: check-business-coverage A cross-feature scan. Asks the question: "for every action the user can take, is the inverse / completion / recovery action also reachable?" Catches the half-cycles that ship under deadline pressure. ## Premise Find real issues. Every cycle in the matrix cites the forward action + inverse action with concrete UI paths or API endpoints. "Inverse missing" requires having searched and confirmed: no route handler, no UI button, no settings entry. Severity (CRITICAL / HIGH / MEDIUM) cites the regulatory / security / business consequence — GDPR Article, payment-vendor rule, app-store guideline, security class. Role coverage findings cite the role + the actual response code observed. ## Halt conditions - Refuse to mark "inverse missing" without grepping routes + UI for the action. - **Refuse a bare checkmark.** Every `✓` in every matrix carries the path that makes it true — a route, a screen + the click path, or an endpoint. A `✓` that costs nothing to write is a claim the reader cannot check and the next audit cannot compare against; it is the exact defect this skill's own Premise forbids. - Refuse to label "CRITICAL" without naming the regulation / policy that demands it. - Halt if `ai/business-flows.md` is absent — recovery is to fill it first, not guess. - Don't propose 10 fixes; rank by impact + cite effort estimate. - Don't audit only the happy path — unhappy paths is where the gaps live. ## When to use - Pre-release sweep across the who