sp-brainstorming

Guide requirement discovery and iterative specification for feature designs.

23|2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/tta-lab/ttal-cli --skill sp-brainstorming-tta-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-brainstorming
Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/sp-brainstorming
Command: npx skills add https://github.com/tta-lab/ttal-cli --skill sp-brainstorming-tta-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps you move from an initial idea to a clear, validated design by uncovering user intent, requirements, constraints, and success criteria before any implementation starts.

Core Features & Use Cases

  • Intent-first questioning: asks one question at a time to refine understanding without overwhelming the user.
  • Approach exploration with trade-offs: proposes 2-3 options and recommends the best one based on reasoning.
  • Incremental design specification: presents the design in 200-300 word sections and validates after each section, covering architecture, components, data flow, error handling, and testing.
  • Design-to-planning chaining: hands off to planning once the design is validated, avoiding duplicated work.

Quick Start

Ask the skill to brainstorm a design for your feature or component by first exploring requirements and constraints in the context of your current project state.

Frequently Asked Questions about sp-brainstorming

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

FAQPage Schema
How do I turn vague feature ideas into validated design specifications?

To turn vague feature ideas into validated design specifications, you need structured requirement discovery. This skill guides intent-first questioning and proposes approaches with trade-offs to refine unclear concepts into actionable architecture plans.

What is the best way to explore architecture trade-offs during product workflow planning?

Exploring architecture trade-offs during product workflow planning involves evaluating multiple viable approaches. This skill proposes 2-3 design options with detailed trade-off analysis and recommends the best one based on your specific constraints.

How do I structure incremental validation for component design and requirements discovery?

Incremental validation for component design requires breaking specifications into 200-300 word sections. You validate architecture, data flow, and error handling iteratively after each section to ensure comprehensive requirements discovery before implementation.

Can I use this approach for behavior modification and feature planning across existing software projects?

Yes, you can use this approach for behavior modification and feature planning across existing software projects. It applies to creative product work including component design and workflow adjustments by uncovering intent and constraints before implementation starts.

When should I avoid one-question-at-a-time requirement discovery for design specifications?

You should avoid one-question-at-a-time requirement discovery when you already possess a clear, validated design specification. If your architecture planning is finalized and constraints are fully uncovered, this iterative validation process creates unnecessary overhead.