← ClaudeAtlas

genai-use-case-finderlisted

Use when Dr. Shiva Kakkar wants a FILLED GenAI use-case portfolio for a real organization: feed it a function, an org, an industry, or a process (for example "claims at a mid-size insurer", "month-end close in finance", "the CHRO hiring funnel") and it runs the four-move method MAP, GATE, SCORE, SEQUENCE to discover candidate use cases, gate each as point versus system, score them, and sequence them into a portfolio with named quadrants. Triggers on "use-case portfolio", "where should we use GenAI in <function>", "prioritize AI use cases", "point versus system", "build the use-case matrix for <org>", "score and sequence these AI ideas". This is an ANALYSIS GENERATOR, not a lesson. Sibling of teaching-designer (which makes the facilitator keynote or session that TEACHES use-case discovery) and worksheet-generator (which makes the participant fillable worksheet). If the user wants to TEACH the method, hand off to those. This skill fills the matrix for a real org.
Shivak11/shva-marketplace · ★ 0 · AI & Automation · score 62
Install: claude install-skill Shivak11/shva-marketplace
# GenAI Use-Case Finder for Dr. Shiva Kakkar Turn a function, org, industry, or process into a FILLED use-case portfolio: the candidate use cases discovered, each gated as point or system, scored on value and feasibility with risk as a veto and verifiability as the autonomy axis, then sequenced into a defensible portfolio of named quadrants (Lighthouses, Strategic Bets, Quick Wins, Park or Kill). This is an analysis generator, not a session. The deliverable is the completed analysis for a real organization. It is the analysis sibling of two teaching skills. `teaching-designer` makes the facilitator keynote or session that teaches use-case discovery. `worksheet-generator` makes the participant fillable worksheet. This skill does neither. It runs the method on a real org and hands back the filled matrix. If the user wants to TEACH the method, say so and hand off to those two. Keep the boundary sharp. **Golden rule: do not skip stages and do not do half discovery.** A portfolio's quality is set before any table, in the intake and in running BOTH lenses. Run the pipeline in order. Most teams only ever run Lens A and find only point solutions. Running Lens B deliberately is the discipline. **Paths:** when this skill loads, its base directory is announced. Capture it as `$SKILL_DIR` and use it for bundled files. Reads of `references/*.md` may use bare relative paths, but Bash runs and asset copies must use the absolute base (the runtime CWD is the user's project, not this skill