Synthesise Reviews

Combine multiple review reports into a single prioritised revision plan with cross-reviewer consensus ranking.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

• Source slug: synthesise-reviews
• Write reports to: reviews/<scope>/synthesise-reviews/YYYY-MM-DD-HHMM.md inside the project, where <scope> is the paper slug (e.g. paper-jtp) or _project for project-level synthesis. Path is relative to the research project root, not the Task-Management repo.
• Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
• Idempotency: if today's file exists, append a same-day descriptor ({date}-revision.md, {date}-r2.md, {date}-pre-submission.md) — never overwrite.
• Index update: if reviews/INDEX.md exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise review-recap will rebuild the index next time it runs.
• Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.

Purpose

After running parallel review agents (paper-critic, domain-reviewer, referee2-reviewer), this skill reads their internal reports, cross-references issues, and produces a unified synthesis grouped into workstreams by priority and theme. It decides the consolidated issue set; strategic-revision --internal is the separate step that turns a complex issue set into an executable DAG.