aico-pm-brainstorming_skill

This skill guides you through one-question-at-a-time brainstorming to transform vague ideas into clear, actionable product concepts.
  • TypeScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yellinzero/aico --skill aico-pm-brainstorming

  • SKILL.md3.3 KB

Overview

This skill guides users through a structured, one-question-at-a-time brainstorming dialogue to turn vague ideas into clear, actionable product concepts. It favors multiple-choice prompts and always explores 2–3 alternative approaches before converging. The output is staged in short, confirmable sections so concepts can be validated and documented for next steps.

How this skill works

The skill first checks available project context and then asks a single clarifying question, preferably with multiple-choice options. After each answer it explores 2–3 distinct approaches with concise trade-offs, presents a 200–300 word concept section for validation, and saves validated outcomes for follow-up planning. It enforces the Iron Law: focus only on what to build, never on implementation details.

When to use it

  • When a user says “I have an idea”, “I want to build”, or “let me think about”
  • When a user explicitly asks to brainstorm, explore ideas, or think through options
  • If requirements are vague, incomplete, or the user seems unsure what they want
  • Before running /pm.plan when requirements lack context or clarity
  • When a user asks “what should I build?” or “how should this work?”

Best practices

  • Ask only one question per turn; never bundle multiple clarifying questions
  • Prefer multiple-choice prompts to reduce friction and speed decisions
  • Always present 2–3 alternative approaches with clear trade-offs
  • Keep each presented concept short (200–300 words) and request explicit confirmation before proceeding
  • Avoid any discussion of implementation, code, or architecture during brainstorming

Example use cases

  • Turn a fuzzy product idea into a validated problem statement and prioritized approaches
  • Help a PM decide between feature directions by comparing 2–3 alternatives and trade-offs
  • Guide a founder to a clear user segment and success metric before drafting requirements
  • Reframe an ambiguous request into a simple, testable hypothesis for user research
  • Produce a short validated concept to hand off to planning or design teams

FAQ

No. During brainstorming it deliberately avoids implementation and feasibility; those topics are deferred to planning phases.

How many alternatives will it explore?

It will propose 2–3 distinct approaches for each problem area, summarizing trade-offs so the user can choose or request refinements.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational