gtsi-brainstorm

Refines fuzzy ideas into approved design specs through incremental questioning.

Updated May 21, 2026
One-click install
npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-brainstorm-gestaosian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtsi-brainstorm
Source: https://github.com/gestaosian/gtsi-claude-skills/tree/main/plugins/gtsi-ops-plugin/skills/gtsi-brainstorm
Command: npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-brainstorm-gestaosian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague idea or feature request into a concrete, approved design is hard when requirements are unclear. This Skill structures the ideation process so nothing is planned or built before the design is validated. ## Core Features & Use Cases - Guided Clarification: Asks one clarifying question at a time, using multiple choice when possible, to define purpose, constraints, and success criteria. - Approach Comparison: Proposes 2-3 alternative approaches with tradeoffs and a justified recommendation before committing to a design. - Incremental Design Approval: Presents the design in sections (architecture, data flow, error handling, rollout) for per-section approval, then writes a spec to .gtsi/specs/<author>/ and hands off to gtsi-plan only after explicit approval. - Use Case: A user says "I want to improve our data pipeline monitoring but don't know where to start." The Skill explores the project context, asks targeted questions, compares monitoring approaches, and produces an approved spec ready for planning. ## Quick Start Ask the assistant to help you brainstorm and refine your idea into a design spec before any planning or coding begins.

Frequently Asked Questions about gtsi-brainstorm

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

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

Start a brainstorming session that asks one clarifying question at a time about purpose, constraints, and success criteria. The process proposes 2-3 approaches with tradeoffs, gets section-by-section design approval, and writes a spec file to .gtsi/specs/<author>/.

What is the best way to brainstorm before writing a project plan?▼

Use a structured ideation flow: explore project context, clarify scope with targeted questions, compare alternative approaches with tradeoffs, and validate the design incrementally. Only after explicit approval should the spec transition into a planning step.

Does this skill write code or create the implementation plan?▼

No. It operates under a hard gate: it writes no code, creates no files except the final spec, and never invokes the planning skill before explicit user approval of the design. Its only output is the approved spec document.

What happens if my idea scope is too large to design at once?▼

The skill detects overly broad scope covering multiple independent subsystems and proposes decomposition. Each subsystem gets its own spec, plan, and implementation cycle, and you choose which one to start with.

Where are the generated design specs saved?▼

Specs are saved to .gtsi/specs/<author-slug>/<YYYY-MM-DD>-<slug>.md, where the author slug is derived from git config user.name. The file follows a template covering context, architecture, data flow, error handling, rollout, risks, and success criteria.