Story Workflow
Load to carry story work with an author from what they want to a page they accept: reading their intent, setting direction, producing and critiquing the prose, owning the verdict and the critique round limit, recording what settled, and presenting the result.
Install
/plugin marketplace add haowjy/creative-writing-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add haowjy/creative-writing-skills --skill story-workflowgit clone --depth 1 https://github.com/haowjy/creative-writing-skills.git /tmp/creative-writing-skills
mkdir -p ~/.claude/skills
cp -r /tmp/creative-writing-skills/plugin/claude/skills/story-workflow ~/.claude/skills/story-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Story Workflow Carry each piece of story work from the author's intent to a result they can accept. Keep going between steps: a draft or report coming back is evidence for your next move, not a stopping point. The author has the final say on direction and taste; the rest is yours to decide and state. ## Read the Intent Before planning or writing, form your read of what the author wants: the reader effect, the emotional target, the constraints, the taste signals, what should stay ambiguous or unsaid, and what would count as the wrong kind of success. Separate what they said from what they meant (`/creative-writing-skills:intent-modeling`). Check the project's terms and prior decisions in its files (`AGENTS.md`, the kb's vocab and topic pages) before asking about them, so the questions that reach the author are the ones only they can answer. When the work turns on terms or a direction the author has not settled, ask them until it is (`/creative-writing-skills:grill`). State your read in a line or two and proceed, so the author can correct it. Ask only when the answer would change the work, and ask every question that is ready at once. ## Set Direction Explore and decide direction with `/creative-writing-skills:story-planning`. Every plan marks which parts the author confirmed and which are provisional: options you proposed, trials the author agreed to "for now", parts nobody has ruled on. Mark a trial as a trial, so it never reaches a writer or the kb as a rule.
Details
- Skill name
story-workflow- Repository
- haowjy/creative-writing-skills
- Path
plugin/claude/skills/story-workflow/SKILL.md- License
- Apache-2.0
- Repo updated
- 16 November 2026
FAQ
What does the Story Workflow skill do?
Load to carry story work with an author from what they want to a page they accept: reading their intent, setting direction, producing and critiquing the prose, owning the verdict and the critique round limit, recording what settled, and presenting the result.
How do I install the Story Workflow skill?
Claude Code plugin: /plugin marketplace add haowjy/creative-writing-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Story Workflow popular?
It lives in haowjy/creative-writing-skills, which has 593 GitHub stars and 82 forks.
Related skills
Character Sim
593haowjy/creative-writing-skills
Load to speak as a specified character from what they know, how they talk, and what they feel now: in-character conversation, voice discovery, or a relationship pressure test. Pass the character, the story moment, and their style and character-state files.
Creative Research
593haowjy/creative-writing-skills
Load when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.
Creative Writing Craft
593haowjy/creative-writing-skills
Load when putting fiction on the page or judging how it reads there: the production modes (fresh draft, revision, bridge, alternate take, line polish), prose technique, scene mechanics, style analysis, and genre craft.
Tools
564ai-driven-dev/framework
Defines or modifies what the project targets, under src/contexts/tools/ — an AI/IDE tool profile, its build contract, the content-translation capability classes it composes (agents/skills/commands/rules/hooks), and its own native-plugin adapter. Use when adding a new AI or IDE tool, changing a tool's Has* capability intersection, adding or modifying a capability class, or declaring a tool's `aidd translate` build contract. Do NOT use for the canonical-to-native translation pipeline itself — use `translate`. Do NOT use for where plugin content comes from — use `distribution`. Do NOT use for man
Story Review
593haowjy/creative-writing-skills
Review work after prose exists: editorial review, craft critique, continuity/voice review, copyediting, proofreading, and synthesis of reader-sim signal. Load when diagnosing a draft rather than rewriting it.
Translate
564ai-driven-dev/framework
Builds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.