se-brainstorm

Guide structured brainstorming through phases, constraints, and decision criteria.

Updated May 7, 2026

Search Tags:#planning #brainstorming #collaboration #requirements #process

Ready to run

npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-brainstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: se-brainstorm
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-brainstorm
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming for software projects often lacks structure, risking unclear scope and missed decisions. This skill provides a guided, phase-based conversation that surfaces goals, constraints, and success criteria before drafting a requirements document. It enables a repeatable process for exploring options and aligning stakeholders.

Core Features & Use Cases

Guided, one-question-at-a-time collaboration to surface assumptions, constraints, and success criteria.
Phase-driven flow (Phase 0 to Phase 4) that surfaces a synthesis and prepares for requirements capture.
Universal-brainstorming mode for non-software domains when needed.

Quick Start

Describe the feature you want to brainstorm, and I'll guide a structured, phase-based brainstorm.

Frequently Asked Questions about se-brainstorm

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

FAQPage Schema

How do I structure brainstorming for software projects before writing requirements?▼

Structured brainstorming for software projects uses a guided, phase-based conversation to surface goals, constraints, and success criteria. This process explores options and aligns stakeholders before you draft a requirements document.

Can I use guided brainstorming for non-software product ideas?▼

Yes, you can use guided brainstorming for non-software product ideas by engaging a universal-brainstorming mode. This mode handles non-software domains by guiding users through phases and decision criteria to surface what to build.

What is the best way to align stakeholders on product scope and decisions?▼

The best way to align stakeholders on product scope is through one-question-at-a-time collaboration. This guided approach surfaces assumptions, constraints, and success criteria to prevent unclear scope and missed decisions.

How do I know what to build when starting a new software feature?▼

To determine what to build, you can use a phase-driven flow that guides you from Phase 0 to Phase 4. This structured brainstorming surfaces a synthesis that informs the requirements doc and planning phase, including scope boundaries.

Does structured brainstorming replace the requirements planning phase?▼

No, structured brainstorming does not replace the requirements planning phase. It precedes planning by outputting a synthesis of key questions to resolve and scope boundaries, which directly informs and prepares the requirements capture.