skills.rest
arbiterForge
arbiterForgeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

brainstorming

Refine rough feature ideas into approved, testable specifications with acceptance criteria.

139|7|Updated May 8, 2026
Search Tags:#brainstorming#specification#acceptance-criteria#open-questions#feature-planning#socratic-review
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill brainstorming-arbiterforge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/brainstorming
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill brainstorming-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents vague feature ideas from reaching implementation before they are clear, testable, and approved. It helps teams surface scope, hidden complexity, and unresolved questions early so coding starts from a concrete spec instead of assumptions.

Core Features & Use Cases

  • Problem framing: turns a one-line idea into a precise statement of the user pain, the caller, and the out-of-scope boundary.
  • Socratic refinement: asks one focused question at a time to replace vague language with concrete decisions, trade-offs, and recorded open questions.
  • Spec writing and handoff: writes an approved spec with numbered acceptance criteria and prepares it for downstream implementation planning.
  • Use case: A product lead says "add notifications," and the Skill helps define exactly which notifications, for whom, under what triggers, and what the acceptance tests must prove.

Quick Start

Use the brainstorming skill to turn this rough feature idea into an approved spec with clear acceptance criteria and open questions.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn rough feature ideas into testable specifications?▼

Feature planning refines rough ideas into testable specifications through problem framing and Socratic clarification. This replaces vague language with concrete decisions, trade-offs, and recorded open questions before implementation begins.

What is the best way to define acceptance criteria for pre-code planning?▼

Acceptance criteria are defined by writing single-test statements during the spec handoff phase. This process ensures feature specifications include clear, testable boundaries and scope framing before any coding starts.

How does Socratic refinement work for feature planning?▼

Socratic refinement asks one focused question at a time to clarify vague feature ideas. This method surfaces hidden complexity, records open questions, and documents specific trade-offs to replace assumptions with concrete decisions.

Can I use this for sprint workflows and scope framing?▼

Yes, this applies directly to pre-code planning for sprint workflows. It handles scope framing by defining the user pain, the caller, and the out-of-scope boundary before passing the approved spec downstream.

What are the limitations of starting implementation before spec handoff?▼

Starting implementation before spec handoff risks coding from assumptions and facing unresolved questions. Phased gating requires an approved specification with numbered acceptance criteria to prevent vague ideas from reaching development.

Related Skills

Explore More Software Engineering Skills→
Imad-OuteImad-Oute
2

mh-cto-sdlc-ideate

Define testable problem statements and evaluate assumptions for SDLC phase 0.

Community
Advanced
LumenWipeLumenWipe
3

elliot-dev

Execute approved software stories using test-first implementation and verification.

Official
Advanced
LGuguiLGugui

nova-feature

Generate feature specification documents in Markdown format.

Community
Intermediate
EwallywEwallyw

deep-interview

Clarify and validate ideas through Socratic questioning with ambiguity scoring.

Community
Advanced