strategic-revision
Strategic Revision — From Referee PDF to DAG-Validated Master Plan
Read a referee comments PDF and produce:
- Standardised tracking files (per-reviewer markdown, LaTeX verbatim, comment tracker, review analysis)
- A computationally validated revision master plan (atomic tasks, DAG, execution blocks A-E, critical path, bottlenecks)
Provenance: DAG validation + critical-path architecture adapted from Jukka Sihvonen's strategic-revision skill (https://github.com/jusi-aalto/strategic-revision). the user's ingestion layer (correspondence scaffolding, LaTeX verbatim, R&R routing, venue strategy, coaching) retained.
When to Use
- Received reviewer reports for a paper (journal or conference)
- Starting an R&R cycle and need to set up tracking + plan revision strategy
- Want both structured referee artifacts AND a dependency-mapped action roadmap
When NOT to Use
- Writing the actual response letter (use generated response blocks as a starting point, then write manually)
- Reviewing someone else's paper (use
/proofreadorpeer-revieweragent) - Internal review synthesis only — use
/synthesise-reviewsinstead
More from flonat/claude-research
update-focus
Use when you need to update current-focus.md with a structured session summary.
11project-safety
Use when you need to set up safety rules and folder structures for a research project.
11latex-autofix
Use when you need to compile LaTeX with autonomous error resolution and citation audit.
8literature
Use when you need academic literature discovery, synthesis, or bibliography management. Supports standalone searches and end-to-end project pipelines with vault sync and auto-commit.
8pre-submission-report
Use when you need all quality checks run before submission, producing a single dated report.
7process-reviews
Use when you need to process referee comments from a reviews PDF into tracking files.
7