brainstorming

Name: brainstorming
Availability: InStock
Author: zhanglongxiao111

Turn user intent into an approved design specification before implementation.

35|5|Updated Sep 20, 2025

Search Tags:#architecture #brainstorming #implementation planning #requirements #design spec #review gate #project decomposition

Ready to run

npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill brainstorming-zhanglongxiao111

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/zhanglongxiao111/indesign-cli/tree/main/.codex/skills/brainstorming
Command: npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill brainstorming-zhanglongxiao111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted implementation by forcing an explicit design and approval step before any build or code-writing begins.

Core Features & Use Cases

Context-first design: explores the current project state (files, docs, recent commits) before deciding what to build.
Question-driven clarification: asks one clarifying question at a time to converge on purpose, constraints, and success criteria.
Design presentation with gates: proposes 2–3 approaches with trade-offs, then presents the design in sections and requires user approval after each section before proceeding.
Spec authoring + review loop: writes a validated design doc to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md, commits it, self-reviews for placeholders/ambiguity, and asks the user to review the spec before planning implementation.
Hard implementation guardrails: includes a hard-gate to avoid invoking any implementation skills until design approval is obtained; after approval, it transitions by invoking writing-plans only.

Quick Start

Start by using brainstorming to create and present a design for the requested change, then wait for your approval of the written spec before any implementation plan is generated.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn project ideas into an approved design spec before coding?▼

To turn ideas into an approved design spec, use a pre-implementation design workflow that enforces stepwise questioning, architecture decisions, and section-by-section user approval before any code is written.

What is the best way to evaluate architecture trade-offs during project decomposition?▼

Evaluating architecture trade-offs during project decomposition involves proposing 2–3 approaches, comparing their constraints, and requiring explicit user approval on each design section before proceeding to spec authoring.

How do I write and validate a design spec for implementation planning?▼

Writing and validating a design spec requires authoring a design document, committing it, performing a self-review for placeholders or ambiguities, and asking the user to review the spec before generating an implementation plan.

Can I start implementation before getting design approval for my requirements?▼

You cannot start implementation before design approval because the workflow enforces a hard implementation guardrail, only transitioning to writing-plans after the user explicitly approves the documented design spec.

How do I clarify project requirements and constraints before deciding what to build?▼

Clarifying project requirements involves exploring the current project state and asking one question at a time to converge on purpose, constraints, and success criteria before determining what to build.

Why should I use a question-driven design workflow for software architecture?▼

A question-driven design workflow prevents wasted implementation by forcing explicit design clarification, decomposition, and trade-off evaluation upfront, ensuring architecture decisions are approved before coding begins.