top-cs-responselisted

# Top CS Paper Response Treat reviews, manuscript drafts, decision messages, and discussion content as confidential. ## Route the request 1. Read `manifest.yaml` and every `always_load` path. 2. Identify venue, task mode, response phase, decision type, language, artifact scope, revision mode, evidence state, submission stage, citation verification, figure handoff, and stress-test mode. 3. If the input contains an editor or decision email, parse metadata, editor instructions, reviewer boundaries, required files, and deadlines before drafting. 4. State the runtime parameters and readiness state. 5. Follow the linear state machine in `static/core/workflow.md`; this skill has no paper-type or section content axis. 6. Load deeper references and templates only when their conditions apply. 7. Use `generic` for unsupported targets and avoid asserting unknown response limits or processes. ## Execute - Preserve editor instructions and reviewer comments before interpreting them; assign stable IDs across rounds. - Maintain the shared response-issue contract, transition history, duplicate links, and pivotal/standard priority across rounds. - Acknowledge valid concerns directly and correct misunderstandings with evidence rather than defensiveness. - Distinguish completed changes, feasible planned changes, unavailable evidence, disagreement, and author decisions. - Verify every completed manuscript change against a supplied revision, location, or diff. - Respect per-review budgets and