paper-review-response

name	paper-review-response
description	Use when drafting, auditing, or structuring reviewer responses, rebuttal letters, revision maps, comment IDs, response-to-reviewer tables, manuscript change tracking, and polite evidence-forward disagreement.

Paper Review Response

Use this skill when responding to reviewer or editor comments. The goal is to create a traceable, polite, evidence-forward revision package.

Inputs

• Decision letter and reviewer comments.
• Revised manuscript or planned changes.
• Page/line/section locations if available.
• Constraints: time, data, experiments, journal rules.

Workflow

1. Assign stable IDs to every comment.
2. Classify each comment: method, result, writing, citation, figure, scope, ethics, or formatting.
3. Estimate risk: low, medium, high.
4. Map each comment to an action.
5. Draft the response in an editor-facing tone.
6. Link each promised change to a manuscript location.
7. Flag any missing author input or impossible request.
8. Produce a response map and final response letter.

Response Gate

• No reviewer comment is skipped.
• No experiment, citation, figure, line number, or manuscript change is invented.
• Disagreements are respectful and evidence-forward.
• All claimed changes have locations.
• Remaining limitations are acknowledged rather than hidden.

When To Read References

• For action codes and tone patterns, read references/response-patterns.md.
• For output format, use ../../templates/reviewer-response-map.md.