Triage an editorial letter into an actionable revision plan
Ingests an editorial letter or beta feedback and produces a structured revision plan: which notes to accept, which to push back on and why, which conflict, and the order to tackle them.
In / outEditorial letter / beta notes → revision plan with accept/reject/push-back per note and ordered action list
You might say…
“Twenty pages of editorial notes used to paralyse me — this turns them into a ranked action list I can start on the same day.”
What it does
Single-judgement skill: ingests a body of external feedback — an editorial letter, developmental notes, copy-edit markup, or collated beta-reader comments — and turns it into a structured revision plan: which notes to accept, which to push back on and why, which conflict with each other, and the order to tackle them in. The author owns which notes to act on. Used when feedback first arrives on a near-complete asset.
Trigger: Use when feedback first arrives on a near-complete asset to convert it into an actionable plan.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation