brainstorming

Guides collaborative design dialogue to produce approved spec documents before implementation.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill brainstorming-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/brainstorming
Command: npx skills add https://github.com/SummerEngine/summer --skill brainstorming-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents wasted implementation work by forcing requirements exploration, approach comparison, and user-approved design specs before any code is written. ## Core Features & Use Cases - Structured Discovery: Explores project context, then asks clarifying questions one at a time to pin down purpose, constraints, and success criteria. - Design Approval Gate: Proposes 2-3 approaches with trade-offs, presents the design in sections, and blocks all implementation until the user approves. - Spec Documentation: Writes the validated design to .summer/specs/YYYY-MM-DD-<topic>-design.md, runs a self-review for placeholders and contradictions, and commits it to git. - Use Case: Before building a new game mechanic, run this Skill to decompose scope, settle the design with the user, and hand off an approved spec to the writing-plans skill. ## Quick Start Ask the agent to brainstorm and design the new feature with you before writing any code.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn a game feature idea into a design spec?

Run the brainstorming flow: explore the current project context, answer clarifying questions one at a time, compare 2-3 proposed approaches, then approve the presented design. The validated spec is written to .summer/specs/ and committed to git.

What is the brainstorming skill in Summer Engine?

It is a mandatory pre-implementation workflow skill that turns ideas into approved design specs through collaborative dialogue. It blocks all coding, scaffolding, and implementation skills until the user approves a written design document.

Can I skip the design step for a simple feature?

No. The skill enforces a hard gate requiring a presented design and user approval for every project, including simple ones. The design can be only a few sentences for trivial work, but approval is still required.

What happens after the design spec is approved?

After the user reviews and approves the committed spec file, the skill invokes the writing-plans skill to create a detailed implementation plan. It never invokes implementation skills like frontend-design or mcp-builder directly.

How does it handle projects that are too large for one spec?

It flags multi-subsystem requests immediately and helps decompose them into independent sub-projects with defined relationships and build order. Each sub-project then gets its own spec, plan, and implementation cycle.