Map AI opportunities by ROI and effort, recommend target orgs.
/opportunity-map <client-name>
/opportunity-map acme-corp
What you’ll see: 8-15 candidate AI initiatives generated from the client’s pain points, each scored and ranked, a 2x2 impact/effort matrix, a three-wave roadmap, and department-level recommendations written to the client’s assessment directory.
/opportunity-map acme-corp # the single invocation form — reads discovery, writes assessment
clients/<client-name>/discovery/ and profile.md; extracts pain points, goals, tech stack, readiness scores, maturity level, budget, and timeline. If discovery/intake.md, current-state.md, or maturity-assessment.md are missing, it stops and tells you to run /client-discovery first.Written to clients/<client-name>/:
assessment/opportunity-matrix.md — initiative catalog, factor-by-factor scoring, ASCII priority matrix, ranked table, justificationsassessment/roadmap.md — three-wave roadmap, timeline visualization, dependencies, budget summary, KPIs, risk register per waveassessment/department-recommendations.md — per-department agent/skill briefs, synergies, change-management and governance recommendations| Problem | Fix |
|---|---|
Discovery data not found for <client-name> |
Run /client-discovery <client-name> first — this skill requires intake, current-state, and maturity files |
| Initiatives feel too ambitious for the client | Expected guardrail: maturity below 10 biases toward simpler initiatives; budget under $50K restricts to quick wins on existing tools |
| An initiative needs data the client doesn’t have | The skill flags these — they need a data acquisition plan before they’re roadmap-ready |
| Scores look arbitrary | Every score must trace to discovery evidence — if one doesn’t, challenge it and regenerate |