skills.rest
gkganesh12
gkganesh12COMMUNITY
Explore all skills by this author →
Website𝕏@gkganesh01GitHub

gk-brainstorm

Transforms project concepts into validated, buildable BRIEF.md specifications via structured discovery workflows.

1|Updated Jul 4, 2026
Search Tags:#brainstorming#requirements#discovery#project-planning#scope-management#product-brief
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-brainstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gk-brainstorm
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-brainstorm
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of project ambiguity by forcing a structured, validated discovery process before any code is written, preventing mid-build scope creep and architectural surprises.

Core Features & Use Cases

  • Validated Brief Generation: Transforms raw ideas into a standardized BRIEF.md file that downstream skills can parse.
  • Agentic Detection: Automatically identifies if a project requires AI agent architecture, flagging it for specialized handling.
  • Complexity Sizing: Provides S/M/L/XL sizing and identifies the primary complexity driver to set realistic expectations.
  • Use Case: A founder has a vague idea for a client dashboard; this skill guides them through defining the problem, success metrics, and non-goals, resulting in a clear, actionable plan that prevents wasted development time.

Quick Start

Use the gk-brainstorm skill to help me plan my new project idea.

Frequently Asked Questions about gk-brainstorm

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

FAQPage Schema
How do I turn fuzzy project ideas into validated, buildable briefs?▼

To turn fuzzy ideas into validated buildable briefs, use a structured brainstorming and discovery workflow that defines core value, success metrics, non-goals, and technical constraints before implementation begins.

What is the best way to prevent scope creep during project planning?▼

The best way to prevent scope creep during project planning is enforcing a validated discovery process that defines non-goals and technical constraints, ensuring architectural readiness before any code is written.

How do I estimate project complexity and size during requirements discovery?▼

Estimate project complexity and size during requirements discovery by using a structured workflow that provides S/M/L/XL sizing and identifies the primary complexity driver to set realistic expectations.

Does structured brainstorming detect if a project requires AI agent architecture?▼

Yes, structured brainstorming includes agentic detection that automatically identifies if a project requires AI agent architecture, flagging it for specialized handling during the discovery workflow.

Can I use a product brief workflow for both personal and client-based projects?▼

Yes, you can use a product brief workflow for both personal and client-based projects, as it operates across distinct paths to define core value, success metrics, and technical constraints for each context.

Related Skills

Explore More Product & Management Skills→
CarbeneAICarbeneAI
9

brainstorming

Breaks down complex problems into actionable steps through guided questioning and iterative solution development, ensuring clarity and feasibility in the final outcome.

Community
Advanced
shirulotshirulot

spec-driven-development

Enforce a gated specification workflow before software implementation.

Community
Advanced
zhaozengqing4364-bitzhaozengqing4364-bit

deep-interview

Clarify ambiguous project ideas into detailed specifications through Socratic questioning.

Community
Intermediate
TrogonStackTrogonStack
10

prd-current-state

Document existing user workflows, manual workarounds, and operational costs.

Official
Intermediate