Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. 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/hollandkevint/thinkhaven/main/.claude/commands/BMad/tasks/validate-next-story.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/commands/hollandkevint/thinkhaven/validate-next-story)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/validate-next-story"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/validate-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.
<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/validate-next-story"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/validate-next-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01277 |
| Opus 5 | $0.00000 | $0.00639 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
validate-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 10d 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.
This is a copy
94% identical to validate-next-story — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate-next-story Task
When this command is used, execute the following task:
Validate Next Story Task
Purpose
To comprehensively validate a story draft before implementation begins, ensuring it is complete, accurate, and provides sufficient context for successful development. This task identifies issues and gaps that need to be addressed, preventing hallucinations and ensuring implementation readiness.
SEQUENTIAL Task Execution (Do not proceed until current Task is complete)
0. Load Core Configuration and Inputs
- Load
.bmad-core/core-config.yaml - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
- Extract key configurations:
devStoryLocation,prd.*,architecture.* - Identify and load the following inputs:
- Story file: The drafted story to validate (provided by user or discovered in
devStoryLocation) - Parent epic: The epic containing this story's requirements
- Architecture documents: Based on configuration (sharded or monolithic)
- Story template:
bmad-core/templates/story-tmpl.mdfor completeness validation
- Story file: The drafted story to validate (provided by user or discovered in
1. Template Completeness Validation
- Load
bmad-core/templates/story-tmpl.mdand extract all section headings from the template - Missing sections check: Compare story sections against template sections to verify all required sections are present
- Placeholder validation: Ensure no template placeholders remain unfilled (e.g.,
{{EpicNum}},{{role}},_TBD_) - Agent section verification: Confirm all sections from template exist for future agent use
- Structure compliance: Verify story follows template structure and formatting
2. File Structure and Source Tree Validation
- File paths clarity: Are new/existing files to be created/modified clearly specified?
- Source tree relevance: Is relevant project structure included in Dev Notes?
- Directory structure: Are new directories/components properly located according to project structure?
- File creation sequence: Do tasks specify where files should be created in logical order?
- Path accuracy: Are file paths consistent with project structure from architecture docs?
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.
- 10d ago First seen · 141 lines · 0 tokens per session scan A 6f8e3ab89348
validate-next-story is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,277 tokens. A static security scan graded it A with 0 findings. It is 94% identical to validate-next-story, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.