review-followupslisted

Consolide et met à jour les suivis ouverts des migrations (next_steps/deferred des migration/report.json + backlog du kit). Use whenever the user asks what remains open across migrated repos, wants a status of pending decisions, says a follow-up item is done, or decides to close/abandon one — triggers on « fais le point », « qu'est-ce qui reste », « suivis », « c'est fait, coche-le », « on ne le fera pas », "what's still open", "status of the follow-ups", "next steps", "mark it done", "we won't do that one", /migrate-followups. Also run it at the end of every migration (phase 7).
phmatray/ai-migration-kit · ★ 3 · Code & Development · score 75

Install: claude install-skill phmatray/ai-migration-kit

# Migration follow-ups — aggregation and updates The pipeline delivers verified apps **and** a queue of follow-ups: decisions that belong to the owner alone, quick tasks, deliberate deferrals. That queue already lives, structured, in each migrated repo's `migration/report.json` (`next_steps`, `deferred`) — this skill surfaces it and updates it **at the source**. Never a parallel list: a separate tracker would diverge from the reports, which are the executive truth and the dashboard's input. Throughout, **`<kit>`** is the plugin root — resolve it as `<skill-dir>/../..`, where `<skill-dir>` is this skill's base directory (given when the skill loads). Kit script paths resolve from there, never from the current working directory. ## Taking stock 1. Determine the repos: those passed as arguments, else the migrated repos known from the conversation/memory, else ask. Add `--backlog <kit>/docs/backlog.md` if the kit repo is accessible (trigger-tagged debts). 2. Run the kit's tool (mandatory — rule 7, never manual aggregation): ```bash python3 "<kit>/scripts/followups.py" <repo1> <repo2> … --backlog "<kit>/docs/backlog.md" ``` 3. Present the output as-is (it is already sorted: owner decisions first, then tasks by increasing effort) and offer the next moves: settle a decision, run a quick task, or close by decision. The tool flags repos without a `migration/report.json` — that is an error to surface, not to mask (a migrated repo without a report has a bigger p