ferrox-brainstorm

Structures brainstorming sessions into approved documents with explicit exits.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-brainstorm
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-brainstorm
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when you have an idea, a blank page, or an early-stage decision and need structured thinking that leads to an approved artifact instead of endless open-ended discussion.

Core Features & Use Cases

  • Three brainstorming stances: Uses guided, generative, or sounding-board mode depending on whether the task is a concrete decision, a blank-page ideation problem, or collaborative creative exploration.
  • Research-supported ideation: Can launch parallel researcher subagents when needed so the discussion is grounded before moving toward a decision.
  • Controlled output flow: Produces a saved brainstorm document with explicit exits for promotion, milestone seeding, or parking the work for later.
  • Use Case: A product lead can use it to explore pricing ideas, compare approaches, and end with a reviewable plan ready for the next workflow step.

Quick Start

Ask the skill to brainstorm a topic such as pricing model for the API tier and choose whether you want research support.

Frequently Asked Questions about ferrox-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague product ideas into an approved plan?

Structured brainstorming workflows transform vague ideas into approved plans by using stance selection, optional parallel research, and gated exits that promote only confirmed outcomes into reviewable artifacts.

What is the best way to compare multiple product strategy directions before committing?

Comparing product strategy directions requires a sounding-board brainstorming stance that structures topic ideation, captures written session notes, and parks unpromoted ideas before final commitment.

How do I run a brainstorming session that includes research support?

Research-supported ideation launches parallel researcher subagents during the brainstorming workflow to ground the discussion, ensuring early-stage product decisions are backed by data before reaching a gated exit.

Can I use structured ideation for early-stage creative exploration and topic ideation?

Structured ideation supports early-stage creative exploration and topic ideation through generative and sounding-board modes, allowing multiple directions to be compared and documented before selecting a confirmed outcome.

Does this brainstorming workflow produce a saved document for milestone seeding?

The workflow produces a saved brainstorm document with explicit gated exits for promotion, milestone seeding, or parking the work, ensuring only confirmed outcomes advance to the next workflow step.

When should I not use an open-ended brainstorming approach for product decisions?

Avoid open-ended discussion for early-stage product decisions when you need an approved artifact, as controlled output flows with written session notes and gated exits prevent endless exploration without commitment.