v1.8.0 — Cohort Migration-Readiness
New Skill: pm-cohort-planner — Cohort Migration-Readiness
A discovery skill for cohort-based migration. For one customer cohort (e.g. Accountants), it reconstructs the complete functional scope that cohort needs to do their entire working day/year in the new product — so the cohort can be migrated fully, with nothing stranded in the legacy system.
Why it exists
The defining failure of cohort migration is partial coverage: you move a cohort over, but a slice of their work still forces them back into the legacy system. The damage usually comes from infrequent-but-critical jobs (year-end close, audit export, quarterly filing) that get missed because teams only look at the visible daily tasks. A working "day" for a cohort is really a working year — this skill makes the whole year visible before cutover.
What it does
- Frequency-banded job map — jobs organized by functional area × cadence (Daily / Weekly / Monthly / Quarterly / Annual / Ad-hoc-Exception). The cadence lens surfaces the landmine jobs.
- Evidence-or-flag discipline — every job carries a confidence level (Verified / Inferred / Assumed — no evidence). Gaps are flagged as coverage risks, never silently filled.
- Mixed-input ingestion — process charts/maps, legacy system artifacts, qualitative evidence (tickets, interviews), usage data, and existing PM docs, each with per-type extraction logic and conflict flagging.
- Completeness sweep — actively hunts period-end events, exception/recovery jobs, cross-cohort hand-offs, and infrequent-but-critical jobs.
- Coverage-risk register + readiness verdict — Ready to plan / Evidence gaps must close first / Not enough signal, with explicit blockers.
- Hand-off block — rows pre-formatted for
pm-migration-plannerPhase 3 (parity matrix); gaps routed topm-prd.
Sits upstream of pm-migration-planner's Cohort-Based strategy, with reciprocal cross-links.
Also
pm-migration-plannergains a pointer topm-cohort-planneras the upstream per-cohort scoping step.- Skill count updated to 47 across README, plugin.json, and marketplace.json.
Full changelog: see CHANGELOG.md.