A workflow for implementing a software story from a completed story-specification file. A story is a small, user-focused unit of planned work with tasks and acceptance criteria.

Building the next planned story, satisfying its acceptance criteria, and recording the implementation details in the story file.

It keeps implementation tied to the written requirements and tracks tasks, changes, files, and completion status in one place.

How salazarsebas/Cougr configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to salazarsebas/Cougr. 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/salazarsebas/Cougr/main/.claude/skills/dev-story/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/salazarsebas/Cougr

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/salazarsebas/cougr/dev-story/github.svg)](https://agentmods.dev/skills/salazarsebas/cougr/dev-story)

Your own site

<a href="https://agentmods.dev/skills/salazarsebas/cougr/dev-story"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/dev-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/salazarsebas/cougr/dev-story"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/dev-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 5,649 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 97% copy Near-identical to another mod 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.00038	$0.05649
Opus 5.5	$0.00015	$0.02260
Sonnet 5.5	$0.00008	$0.01130
Haiku 4.5	$0.00004	$0.00565

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

Security

Grade A, and why

dev-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 today.

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

This is a copy

97% identical to bmad-dev-story — 47 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.

.claude/skills/dev-story/SKILL.md · 486 lines

How it starts

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

Dev Story Workflow

Goal: Execute story implementation following a context filled story spec file.

Your Role: Developer implementing the story.

Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
Generate all documents in {document_output_language}
Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
Execute ALL steps in exact order; do NOT skip steps
Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.
User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.

Conventions

Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/.stellar-build/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

{skill-root}/customize.toml - defaults
{project-root}/.stellar-build/custom/{skill-name}.toml - team overrides
{project-root}/.stellar-build/custom/{skill-name}.user.toml - personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Read the full file on GitHub · 486 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

today First seen · 486 lines · 38 tokens per session scan A b41235513a64

Subscribe to this mod's changes

dev-story is a skill published in the GitHub repository salazarsebas/Cougr (53 stars, last pushed 17d ago), licensed MIT. It adds 38 tokens to every session and 5,649 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to bmad-dev-story, differing in 47 lines, and is treated as a copy.

Project management blockchain-gaming ecs game-engine on-chain-games soroban

dev-story next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
dev-storysalazarsebas/Cougr	Skill	53	17d ago	MIT	A	38	Claude Code
llmginelordbasilaiassistant-sudo/llmgine	Skill	1	1mo ago	MIT	B	78	Claude Code, Codex
soundclawiamlukethedev/Claw3D	Skill	2.4k	2d ago	MIT	A	18	Claude Code, Codex
task-manageriamlukethedev/Claw3D	Skill	2.4k	2d ago	MIT	A	56	Claude Code, Codex
todoiamlukethedev/Claw3D	Skill	2.4k	2d ago	MIT	A	12	Claude Code, Codex
ecspressokayac/ecspresso	Skill	1.1k	today	MIT	A	17	Claude Code
html-to-uguiAlex-Rachel/TEngine	Skill	2.4k	today	MIT	A	75	Codex

Cougr: Skill for Claude Code