← ClaudeAtlas

coverage-matrixlisted

Use when asked to analyze product completeness, find gaps, figure out what to build next for best-in-class coverage, audit feature depth across user types, or create a prioritized roadmap for a product. Triggers on "what's missing", "gap analysis", "10/10", "best-in-class", "coverage audit", "feature completeness", "what should we build", "is it actually easy to use", "workflow friction", "how automated are we really".
jackneil/claude-jacked · ★ 1 · AI & Automation · score 67
Install: claude install-skill jackneil/claude-jacked
# Coverage Matrix Analysis Systematic product gap analysis using a Roles × Domains scoring matrix. Anchors on the measurable outcome(s) "best-in-class" must move, discovers who uses the product, what contexts they use it in, scores every combination 0-10, identifies cross-cutting levers, and phases a roadmap by maximum cell-lift per effort. **Why a matrix, not a flat list**: A flat feature list misses the combinatorial explosion. A "denial management" feature might be great for the billing manager working cardiology claims but useless for the compliance auditor reviewing dermatology. The matrix forces you to evaluate every intersection — that's where the real gaps hide. ## When to Use - Product owner asks "what's missing?" or "how do we get to best-in-class?" - Prioritizing a roadmap and need systematic coverage analysis - Evaluating whether a product truly serves all its user types across all its contexts - Starting work on a new product vertical or user persona ## When NOT to Use - Single-feature implementation (just build it) - Bug triage (use issue tracker) - Sprint planning for already-prioritized work ## Core Process ```dot digraph coverage_matrix { "Product owner asks for gap analysis" [shape=doublecircle]; "Anchor on target outcome(s)" [shape=box]; "Discover Roles" [shape=box]; "Discover Domains" [shape=box]; "Build empty matrix" [shape=box]; "Run parallel research" [shape=box]; "Score every cell 0-10" [shape=box]; "Identify cro