agentmods.dev

brainstorm-feature

brainstorm-feature is a command for Claude Code from HoangNguyen0403/agent-skills-standard. It costs 0 tokens per session (905 once invoked), scanned A, original, MIT.

A structured brainstorming workflow that turns a rough product or engineering idea into a short business brief with goals, options, constraints, and measurable value.

In plain words
What is it for?
Use it to clarify the problem, compare possible approaches, identify stakeholders and risks, and define how success will be measured.
Why use it?
It makes vague requests concrete enough to evaluate before committing to product requirements or implementation work.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 565repo +4 3d ago A scan 0 tokens original MIT

Good fit Use it to clarify the problem, compare possible approaches, identify stakeholders and risks, and define how success will be measured.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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 brainstorm-feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature/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 brainstorm-feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/brainstorm-feature.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 905 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.00905
Opus 5 $0.00000 $0.00452
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00090

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

Security

Grade A, and why

brainstorm-feature 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.

.claude/commands/brainstorm-feature.md · 90 lines

How it starts

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

Brainstorm Feature

Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.

Input: $ARGUMENTS

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

Execute the following steps for $ARGUMENTS.

Brainstorm Feature Workflow (BRD-lite / Why)

Goal: Convert vague intent into a compact BA-owned BRD-lite brief before PM PRD planning or technical design.

Steps

  1. Gather intent:
    • Load baseline BRD section, common-business-requirements, and common-operator-profile.
    • Infer operator_profile (business | hybrid | technical) from request phrasing; never ask the operator to self-rate. Carry it in the Handoff Payload.
    • Draft a provisional brief before asking.
    • Capture objective, sponsor, validation owner, stakeholders, users, pain/opportunity, value hypothesis, SMART metric, constraints, glossary, non-goals, and delivery context.
  2. Explore options:
    • List 3 viable approaches.
    • Capture benefit, cost, risk, and unknowns for each.
    • Include funding/priority rationale.
    • Mark one recommended approach.
  3. Pressure-test:
    • Keep BRD solution-free; route functional behavior to PRD/SRS.
    • Check security, privacy, accessibility, performance, data, rollout risks, and measurable approval criteria.
    • Treat non-critical unknowns as assumptions.
    • Split stakeholder asks into candidate REQ-* placeholders and flag platform, market, permission, and edge-case gaps for PM.
  4. Decide:
    • Ask only true blocking product decisions, max 3 at a time.
    • Include a recommended default and 2-3 options for each question.
    • Record accepted approach and rejected alternatives.
    • Draft defaults before blocking: sponsor/validation owner = the requesting operator; SMART metric drafted from the stated pain (mark assumed); scope fence drafted from the request with explicit non-goals.
    • For operator_profile=business, present all three drafted defaults as one confirm-with-default question round (fits the max-3 rule) instead of blocking outright.
    • Continue on non-critical assumptions; return BLOCKED only when the operator rejects the drafted defaults, or in autonomous/channel mode with no confirmation channel available.
    • Save to docs/brd/brd-[slug].md when writes are allowed and route to plan-feature.

Read the full file on GitHub · 90 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 · 90 lines · 0 tokens per session scan A 187a773e6005

Subscribe to this mod's changes

brainstorm-feature is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 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-09-03.

PlanningProject managementReactbest-practicescoding-standardsflutternestjsnextjs
Related

Other commands, from other repositories

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 35 tokens

schedule

Register a scheduled agent job from a natural-language schedule request — parse the interval, resolve agent-id + prompt + workspace, call oma schedule:add, then confirm with oma schedule:list.

first-fluke/fullstack-starter · 35 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 19 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 20 tokens

work

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens