本文へ移動
cccskills
無料GitHub で公開

brainstorming

Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria — instead of listing ten obvious ideas and calling it creativity. Use when asked to brainstorm, generate ideas or options, explore a solution space, or name something. Produces a genuinely wide option set (including the weird tail), then a shortlist selected against named criteria with the rejects preserved.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Brainstorming Skill

Asked to brainstorm, a model produces ten reasonable ideas that any competent person would list — which is retrieval, not ideation. Real brainstorming has two phases with a wall between them: diverge (volume, no judgment, deliberately weird) then converge (explicit criteria, honest scoring). This skill enforces the wall.

What This Skill Produces

  • A divergent set: 20-40 ideas spanning distinct strategies, not ten variants of one idea
  • A convergent shortlist: 3-5 selected against criteria named before scoring
  • The reject ledger: what was set aside and why — half the value, always preserved

Required Inputs

Ask for (if not already provided):

  • The problem or prompt, and what an idea must accomplish to count
  • Constraints that are real (budget/tech/brand) vs assumed — challenge one assumed constraint deliberately
  • What's been tried or rejected already (avoids retreading; also reveals the requester's hidden criteria)

Divergent Phase (no judgment permitted)

  1. Quota past the obvious. The first 8-10 ideas are what anyone would say — produce them fast to exhaust them, then keep going; ideas 15-30 are where non-obvious lives.
  2. Rotate strategies, don't rephrase. Generate down distinct axes, a few ideas per axis:
    • Inversion — what would make the problem worse? Reverse each answer
    • Extremes — the $0 version; the $10M version; the version shipping tomorrow
    • Transplant — how does a hospital / game studio / street market solve the equivalent?
    • Constraint removal — if [assumed constraint] vanished, what becomes possible?
    • Actor shift — the user solves it themselves / the community solves it / it never occurs at all (prevention)
    • Combination — force-merge two earlier ideas
  3. Keep the weird tail. 20% of the set should make the requester slightly uncomfortable. A brainstorm with no bad ideas didn't explore the edges — the weird ones exist to stretch the space, and occasionally to win.
  4. No evaluative language in this phase. Not even "(probably impractical)". Judgment leaks kill volume.

Convergent Phase (judgment, but named)

  1. Write criteria before looking back at the list. 3-4 max, from the requester's actual situation (impact, feasibility-this-quarter, differentiation, reversibility…). Criteria chosen after re-reading the list get reverse-engineered to bless a favourite.
  2. Score coarsely (✅/➖/❌ per criterion). False precision on creative options is theatre.
  3. Shortlist 3-5 with one line each on why. Include one wildcard — highest-variance, criteria-marginal — labelled as such.
  4. Preserve the rejects with reasons. "Rejected: needs a partnership we don't have (yet)" is a future idea with a trigger condition; a deleted reject is a repeated brainstorm next quarter.

Output Format

Brainstorm: [prompt]

Divergent set ([n] ideas, by strategy): [grouped list — no judgments attached]

Criteria (named before selection): 1) … 2) … 3) …

Shortlisted[C1][C2][C3]Why it made it
(3-5 rows, incl. 🃏 one wildcard)

Reject ledger: [idea → the criterion it failed → what would revive it]

Quality Checks

  • ≥20 ideas spanning ≥5 distinct strategies — not variants of two ideas
  • The weird tail exists (ideas that risk sounding silly)
  • Zero evaluative language in the divergent set
  • Criteria were stated before scoring, and trace to the requester's situation
  • Rejects preserved with revival conditions

Anti-Patterns

  • Do not judge while generating — one "(unrealistic)" mid-list collapses the whole divergent phase
  • Do not produce ten polished-obvious ideas and stop — that's a search result, not a brainstorm
  • Do not let the criteria appear after the list has been read — that's rationalising a favourite
  • Do not delete the rejects — the ledger is half the artifact
  • Do not ship the shortlist without the wildcard — a fully-safe shortlist means the exercise removed everything it was for

Example Trigger Phrases

  • "Generate ideas."
  • "Explore a solution space."
  • "Name something."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する