brainstorm

Transform vague ideas into validated designs through structured dialogue.

74|14|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ActiveMemory/ctx --skill brainstorm-activememory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/ActiveMemory/ctx/tree/main/.claude/skills/brainstorm
Command: npx skills add https://github.com/ActiveMemory/ctx --skill brainstorm-activememory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform raw ideas into clear, validated designs through structured dialogue before any implementation begins.

Core Features & Use Cases

  • Structured clarification: ensure understanding of goals and constraints before designing.
  • Stepwise design process: understand current context, clarify ideas, capture non-functional requirements, and secure an Understanding Lock.
  • Decision logging: persist decisions and design rationale to the context to guide implementation.

Quick Start

Start by stating the goal and constraints, then provide an Understanding Summary and one design approach to proceed.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I turn vague software requirements into a validated design before coding?

To turn vague requirements into a validated design, use structured dialogue to clarify goals, capture non-functional constraints, and secure an Understanding Lock before implementation begins.

What is the best way to document architectural decisions during feature ideation?

To document architectural decisions during feature ideation, persist decisions and design rationale to `.context/DECISIONS.md`, ensuring shared context and guiding implementation across the software project.

How do I capture non-functional requirements during the design clarification process?

Capture non-functional requirements by applying a stepwise design process that reviews current context, clarifies ideas, and secures an explicit Understanding Lock before exploring design options.

Can I use structured dialogue to explore design options for architectural decisions?

Yes, structured dialogue enforces stepwise context review and explicit assumptions to explore design options for architectural decisions, producing a shared design and a documented decision log before coding.

Do I need an Understanding Lock to shape requirements across software projects?

Yes, an Understanding Lock ensures shared clarity of goals and constraints before designing, allowing you to safely shape requirements and proceed with feature ideation across software projects.

What are the limitations of brainstorming designs without stepwise context review?

Without stepwise context review, brainstorming designs risks missing non-functional requirements and explicit assumptions, leading to unvalidated architectural decisions and unaligned implementation.