mcpadvisor: Command for Claude Code

.claude/commands/BMad/tasks/create-next-story.md

create-next-story is a command for Claude Code from istarwyh/mcpadvisor. It costs 0 tokens per session (1,682 once invoked), scanned A, original, MIT.

A project-planning command that identifies the next logical development story and writes it as a complete, actionable file for an implementation agent.

In plain words
What is it for?
Use it to turn project progress and larger feature groups, called epics, into ready-to-implement development stories.
Why use it?
It removes the need to gather requirements, technical context, and acceptance criteria by hand before development starts.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is istarwyh/mcpadvisor's own configuration. It tells Claude Code how to work on mcpadvisor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcpadvisor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to istarwyh/mcpadvisor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/istarwyh/mcpadvisor/main/.claude/commands/BMad/tasks/create-next-story.md
Clone the repo
git clone --depth 1 https://github.com/istarwyh/mcpadvisor

Made for: Claude Code.

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.

agentmods badge for create-next-story

README.md
[![agentmods](https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/create-next-story/github.svg)](https://agentmods.dev/commands/istarwyh/mcpadvisor/create-next-story)
Your own site
<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/create-next-story"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/create-next-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.

agentmods 80×15 button for create-next-story

Your own site · 80×15
<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/create-next-story"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/create-next-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,682 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01682
Opus 5.5 $0.00000 $0.00673
Sonnet 5.5 $0.00000 $0.00336
Haiku 4.5 $0.00000 $0.00168

Measured 9d ago against content hash c3260dc4aae1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-next-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 9d 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.claude/commands/BMad/tasks/create-next-story.md · 118 lines

How it starts

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

/create-next-story Task

When this command is used, execute the following task:

Create Next Story Task

Purpose

To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the Story Template. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research or finding its own context.

SEQUENTIAL Task Execution (Do not proceed until current Task is complete)

0. Load Core Configuration and Check Workflow

  • Load .bmad-core/core-config.yaml from the project root
  • If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
  • Extract key configurations: devStoryLocation, prd.*, architecture.*, workflow.*

1. Identify Next Story for Preparation

1.1 Locate Epic Files and Review Existing Stories
  • Based on prdSharded from config, locate epic files (sharded location/pattern or monolithic PRD sections)
  • If devStoryLocation has story files, find {epicNum}.{storyNum}.*.md files (including legacy {epicNum}.{storyNum}.story.md) and select the highest epic/story pair numerically, not lexicographically. If multiple files have the same pair, stop and ask which is authoritative; do not overwrite either file.
  • If highest story exists:
    • Verify status is 'Done'. If not, alert user: "ALERT: Found incomplete story! File: {actualStoryPath} Status: [current status] You should fix this story first, but would you like to accept risk & override to create the next story in draft?"
    • If proceeding, select next sequential story in the current epic
    • If epic is complete, prompt user: "Epic {epicNum} Complete: All stories in Epic {epicNum} have been completed. Would you like to: 1) Begin Epic {epicNum + 1} with story 1 2) Select a specific story to work on 3) Cancel story creation"
    • CRITICAL: NEVER automatically skip to another epic. User MUST explicitly instruct which story to create.
  • If no story files exist: The next story is ALWAYS 1.1 (first story of first epic)
  • Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}"

Read the full file on GitHub · 118 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.

  1. 9d ago First seen · 118 lines · 0 tokens per session scan A c3260dc4aae1

Subscribe to this mod's changes

create-next-story is a command published in the GitHub repository istarwyh/mcpadvisor (89 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,682 tokens. 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-10-12.