brainstorming

Guide teams from vague ideas to concrete design plans through structured dialogue.

Updated Nov 24, 2024
One-click install
npx skills add https://github.com/devtitus/3D-Portfolio --skill brainstorming-devtitus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/devtitus/3D-Portfolio/tree/main/.kilocode/skills/brainstorming
Command: npx skills add https://github.com/devtitus/3D-Portfolio --skill brainstorming-devtitus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn raw ideas into fully formed design concepts through structured, collaborative dialogue. It reduces ambiguity and speeds up planning by enforcing a one-question-at-a-time approach and delivering incremental design sections.

Core Features & Use Cases

  • Guided ideation: Convert vague concepts into clear design goals by asking one focused question at a time.
  • Multi-solution exploration: Propose 2-3 design approaches with trade-offs and a recommended option with rationale.
  • Incremental design delivery: Present the design in concise 200-300 word sections covering architecture, components, data flow, and testing criteria.
  • Documentation readiness: Write the validated design to docs/plans with a timestamp and explicit next steps for implementation.
  • Implementation guidance: If continuing, prompt for readiness to set up an implementation plan and isolated workspace.

Quick Start

Describe the project goal and constraints, then request a design in 200-300 word sections delivered incrementally with one-question-at-a-time prompts.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague project ideas into clear design plans?

Brainstorming design approaches involves exploring 2-3 proposed solutions with trade-offs and a recommended option. This multi-solution exploration helps evaluate architecture, components, and data flow before committing.

What is the best way to gather requirements during a design sprint?

Gathering requirements during a design sprint is best handled through one-question-at-a-time dialogue. This enforces focused requirement gathering and feature scoping to create clear, actionable designs incrementally.

How do I document a design plan for implementation readiness?

To document a design plan for implementation readiness, write the validated design to docs/plans with a timestamp and explicit next steps. This ensures the incremental design sections are actionable for development.

Can I receive design sections incrementally instead of all at once?

Yes, you can receive design sections incrementally. The design is delivered in concise 200-300 word sections covering architecture, components, data flow, and testing criteria to speed up planning and reduce reading friction.

Does collaborative ideation work for feature scoping without prior architecture?

Yes, collaborative ideation works for feature scoping without prior architecture. It is applied during early ideation and requirement gathering to transform raw ideas into fully formed design concepts through structured dialogue.