story
Skill3 starsChanged 32 days agoMITView on GitHub
Use when you have requirements, PRDs, or feature descriptions that need to become implementable work. Transforms requirements into INVEST-compliant user stories with testable acceptance criteria.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- cjh-solver/MathModeling-Skills-Arsenaltheir own version, first seen Nov 8, 2026
- zenstory-ai/oh-story-claudecodetheir own version, first seen Nov 8, 2026
- hua695/MathModeling-Skills-Arsenaltheir own version, first seen Oct 25, 2026
- nschurmann/hola-aitheir own version, first seen Oct 25, 2026
- ES-92/esctheir own version, first seen Oct 20, 2026
- nicodiansk/turbochargeword for word, first seen Oct 13, 2026
Used with
Projects with it also use story-deslop, story-long-write and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
XiaoyangySkillstory-deslop
网文去AI味。检测并清除文本中的AI写作痕迹，让文字回归自然、非模板化。触发方式：/story-deslop、/去AI味、「去AI味」「这篇太AI了」「网文去AI味」。
Also in 5 projects that use this
- XiaoyangySkill
story-long-write
长篇网文写作方法论与 novel-studio pipeline 适配器。用于把长篇开书、大纲、日更、续写、重写等需求整理为 pipeline 输入；在 novel-studio 内禁止直接生成正文。触发方式：/story-long-write、/写长篇、「帮我开书」「写大纲」「日更」「续写」「继续写」「修改第X章」「回炉」「重写第X章」。
Also in 5 projects that use this
worldwondererSkillstory-cover
小说封面生成与提示词设计。根据书名、作者名和题材构建封面提示词；用户只要提示词时不生图，要求封面图时调用 GPT-Image-2，Codex CLI 优先使用内置 ImageGen。触发方式：/story-cover、/封面、「帮我做个封面」「生成封面图」「封面提示词」「封面设计」。
Also in 4 projects that use this
- worldwondererSkill
story-import
逆向导入已有小说。将已写好的小说（半成品或完本）反向解析为标准项目目录结构，兼容 story-long-write / story-short-write 后续写作流程；内部复用 story-long-analyze / story-short-analyze 的拆解管道，按篇幅自动分流。触发方式：/story-import、「导入小说」「反向解析」「导入」「把我的书导进来」。
Also in 4 projects that use this
marketcallsSkillstory-setup
Set up the story-telling environment. Checks Node, installs dependencies, creates .env from the template, verifies the Sarvam, fal and OpenAI keys, and confirms all Remotion packages are on one version.
Also in 5 projects that use this
badgidsSkillstory-review
Diagnose existing prose at a chosen editorial level, from whole-story and developmental problems through scene, line, copy, and proof passes, without rewriting until the diagnosis is accepted.
Also in 5 projects that use this
- +2 more from Xiaoyangy
- +3 more from worldwonderer
Other versions13 projects use a version of this.
Word for word · 1
- nicodiansk/turbocharge★ 3100% same
Edited · 0
None found.
Wrote their own version · 12
- worldwonderer/oh-story-claudecode★ 8.4ksame name
- zenstory-ai/oh-story-claudecode★ 8.4ksame name
- receptron/mulmocast-cli★ 476same name
- Xiaoyangy/novel-studio★ 122same name
- nschurmann/hola-ai★ 101same name
- cjh-solver/MathModeling-Skills-Arsenal★ 14same name
- hua695/MathModeling-Skills-Arsenal★ 12same name
- Storybloq/plugin-archive★ 8same name
- ByronFinn/dev-skills★ 4same name
- LightbridgeLab/CodeCannon★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- atlasSkill
- brainstormSkill
- buildSkill
- debugSkill
- planSkill
- reviewSkill
- setupSkill
- shipSkill
- wrapSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Every story must have testable acceptance criteria before implementation.
- Distinctive: line 22
Don't start work without criteria
- Distinctive: line 23
Don't assume "obvious" criteria
- Distinctive: line 24
Don't defer criteria to "later"
- Distinctive: line 29
Every story MUST pass:
- Distinctive: line 116
Run each story through all 6 criteria.
- Distinctive: line 119
Start with happy path
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Story Breakdown
Transform requirements into INVEST-compliant user stories with testable acceptance criteria.
Announce: "Using story breakdown to create implementable stories."
The Iron Law
NO STORY WITHOUT ACCEPTANCE CRITERIAEvery story must have testable acceptance criteria before implementation.
No exceptions:
- Don't start work without criteria
- Don't assume "obvious" criteria
- Don't defer criteria to "later"
- Later never comes
INVEST Criteria
Every story MUST pass:
| Criterion | Question | Failure Symptom |
| Independent | Can this ship without other stories? | "We need to do X first" |
| Negotiable | Can scope be discussed? | "It has to be exactly this" |
| Valuable | Does user/business care? | "It's technical debt" |
| Estimable | Can team size it? | "No idea how long" |
| Small | Fits in one iteration? | "It's a 2-week story" |
| Testable | Can we verify done? | "We'll know when we see it" |
Failing any criterion = story needs work.
Epic Template
# Epic: [Name]
## Problem Statement
[What problem does this solve? Who has this problem?]
## Success Metrics
- [Measurable outcome 1]
- [Measurable outcome 2]
## Scope
### In Scope
- [Feature/capability]
### Out of Scope
- [Explicitly excluded]
## Stories
1. [Story 1 title]
2. [Story 2 title]
## Dependencies
- [External dependencies]
## Risks
- [Risk]: [Mitigation]Story Template
# Story: [Title]
**As a** [role/persona],
**I want** [capability/feature],
**So that** [benefit/value].
## Acceptance Criteria
### Criterion 1: [Name]
**Given** [precondition]
**When** [action]
**Then** [expected result]
### Criterion 2: [Name]
**Given** [precondition]
**When** [action]
**Then** [expected result]
## Technical Notes
- [Implementation consideration]
## Story Points: [1/2/3/5/8]Breakdown Process
Phase 1: Understand the Epic
- Identify the user/persona
- State the core problem
- Define success metrics
- List what's explicitly OUT of scope
Phase 2: Slice by User Value
- What's the smallest valuable increment?
- Split by workflow, not by component
- Each story = one user capability
Good splits: By workflow step, user role, data type, happy path vs error Bad splits: By technical layer, by file, by developer
Phase 3: Apply INVEST
Run each story through all 6 criteria. Fix failures. Re-split if needed.
Phase 4: Write Acceptance Criteria
- Start with happy path
- Add error states
- Add edge cases
- Each criterion = one test case
Sizing Guide
| Points | Meaning | Example |
| 1 | Trivial | Copy change, config toggle |
| 2 | Simple | Add field, simple validation |
| 3 | Moderate | New form, basic CRUD |
| 5 | Complex | Multi-step flow, integration |
| 8 | Too large | Needs to be split |
If >5 points, split the story.
Red Flags — STOP
| Flag | Problem |
| "Technical story" | No user value — attach to user story |
| "As a developer" | Wrong persona — find the actual user |
| No acceptance criteria | Not a story — it's a wish |
| Vague criteria | "Works correctly" — define what correct means |
| >5 points | Too big — split it |
| Implementation in story | "Using React" — describe WHAT not HOW |
After Stories Are Complete
- Save to
docs/plans/YYYY-MM-DD-<feature>-stories.md - Commit
- Offer: "Ready for implementation planning?" → chains to
/turbocharge:plan
Workflow Position
brainstorm → story → plan → build → review → shipDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.