revision-coordinator_skill

Overview

This skill orchestrates manuscript revision by parsing feedback, mapping issues to article sections, and routing tasks to specialized writing skills. It coordinates targeted sub-skill revisions, tracks progress, and verifies coherence so you can produce a focused, accountable revised draft.

How this skill works

I read the manuscript and feedback, break feedback into discrete actionable items, and map each item to the relevant section and specialist skill. For each mapped item I dispatch that section to the appropriate sub-skill with clear instructions, track status, and run cross-section coherence checks before producing a final verification and revision summary.

When to use it

• You have a complete draft or substantial sections and received reviewer/editor/colleague feedback.
• You need systematic routing of different feedback types (theory, methods, findings, conclusion) to specialist revision skills.
• You want a tracked, auditable revision process that preserves what works and fixes targeted problems.
• You must reconcile conflicting feedback or ensure intro/conclusion and theory/findings coherence.
• You need a reviewer response summary mapping changes to comments.

Best practices

• Provide the full draft and all feedback in any format so feedback can be parsed into discrete items.
• Confirm routing decisions at the Phase 0 pause before sub-skills are invoked.
• Address structural changes before stylistic calibration to avoid wasted rewrites.
• Flag ambiguous or conflicting feedback for user decisions rather than guessing.
• Keep the revision map updated: Pending, In progress, Addressed, Needs decision.

Example use cases

• Convert reviewer comments into a revision map and dispatch theory edits to lit-writeup and methods clarifications to methods-writer.
• Resolve a promise-delivery mismatch by deciding whether to revise the intro or the findings and then running coherence checks.
• Expand a methods section to address credibility queries (coding detail, intercoder reliability) using the methods-writer pathway.
• Handle a 'two intros' problem by turning the second intro into a Theory section and running bookend coherence.
• Produce a revision-summary.md that itemizes changes and drafts a response memo for reviewers.