A guide for turning an established project idea or conversation into a wiki plan with Gherkin scenarios. Gherkin is a readable format for describing software behavior with given conditions, actions, and outcomes.

Use it to create a thin implementation plan, write one or more story files, and define acceptance scenarios from a conversation or approved intent.

It converts an agreed scope into small, testable stories without reopening the discovery interview. It keeps the stories linked to the project's intent and decisions.

to-stories — Skill for Claude Code by bartolli/kmd

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add bartolli/kmd --skill to-stories

Clone the repo

git clone --depth 1 https://github.com/bartolli/kmd

Made for: Claude Code.

Or install wiki-sdd, the plugin that ships this one along with the rest of its 10 skills, 5 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bartolli/kmd/to-stories/github.svg)](https://agentmods.dev/skills/bartolli/kmd/to-stories)

Your own site

<a href="https://agentmods.dev/skills/bartolli/kmd/to-stories"><img src="https://agentmods.dev/badge/skills/bartolli/kmd/to-stories/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bartolli/kmd/to-stories"><img src="https://agentmods.dev/badge/skills/bartolli/kmd/to-stories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 187 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,611 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00187	$0.02611
Opus 5.5	$0.00075	$0.01044
Sonnet 5.5	$0.00037	$0.00522
Haiku 4.5	$0.00019	$0.00261

Measured 1mo ago against content hash 5b841f105571, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

to-stories scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/claude/wiki-sdd/skills/to-stories/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

To Stories — Conversation or Intent into Wiki Stories

Two inputs, one output shape. From the current conversation, a thin orchestration plan plus per-story files. From a promoted intent, one story under the active plan. Does not interview — synthesizes what is already established. If intent isn't clear, suggest /intent first and stop.

Input B — a promoted intent

When /triage promotes an intent, or the user names one:

Read projects/<scope>/intent/intent-<slug>.md in full, then glossary.md and the ADRs it links.
Derive the story from the intent's sections — Problem and Proposed outcome become the User Story and the Problem line; the Falsification path becomes the first scenario, since it already names an observable outcome; Affected names the code paths for the slices; Constraints and Open questions land in the story's Decisions and scenarios respectively.
Write projects/<scope>/plan/<active-plan>/story-N-<slug>.md — next N in that plan — with [[intent-<slug>]] under References. No new plan for one story.
triage_state is what the operator chose at promotion: ready-for-agent when the brief is complete, needs-triage otherwise.
Add the Story Index row to the plan, then report the story slug back so triage writes promoted_to and archives the intent (the intent's frontmatter is triage's to close, not this skill's).

Everything below is Input A — the conversation.

Prerequisites

WIKI_SCOPE: <scope> declared in the project instructions. If missing, suggest /wiki and stop.
projects/<scope>/index.md exists. If missing, suggest /intent and stop.
The conversation has discussed a concrete piece of work (a feature, a refactor, a phase). If only abstract intent has been discussed, suggest /intent to nail it down first.

What this skill produces

projects/<scope>/
├── plan/
│   ├── plan-<name>.md                    ← thin orchestration (~60-100 lines)
│   └── <name>/
│       ├── story-1-<slug>.md             ← Gherkin + slices (~40-60 lines)
│       ├── story-2-<slug>.md
│       └── story-3-<slug>.md

Read the full file on GitHub · 226 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed 5b841f105571
1mo ago Changed 15e88030aecd
1mo ago First seen · 226 lines · 187 tokens per session scan A 2a14af7cbfbe

Subscribe to this mod's changes

to-stories is a skill published in the GitHub repository bartolli/kmd (7 stars, last pushed 1mo ago), licensed MIT. It adds 187 tokens to every session and 2,611 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Planning Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

to-stories