speckit-brainstorm

Plans a new feature and generates approved idea.md plus orchestrator-state.json for the SpecKit pipeline.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/lamtuanvu/agentskills --skill speckit-brainstorm-lamtuanvu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-brainstorm
Source: https://github.com/lamtuanvu/agentskills/tree/main/skills/speckit-brainstorm
Command: npx skills add https://github.com/lamtuanvu/agentskills --skill speckit-brainstorm-lamtuanvu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Brainstorming and planning a new feature before the SpecKit pipeline executes.

Core Features & Use Cases

  • Guided brainstorming to clarify intent, scope, and success criteria.
  • Define requirements and create an approved idea.md template for downstream execution.
  • Generate orchestrator artifacts (orchestrator-state.json) and branch plans for the SpecKit workflow.

Quick Start

Invoke speckit-brainstorm to start brainstorming, then obtain user approval and run speckit-orchestrator to generate idea.md and orchestrator-state.json.

Frequently Asked Questions about speckit-brainstorm

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

FAQPage Schema
How do I brainstorm and plan a new feature before starting development?

Feature planning requires clarifying intent, scope, and success criteria through guided questions. This process produces an approved idea.md and an orchestrator-state.json to drive downstream execution steps.

What is an idea.md file and when do I need it for feature planning?

An idea.md is a template that defines feature requirements after early-stage ideation. You need it when scoping a new feature across product and engineering teams to ensure downstream pipeline execution has approved requirements.

How do I create an orchestrator-state.json file for my workflow?

An orchestrator-state.json is generated alongside a new feature branch plan after brainstorming is approved. It serves as an artifact to drive downstream steps in the SpecKit workflow pipeline.

Can I use guided brainstorming for early-stage feature scoping across product and engineering teams?

Guided brainstorming is designed for early-stage ideation and feature scoping across product and engineering teams. It clarifies intent, scope, and success criteria to align stakeholders before requirements are finalized.

What's the best way to define requirements before executing a feature development pipeline?

The best way to define requirements is through guided brainstorming that clarifies scope and creates an approved idea.md template. This ensures the downstream pipeline receives structured, approved requirements before execution begins.

Do I need user approval before generating orchestrator artifacts for my feature branch?

User approval is required after brainstorming and before generating the idea.md and orchestrator-state.json artifacts. Once approved, these artifacts create a new feature branch plan to drive the downstream workflow steps.