agentleFS
paoloirrerapaoloirrera/ccgraph/.claude/skills/story-new/SKILL.md

story-new

Skill1 starsChanged 4 months agoMIT-0View on GitHub

Draft a new AI-DLC user story from a one-line idea into .local/user-stories/<name>/story.md

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. marketcalls/story-telling★ 4same name

    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 repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Distinctive:

    If no slug is given, propose one (kebab-case, derived from the idea) and confirm it.

    line 14
  2. Distinctive:

    Keep it a *story*, not a design: describe what and why, defer how to the design doc.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/story-new — draft a user story

Kicks off the AI-DLC pipeline (inception phase) by turning a rough idea into a structured story.md. This is step 1 of: story-new → story-refine → design-doc → tasks → (build) → pr-draft.

Input

The user's argument is a short idea and (ideally) a slug for the folder, e.g. /story-new weather-tool "an MCP tool that fetches current weather for a city".

If no slug is given, propose one (kebab-case, derived from the idea) and confirm it.

Steps

  1. Resolve the target folder. .local/user-stories/<slug>/. If it already exists and contains a story.md, STOP and ask whether to overwrite or pick a new slug — never clobber silently.
  2. Read the template in references/story-template.md (bundled in this skill folder). It is the canonical shape. Match its section order and conventions.
  3. Draft the story. Fill the template from the idea. It is fine — expected — to leave Investigation outcomes sparse and mark unknowns explicitly as ⏳ open: items; /story-refine resolves those next. Do NOT invent library versions, API shapes, or AWS contract details you haven't verified — flag them as open questions instead.
  4. Show the draft to the user (the full proposed story.md) and ask for approval or edits. Do not write the file until the user confirms.
  5. On confirmation, write .local/user-stories/<slug>/story.md and tell the user the path plus the suggested next step: /story-refine <slug>.

Conventions

  • Stories live under .local/user-stories/<slug>/ — this is gitignored working space, by design.
  • Keep it a story, not a design: describe what and why, defer how to the design doc.
  • The Definition of Done is a checkbox list of observable, testable outcomes.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.