manuscript-revision-agent-files

Manuscript Revision Agent Files Scaffold

Trigger

• Use when a LaTeX IEEE-style manuscript-writing workspace needs revision-specific coordination on top of the parent manuscript-writing-agent-files contract.
• Use when joint manuscript and response-letter drafting requires REVISION_TASK.md alongside the four core AGENT files.
• Do not use for standalone manuscript writing or drafting without revision-response coordination; route to manuscript-writing-agent-files.
• Do not use for generic agent-file scaffolding; route to agent-files.
• Do not use to curate or revise an existing AGENT_GOAL.md; goal curation is outside this skill's write surface.
• Do not use when only REVISION_TASK.md is wanted without the core four-file contract — the sidecar is lower precedence than the control contract and is not authoritative on its own.

Inputs

• target_dir: directory where the parent manuscript-writing AGENT files will be scaffolded before revision-specific sidecar handling
• mission: one- or two-sentence long-term manuscript-writing or revision mission statement passed to manuscript-writing-agent-files and written into AGENT_GOAL.md; required so the scaffolded contract is internally consistent on first read. It must not include reusable editing rules, formatting preferences, current task state, transient response-letter tasks, response-letter next steps, or transient objectives.
• objective: optional concrete in-flight objective written into AGENT_PROGRESS.md; it must be transient current manuscript-writing or revision work, not a second mission statement or permanent scope rule. When omitted, the ## Current Objective section is removed rather than left as a literal placeholder
• overwrite: when true, existing parent scaffold files may be replaced by manuscript-writing-agent-files, and this skill refreshes only its own child-owned harness extension plus REVISION_TASK.md; otherwise only compatible existing parent files, the child harness extension, and sidecar are recorded in files_skipped