Story Workflow logo

Story Workflow

Community
haowjy
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.

Overview

Publisherhaowjy
Repositorycreative-writing-skills
Skill namestory-workflow
Stars
553
Forks
75
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by haowjy on GitHub. Read the source before you install it.

Installation

Install the Story Workflow AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/haowjy/creative-writing-skills/tree/main/plugin/claude/skills/story-workflow
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git 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-workflow
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Story Workflow in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Story Workflow on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Story Workflow is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 decision 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, grill them on it with /creative-writing-skills:grill-with-docs.

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. Keep the author's hedges in their own words, so a trial never reaches a writer or the kb as a rule.

Produce

Draft and revise the prose with /creative-writing-skills:writing-principles loaded, following /creative-writing-skills:creative-writing-craft resources/prose-modes.md. For a pivotal passage whose direction the page has not proven, write two takes that change a real variable and say what each one shows.

When you can spawn this package's agents (@critic, @writer, @kb-lead and the rest), spawn the lanes that need a context of their own, as /creative-writing-skills:writing-staffing describes: critique, continuity, reader simulation, research, alternate takes, and knowledge capture. A critic that did not write the draft reads it the way a reader will, and a lane on another model brings other blind spots. Without them, run each lane yourself as its own pass, with the skill its agent would load (/creative-writing-skills:story-review, /creative-writing-skills:reader-sim, /creative-writing-skills:creative-research, /creative-writing-skills:character-sim, /creative-writing-skills:shared-dao, /creative-writing-skills:story-memory), and finish one stance before taking up the next: draft before judging, critique from the reader's side, revise the highest-impact issue first.

Own the Verdict

Read every draft and report yourself, and decide the next move: revise, explore an alternative, run another lane, ask the author, or present. Reports are evidence; resolve their conflicts against the author's intent and the page.

Count critique rounds per chapter, or per piece for work shorter than a chapter: a round is one critique pass and the revision it calls for. After two completed rounds, stop sending critique: present the work with the concerns still open, and the author decides whether to revise again, change direction, or accept it.

After Work Settles

When a chapter, a revision, or an author ruling settles and the work will pause, record what settled. When you can spawn @kb-lead, do: tell it to load /creative-writing-skills:story-memory, and brief it with what settled, the files that show it, and the author's decisions quoted with their hedges. Otherwise apply /creative-writing-skills:story-memory yourself. Brainstorms, drafts, and provisional choices stay in the work directory; the kb records as settled only what the author confirmed or the finished prose establishes.

Present

Tell the author what changed, what works, what still concerns you, and the decision you need from them when the next move turns on taste or direction. Give your synthesis, not raw reports. If character state (/creative-writing-skills:story-memory resources/kb-layout.md) is stale against the new prose, say so and ask whether to update it.

Frequently asked questions

What does the Story Workflow AI 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.

Why use Story Workflow on TypingMind?

Because you install it once and use it with any model. Story Workflow is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Story Workflow in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/haowjy/creative-writing-skills/tree/main/plugin/claude/skills/story-workflow. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Story Workflow?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Story Workflow?

As many as you like. As long as a model supports skills, you can use Story Workflow with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Story Workflow AI skill free?

Yes. It is published on GitHub by haowjy under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇