ais.spec.brainstorm

Generate Spec Seed Briefs from project context and initial ideas.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-spec-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ais.spec.brainstorm
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/.cursor/skills/ais.spec.brainstorm
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-spec-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of converting initial ideas into comprehensive, actionable Spec Seed Briefs, bridging the gap between raw concepts and formalized feature specifications.

Core Features & Use Cases

  • Discovery Facilitation: Turn early ideas into concise, actionable briefs for feature spec creation.
  • Contextual Analysis: Incorporates project and setup artifacts to shape briefs that consider current context.
  • Iterative Clarification: Guides users through a structured process to refine ideas and ensure clarity.
  • Seed Brief Production: Outputs a detailed brief including problem statement, users, outcomes, and more.
  • Optional Persistence: Allows saving the brief for future reference if desired.

Quick Start

Begin brainstorming a new feature spec for 'AI project X' by running: ais.spec.brainstorm --save --title "AI project X brainstorm" --brief "Initial thoughts and considerations..."

Frequently Asked Questions about ais.spec.brainstorm

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

FAQPage Schema
How do I convert initial ideas into actionable feature specifications?

To convert initial ideas into feature specifications, run the Skill with an initial title and brief to generate a Spec Seed Brief. It analyzes project context to identify problems, users, and outcomes before any code or design begins.

What is a Spec Seed Brief and when do I need one for product development?

A Spec Seed Brief is an early-stage document that bridges raw concepts and formalized feature specifications. You need one during project planning to define problem statements, target users, and expected outcomes before development starts.

How do I brainstorm feature specs using existing project context?

To brainstorm feature specs using project context, the Skill incorporates your project and setup artifacts during the analysis. It guides you through iterative clarification to refine ideas and ensure clarity for your specific environment.

Can I save a Spec Seed Brief for future reference during feature specification?

Yes, you can save a Spec Seed Brief for future reference by running the command with the save flag. This optional persistence ensures your brainstormed problem statements and outcomes remain accessible for downstream product development.

What is the best way to structure early project planning before code development?

The best way to structure early project planning is to use a structured process that explores possible approaches and identifies problems, users, and outcomes. This ensures your feature specification is clear, actionable, and grounded in actual project requirements.

Do I need existing code or design artifacts to start idea brainstorming for feature specs?

No, you do not need existing code or design artifacts to start idea brainstorming for feature specs. The Skill is designed specifically for the early stages of feature specification, operating before any code or design has commenced.