Claude prompt for creative writing: Pacing Pass (Common Fixes)
Claude · Creative Writing · Common Fixes
You are a systems thinker using Claude for creative writing, specifically pacing pass.
Job: tighten a slow chapter.
Audience: editors. Constraint: cut explanation.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Claude creative writing template when editors need pacing pass with the rule: cut explanation. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
For Anthropic models, creative writing prompts fail when they mix strategy and execution. This pacing pass brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Uses diagnostic language that matches how practitioners actually brief work.
- Centers tighten a slow chapter so success is observable.
- Repeats the hard constraint: cut explanation.
- Separates draft from critique so you can steal the structure later.
- Names a clear job so Claude does not wander into generic advice.
How to use it in Claude
Paste the prompt into Claude and replace bracketed details with your facts. This Common Fixes path is for editors who care about tighten a slow chapter. Redact client names; keep structure. Slug pacing-pass-fixes is your canonical URL for this brief. Add one real example from your last week of work so the model mirrors your domain. Name the success metric aloud: tighten a slow chapter. If the draft cannot pass it, do not polish prose yet.
Start with the ugly first pass for pacing pass. Name what is wrong in five bullets, then rerun in Claude. For pacing pass in creative writing, the failure mode is usually no example. This prompt blocks that by design — especially "cut explanation". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for pacing pass; they cannot invent metrics or brand rules. authors and storytellers teams bookmark slug pacing-pass-fixes when typical failures and how to repair the prompt matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (editors, offer, timeline).
- Confirm the constraint is still visible: cut explanation.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Pacing Pass, 3 short sections, bullet list of recommendations, closing line that states cut explanation. Facts you supply appear; nothing invented.
Common mistakes
- Deleting "cut explanation" to save space — that is usually the whole point.
- Ignoring the output contract headings.
- Asking for pacing pass plus three other jobs in one message.
Expert notes
Slug pacing-pass-fixes: a authors and storytellers-oriented creative writing brief. Scenes, voice, character, and narrative craft. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if cut explanation no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a pacing pass piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Keep cut explanation visible in the prompt, not only in your head.
- Creative Writing work needs scenes, voice, character, and narrative craft.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Compare against other Claude angles on the same use case before you standardize.
- If text output drifts, re-anchor with cut explanation.
FAQ
- What is a Claude prompt for pacing pass?
- It is a structured brief that tells Claude how to produce creative writing output for editors. This common fixes version stresses typical failures and how to repair the prompt and keeps "cut explanation" in the instructions.
- How do I customize this Claude creative writing prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "cut explanation" should stay unless your brief truly changed.
- Why use the common fixes angle for pacing pass?
- Different angles solve different failures. Common Fixes helps when editors need typical failures and how to repair the prompt. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.