Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/story/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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.
[](https://agentmods.dev/skills/rakovi4/continue-framework/story)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/story"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/story/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.
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/story"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01824 |
| Opus 5.5 | $0.00016 | $0.00730 |
| Sonnet 5.5 | $0.00008 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
story 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Story to Backlog
Add a story row to the Backlog table in ProductSpecification/stories.md.
This skill does NOT generate a story specification — spec generation is
dispatched by /continue via .claude/templates/spec/story-spec-generation.md
when the story's spec phase starts (see .claude/rules/workflow.md Lifecycle).
Usage
/story "Story name" # Add named story to the Backlog
/story # Ask for the story name, then add
A bare-number argument is not a story name (the retired spec-generation
/story selected stories by number) — ask what the user meant instead of
adding a row named after the number.
Workflow
Phase 1: Read the story map
Read ProductSpecification/stories.md — all three tables (In Progress,
Backlog, Done).
Phase 2: Duplicate check
If the requested name matches an existing row in any table (case-insensitive, ignoring punctuation), report the existing row and its table instead of adding a duplicate. Stop.
Phase 3: Quality gate — pain or opportunity
A story is a pain to be cured or an opportunity to be gained for a user. Before adding the row, test the requested story against both rejection patterns below. Do not silently accept a story that fails one.
- Tech story — names a solution or technology instead of a user outcome
(e.g., "add message-queue streaming", "migrate to a new cache"). Technology
choices are implementation decisions made inside a story's scenarios, not
stories. Ask what user pain or opportunity the technology serves, and
propose the story reformulated around that value (e.g., "add message-queue
streaming" → "a user sees updates without refreshing"). When the work has
no user-facing outcome at all — a purely internal migration or clean-up —
point at
/task(a refactor task) as its home: the story lifecycle would run interview, mockups, and frontend phases over work with no user to interview and no screen to mock up. - Part-story — a fragment of a user journey with no independent value: a step, precondition, or continuation of another behavior (e.g., "log in and download the file" + "remove the watermark from the downloaded file" instead of "remove the watermark"). Propose the single story that carries the whole user value — preconditions and steps belong to that story's flow, not to separate rows. When that whole-value story is already a row, the fragment belongs inside its scope: report that row and stop rather than appending a second, overlapping row.
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.
- 2mo ago First seen · 153 lines · 40 tokens per session scan A d3cca872d499
story is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 40 tokens to every session and 1,824 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.