Revise an existing story based on updated instructions in its story-prompt.md.
Steps
- •Read
$ARGUMENTS/story-prompt.mdto get the current prompt with any new or changed instructions. - •Run
git diff $ARGUMENTS/story-prompt.mdto see what changed in the prompt. If there is no git diff (changes already committed), rungit log -1 -p -- $ARGUMENTS/story-prompt.mdto see the most recent change. - •Read the existing story file in
$ARGUMENTS/(the.mdfile that is notstory-prompt.md,preamble.md, orLICENSE-*). - •Read
CLAUDE.mdfor writing conventions. - •Rewrite the story, applying the prompt changes to the existing narrative. Preserve the story's structure, characters, plot, and tone — only modify what the prompt changes require. If the prompt changes are sweeping (e.g., change the setting entirely), rewrite accordingly while keeping the core narrative intact.
- •Write the revised story back to the same file, using the same format.
Story Format
The story file must begin with this header structure:
markdown
# Story Title ### *One-line tagline in italics* ### A Story by Claude & Mark Buckaway ---
If the prompt specifies a title or subtitle, use those. Otherwise keep the existing ones.
Then the story body, divided into titled parts using ## Part Name headings, separated by --- horizontal rules.
End the story with *fin.*
Guidelines
- •Apply prompt changes faithfully — if the prompt says to change the setting, characters, or plot elements, do so thoroughly and consistently throughout the entire story.
- •Maintain the same literary quality, pacing, and length as the original.
- •Default writing conventions from CLAUDE.md apply unless the prompt explicitly overrides them (e.g., "set the story in the US" overrides the Canadian setting convention).
- •Do not include any AI branding, tool mentions, or meta-commentary in the story file.
After Writing
Tell the user the story has been revised, summarize what changed, and suggest they review it. Do not commit, publish, or run any other scripts automatically.