「brainstorm」の検索結果

Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order. Prevents premature implementation, skipped validation, and unreviewed high-risk designs.

日本語の概要は準備中です。原文の説明を表示しています。

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill before any creative or constructive work (features, components, architecture, behavior changes, or functionality). This skill transforms vague ideas into validated designs through disciplined, incremental reasoning and collaboration.

日本語の概要は準備中です。原文の説明を表示しています。

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

日本語の概要は準備中です。原文の説明を表示しています。

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

日本語の概要は準備中です。原文の説明を表示しています。

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.

日本語の概要は準備中です。原文の説明を表示しています。

Explore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration.

日本語の概要は準備中です。原文の説明を表示しています。

Design-first ideation workflow — explore user intent, clarify constraints, propose approaches, and produce an approved design document before planning

日本語の概要は準備中です。原文の説明を表示しています。

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written

日本語の概要は準備中です。原文の説明を表示しています。

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

日本語の概要は準備中です。原文の説明を表示しています。

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

日本語の概要は準備中です。原文の説明を表示しています。

Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation

日本語の概要は準備中です。原文の説明を表示しています。

Generate creative, memorable, and available domain name ideas for projects, products, and businesses with consideration for branding, SEO, and availability. Use when naming new projects, finding available domains, creating memorable brand names, generating naming ideas, checking domain availability, or establishing online presence.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

日本語の概要は準備中です。原文の説明を表示しています。

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).

日本語の概要は準備中です。原文の説明を表示しています。

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)

日本語の概要は準備中です。原文の説明を表示しています。

Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.

日本語の概要は準備中です。原文の説明を表示しています。

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

日本語の概要は準備中です。原文の説明を表示しています。

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".

日本語の概要は準備中です。原文の説明を表示しています。

Use before creative or constructive work (features, architecture, behavior). Transforms vague ideas into validated designs through disciplined reasoning and collaboration.

日本語の概要は準備中です。原文の説明を表示しています。

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

日本語の概要は準備中です。原文の説明を表示しています。