bmad-forge-idea

bmad-forge-idea is a skill for Claude Code from zsutxz/ClaudeLearning. It costs 56 tokens per session (2,246 once invoked), scanned A, a copy of bmad-forge-idea, MIT.

A conversation-based method for testing an unfinished idea by questioning its assumptions and possible weaknesses. It aims to clarify whether the idea should be strengthened, acted on, or rejected while changes are still inexpensive.

In plain words
What is it for?
Use it when pressure-testing, stress-testing, or hardening an idea. It can apply to product ideas, features, or other proposals and may optionally produce a handoff document.
Why use it?
It exposes unclear decisions and unsupported claims before they become costly product or feature problems. The process focuses on improving the thinking rather than automatically producing a build plan.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it when pressure-testing, stress-testing, or hardening an idea. It can apply to product ideas, features, or other proposals and may optionally produce a handoff document.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zsutxz/claudelearning/bmad-forge-idea
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.

Any agent
npx skills add zsutxz/ClaudeLearning --skill bmad-forge-idea
Clone the repo
git clone --depth 1 https://github.com/zsutxz/ClaudeLearning

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 bmad-forge-idea

README.md
[![agentmods](https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-forge-idea/github.svg)](https://agentmods.dev/skills/zsutxz/claudelearning/bmad-forge-idea)
Your own site
<a href="https://agentmods.dev/skills/zsutxz/claudelearning/bmad-forge-idea"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-forge-idea/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 bmad-forge-idea

Your own site · 80×15
<a href="https://agentmods.dev/skills/zsutxz/claudelearning/bmad-forge-idea"><img src="https://agentmods.dev/badge/skills/zsutxz/claudelearning/bmad-forge-idea.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,246 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 91% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.02246
Opus 5 $0.00028 $0.01123
Sonnet 5 $0.00011 $0.00449
Haiku 4.5 $0.00006 $0.00225

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

Security

Grade A, and why

bmad-forge-idea 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/resolve_personas.py, scripts/tests/test_resolve_personas.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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

91% identical to bmad-forge-idea — 4 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/bmad-forge-idea/SKILL.md · 108 lines

How it starts

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

BMad Forge Idea

Overview

Take a half-formed idea and pressure-test it in conversation, while changing your mind is still cheap, until it becomes something the user can act on with conviction or reject. The main risk is what the user has not examined yet: unchecked assumptions and unresolved decisions usually become more expensive problems later.

The main goal is better thinking, not producing an artifact. Strengthening an idea, rejecting it, or thinking it through more clearly are all complete outcomes. Writing forged-idea.md to hand off to another workflow is optional. Do not steer the conversation toward "shall we build it?"

This skill can be used on many kinds of ideas. When the idea is about a product or feature, what survives may be written to forged-idea.md for later planning.

Lead by questioning, not lecturing. Ask one question at a time, press on weak points, and do not let vague claims pass without examination.

Conventions

  • Scripts live in two places — run each from the exact path written, never assume co-location: the shared core scripts (memlog.py, resolve_customization.py, resolve_config.py) are installed by BMad core at {project-root}/_bmad/scripts/ and are never bundled here; this skill's own resolve_personas.py is at {skill-root}/scripts/.
  • {workflow.<name>} resolves to fields in the merged customize.toml [workflow] table.

On Activation

  1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read {skill-root}/customize.toml directly with defaults. Apply the resolved {workflow.*} values throughout.
  2. Run each {workflow.activation_steps_prepend} entry; treat each {workflow.persistent_facts} entry as foundational context (file: entries load their contents, skill: names a skill to consult, others are facts verbatim).
  3. Load {project-root}/_bmad/core/config.yaml (and config.user.yaml if present); resolve {user_name}, {communication_language}, {output_folder}. Missing → neutral defaults; never block. Greet {user_name} in {communication_language} and stay in it.
  4. Note whether a BMad persona is already active in this conversation — the user loaded one (e.g. the analyst, the storyteller) and invoked the forge from within it. If so, that persona leads the session, in voice, throughout.
  5. Resume: glob {workflow.forge_output_path}/**/.memlog.md (recursive, so it still finds sessions when run_folder_pattern is overridden to nest paths) and read only each match's frontmatter to find any whose status is not complete. Offer to resume one — then read its full memlog once to rebuild state and continue append-only — or to start fresh.
  6. Run each {workflow.activation_steps_append} entry.

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

  1. 9d ago First seen · 108 lines · 56 tokens per session scan A c62ac3a30a4c

Subscribe to this mod's changes

bmad-forge-idea is a skill published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,246 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to bmad-forge-idea, differing in 4 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens