A workflow for turning rough input into a structured product specification. The specification records why something is needed, what it should do, its limits, what it will not do, and how success will be judged.

Use it to create, update, or validate a specification from material such as a product brief, requirements document, game design document, research note, or conversation.

It gives downstream development work a shared contract instead of leaving important decisions scattered across ideas, briefs, messages, and documents. Extra detail can be kept in companion files when it does not belong in the core specification.

bmad-spec — Skill for Claude Code and Codex by jeffrey2423: A workflow for turning rough input into a structured…

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.

agentmods

npx agentmods add skills/jeffrey2423/commit-like-pro/bmad-spec

Any agent

npx skills add jeffrey2423/commit-like-pro --skill bmad-spec

Clone the repo

git clone --depth 1 https://github.com/jeffrey2423/commit-like-pro

Made for: Claude Code, Codex.

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/jeffrey2423/commit-like-pro/bmad-spec.svg)](https://agentmods.dev/skills/jeffrey2423/commit-like-pro/bmad-spec)

Your own site

<a href="https://agentmods.dev/skills/jeffrey2423/commit-like-pro/bmad-spec"><img src="https://agentmods.dev/badge/skills/jeffrey2423/commit-like-pro/bmad-spec.svg" alt="Measured on agentmods" height="20"></a>

Per session 57 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. Scan, not verified.

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	$0.00057	$0.02611
Opus 5	$0.00028	$0.01306
Sonnet 5	$0.00011	$0.00522
Haiku 4.5	$0.00006	$0.00261

Measured 3d ago against content hash 13ecac915925, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bmad-spec 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 3d 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.

.claude/skills/bmad-spec/SKILL.md · 130 lines

How it starts

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

BMad Spec

Overview

Canonical transformer for the BMad spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces SPEC.md carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream BMad skill consumes.

Multiple skills may call to update the same spec over time.

Conventions

Bare paths (e.g. assets/spec-template.md) resolve from the skill root.
{skill-root} is this skill's install dir; {project-root} is the working dir.
{workflow.<name>} resolves to fields in customize.toml.

On Activation

Resolve customization: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read {skill-root}/customize.toml directly.
Run {workflow.activation_steps_prepend}. Treat {workflow.persistent_facts} as foundational context (file: entries are loaded).
Load {project-root}/_bmad/core/config.yaml (and config.user.yaml if present), root level and bmm section. Resolve {user_name}, {communication_language}, {document_output_language}, {planning_artifacts}, {project_name}, {date}.
Detect mode. Headless when any of: no TTY, programmatic caller (another skill or non-interactive runner), or the first message pre-supplies all inputs and asks for an artifact path back. Interactive otherwise. In interactive mode, greet by {user_name} in {communication_language}, stay in that language, and mention that bmad-party-mode and bmad-advanced-elicitation are available for deeper exploration on any field.

Run {workflow.activation_steps_append}.

Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

Read the full file on GitHub · 130 lines

Files

What ships with it

3 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.

3d ago First seen · 130 lines · 57 tokens per session scan A 13ecac915925

Subscribe to this mod's changes

bmad-spec is a skill published in the GitHub repository jeffrey2423/commit-like-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,611 once invoked, about $0.0003 per session on Opus 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-31.

Planning agents ai claude claude-code cli commit

git-iris

Use this skill when generating commit messages, pull request descriptions, release notes, changelogs, or code reviews in a repository where git-iris is available. Activates on requests like "commit this", "write a commit message", "draft a PR", "generate release notes", "write a changelog", or "review my changes" when…

hyperb1iss/git-iris · 81 tokens

implement

Execute tasks from track plan with TDD workflow and git commit integration.

MadAppGang/claude-code · 15 tokens

fix-pr-commit-titles

Bulk-rewrite commit titles on a PR branch to match [LKPR-N] format using filter-branch — avoids per-commit hook re-runs.

Jessinra/Lorekeeper · 38 tokens

lrc

Manage LiveReview code review for staged changes in this repo. Run /lrc review to open a browser-based AI review of staged changes before committing. Use /lrc skip to bypass review and write an attestation, or /lrc vouch to manually approve without AI. Check and toggle hook state with /lrc hooks status, hooks disable…

HexmosTech/git-lrc · 124 tokens

commit-convention

Git commit convention for Lorekeeper — enforced by commit-msg hook. Covers author identity, ticket tags, and message format for both PM (Akane) and Dev roles.