Przejdź do treści
Biblioteka skilli
Programowanie · Planowanie

brainstorming

/brainstorming

Prowadzi burzę mózgów nad zmianą w kodzie, wzbogaconą wcześniej o sygnały ryzyka, własności i długu technicznego z tea-rags, żeby eksploracja opierała się na faktycznym stanie obszaru.

Repozytorium
tearags-mcp ↗
Licencja
MIT
Ostatnia zmiana repozytorium
18.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 18.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Prowadzi burzę mózgów nad zmianą w kodzie, wzbogaconą wcześniej o sygnały ryzyka, własności i długu technicznego z tea-rags, żeby eksploracja opierała się na faktycznym stanie obszaru.

Wyzwalacze z opisu

brainstorm Xdesign featurerefactor Yletдавай обсудимкак перестроитьчто может сломаться
Oryginalny opis (EN)

Brainstorm code change seeing risk, ownership, tech-debt signals from tea-rags first — creative exploration grounded in actual state of affected area. Triggers on "brainstorm X", "design feature", "refactor Y", "let's discuss", "давай обсудим", "как перестроить", "что может сломаться". NOT for trivial edits or stylistic questions with no code area to enrich. Wraps superpowers:brainstorming with tea-rags risk-signal enrichment step.

Jak działa

  1. Iron Rule
  2. Step 1 — Extract target area
  3. Step 2 — Three tea-rags enrichment calls (five with codegraph)
  4. Step 3 — Build enrichment block
  5. Step 4 — Invoke superpowers:brainstorming
  6. Red Flags — STOP and restart from Step 2
  7. Common Mistakes
Sekcje z nagłówków SKILL.md, w oryginale · 179 linii, 1 196 słów
Podgląd SKILL.md
---
name: brainstorming
description:
  Brainstorm code change seeing risk, ownership, tech-debt signals from tea-rags
  first — creative exploration grounded in actual state of affected area.
  Triggers on "brainstorm X", "design feature", "refactor Y", "let's discuss",
  "давай обсудим", "как перестроить", "что может сломаться". NOT for trivial
  edits or stylistic questions with no code area to enrich. Wraps
  superpowers:brainstorming with tea-rags risk-signal enrichment step.
---

# dinopowers: brainstorming

Wrapper over `superpowers:brainstorming`. Ensures creative exploration starts
from real git signals (hotspots, owners, legacy debt) of target area — not from
assumptions about how code looks today.

## Iron Rule

**tea-rags enrichment MUST be called BEFORE `Skill(superpowers:brainstorming)`**
— whenever target area identifiable. Correct preset selection (`hotspots`,
`ownership`, `techDebt`) + correct parameters + correct ordering = core value of
this wrapper.

If no code area identifiable from user request (pure conceptual brainstorming):
skip enrichment, invoke `superpowers:brainstorming` directly. State explicitly —
do not fabricate an area.

**Chaining rule:** see [CHAINING.md](../../CHAINING.md) — every dinopowers:X
redirects superpowers:X. NEVER bypass wrapper.

**Index freshness:** see [FRESHNESS.md](../../FRESHNESS.md) and
`tea-rags/rules/index-freshness.md`. No background reindex hook. Linked
worktree: overlay serves uncommitted edits — never reindex for them. Main
checkout: incremental `mcp__tea-rags__index_codebase` BEFORE first tea-rags call
over code edited but not committed.

## Step 1 — Extract target area

From user request identify:

| Element                                        | Example                                                 |
| ---------------------------------------------- | ------------------------------------------------------- |
| **Area** — path or domain                      | `src/core/domains/ingest/**`, `auth/`, "rerank presets" |
| **Change type** — what the brainstorm is about | "new feature", "refactor", "bug-fix approach"           |
| **Scope hint** — narrower filter if mentioned  | file name, class name, symbol                           |

Compose:

- `pathPattern` for Step 2 (e.g. `**/auth/**`,
  `src/core/domains/ingest/**/chunker/**`)
- `query` — single sentence describing change intent

If no area mentioned or derivable: skip to Step 4 with empty enrichment. Report
"no area identifiable — proceeding without tea-rags enrichment".

## Step 2 — Three tea-rags enrichment calls (five with codegraph)

Run these three `mcp__tea-rags__semantic_search` calls **in parallel** (same
tool call block), each with `metaOnly: true` (want signals, not content):

| Call          | `rerank` preset      | Why                                                                                                                                 |
| ------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| A — Hotspots  | `"hotspots"`         | Bug-prone zones the brainstorm must account for (high churn + recency + bugFix)                                                     |
| B — Ownership | `"ownership"`        | Knowledge silos — single-owner files that need reviewer pairing                                                                     |
| C — Tech debt | `"techDebt"`         | Legacy zones where "just refactor it" hides cost (age + churn + bugFix)                                                             |
| D — Backbone  | `"architecturalHub"` | **Codegraph only** — structural hubs (high `fanIn` / `isHub`) the design must respect; a change to a backbone has wide blast radius |

Call D runs ONLY when codegraph active (prime `## Enrichment` lists
`codegraph.symbols`). When that line absent, omit Call D — run A/B/C only, note
structural backbone not assessed (do NOT substitute a similarity-ranked list as
"the hubs"). See search-cascade "Graph navigation".

**Call E — vocabulary (codegraph only, same parallel block):**
`get_naming_lexicon(concept=<Step 1 query>, language, pathPattern)` →
`concept.terms` = the words the project already uses for this area. Reading:
`tea-rags:data-driven-generation` Step 5 "Naming (lexicon)".

Exact parameters per call:

```
path:        <your working directory>   ← tea-rags search-cascade "Addressing the Codebase"; never project alone
query:       <intent sentence from Step 1>
pathPattern: <pathPattern from Step 1>
rerank:      "hotspots" | "ownership" | "techDebt" | "architecturalHub"
limit:       10
metaOnly:    true
```

(`"architecturalHub"` = Call D, codegraph-gated per the note above.)

Do NOT substitute:

| Wrong tool                     | Why wrong                                                                                            |
| ------------------------------ | ---------------------------------------------------------------------------------------------------- |
| `mcp__tea-rags__hybrid_search` | Same rerank, but its BM25 leg re-ranks by query-token overlap — signal scan wants semantic + signals |
| `mcp__tea-rags__find_similar`  | Requires an existing symbolId; brainstorm targets an area, not a known symbol                        |
| `mcp__tea-rags__find_symbol`   | Returns one symbol; brainstorming needs area-wide risk distribution                                  |
| Running the calls sequentially | Wastes time; they are independent — issue them in one parallel block                                 |

Do NOT pass:

- `metaOnly: false` — content not needed; larger payloads slow wrapper
- Custom `rerank` weights instead of three named presets — loses calibrated
  risk-assessment semantics
- `filter` on `git.ageDays` / `git.commitCount` — presets already encode these
  signals; adding filters shrinks result set, hides debt

If all three risk calls return 0 results (area new, untouched by git): report
"no git-enriched results for pathPattern `<X>` — area is new or excluded from
indexing" and skip to Step 4 without enrichment block. Do NOT fabricate signals.

## Step 3 — Build enrichment block

From three result sets, compose compact block (max ~15 lines):

```
### tea-rags enrichment for <pathPattern>

**Hotspots (bug-prone):**
- <relativePath>:<startLine>-<endLine> — bugFixRate <N>, commitCount <N>, ageDays <N>
- ... (top 3)

**Knowledge silos (single live-line owner):**
- <relativePath> — <blameDominantAuthor> (<blameDominantAuthorPct>%), <commitCount> commits
- ... (top 3)

**Tech debt (legacy + churn):**
- <relativePath> — ageDays <N>, commitCount <N>, relativeChurn <X>
- ... (top 3)

**Project vocabulary (Call E):** <term> (<holder>), ... (top 5)
```

Cap each section at 3 entries. If a file appears in multiple sections, note
explicitly (`→ also in Hotspots`) — overlap is strong brainstorming signal. Do
NOT paste raw JSON. Extract readable `relativePath` + 2-3 key signals per entry.
Values: `rankingOverlay.{file,chunk}.<field>` (every preset-surfaced signal,
labelled); metaOnly payload `git.*` holds essentials only (commitCount, ageDays,
taskIds, blame\*), raw. File-level presets (ownership, architecturalHub) → no
startLine on the hit.

## Step 4 — Invoke superpowers:brainstorming

Invoke `Skill` tool with `superpowers:brainstorming`. Prepend enrichment block
from Step 3 as context. Phrase handoff as:

> "Before exploring, note these risk signals in the target area: …<block>… Use
> them to pressure-test ideas — especially around the hotspot files. A name the
> design proposes for a new symbol goes through
> `get_naming_lexicon(names, language)` before the design fixes it: `MISFIT` →
> take `suggestion`; `NEW_TERM` → a vocabulary term if it means the same,
> otherwise justify the new word.
>
> Chaining rule reminder: if your cycle would next invoke a `superpowers:Y`
> skill (writing-plans, test-driven-development, etc.), invoke the
> `dinopowers:Y` wrapper instead when one exists — see the Chaining rule section
> above."

Let `superpowers:brainstorming` run full exploration cycle — this wrapper does
not replace it, only grounds it.

## Red Flags — STOP and restart from Step 2

- "I already know which files are hotspots here" → run Step 2 anyway; memory
  stale
- "tea-rags is slow for 3 calls, let me do one" → three presets = different
  lenses; one call loses two
- Substituted `hybrid_search` / `find_similar` / `find_symbol` → redo with
  `semantic_search` + preset
- Ran the calls sequentially → reissue as parallel (same tool block)
- Invoked `superpowers:brainstorming` first, tea-rags after as "validation" →
  wrong order, restart
- Set `metaOnly: false` to "see content" → unnecessary; restart with
  `metaOnly: true`
- Let `superpowers:brainstorming` chain into a raw `superpowers:Y` (e.g.
  `superpowers:writing-plans`) without redirecting to `dinopowers:Y` → intercept
  and invoke wrapper instead (see Chaining rule)

## Common Mistakes

| Mistake                                                     | Reality                                                                        |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Skip tea-rags because "brainstorming is abstract"           | If the user named a code area, it's not abstract. Enrich it.                   |
| Use `rerank: "relevance"` instead of the three risk presets | Loses the point — brainstorming should see risk, not just relevance            |
| Collapse three calls into one with custom weights           | Custom weights ≠ calibrated presets; output is noisy and hard to interpret     |
| Paste raw `results[]` JSON into Step 4 handoff              | `superpowers:brainstorming` drowns in noise; extract 3 entries per lens        |
| Fabricate an area when user didn't name one                 | Explicit "no area — skipping enrichment" is honest; faked pathPattern is a lie |

Wersje

RepozytoriumWynikLicencja
Ta strona · artk0de/tearags-mcp100MIT
jjuraszek/pi-gauntlet100MIT
GanyuanRan/Aegis100MIT
Montinou/triqual100MIT
guanyang/antigravity-skills100MIT
osmontero/opencode-skills100MIT
Sanit-mann/The-Insectoids100MIT
coco-research/coco100MIT
ILIV007/prime-skill100MIT

Migawka bazy z 13.11.2026 · wersja paczki ede0eaef4495 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100dino-brainstorming
    Prowadzi burzę mózgów o zmianie w kodzie, opierając się na sygnałach ryzyka, właścicielstwa i długu technicznego z narzędzia tea-rags.
  • 100writing-plans
    Pisze plan wdrożenia, w którym sekcja plików wzbogacona jest o import, zmiany, właścicieli i zadania, na podstawie sygnałów tea-rags.
  • 90pr-tools:address-review
    Pobiera komentarz z przeglądu PR i prowadzi przez burzę mózgów nad planem poprawek, zanim zmiany trafią do kodu.
  • 100design
    Tworzy artefakty projektowe przez wspólną burzę mózgów nad podejściami, architekturą i kompromisami, w tym dokument projektowy.
  • 90ck:brainstorm
    Prowadzi burzę mózgów rozwiązań z analizą kompromisów i bezwzględną szczerością: ideacja, decyzje architektoniczne, spory techniczne, eksploracja funkcji i ocena wykonalności.
  • 90tech-debt
    Prowadzi rejestr długu technicznego: zapisuje koszt i ryzyko, wyszukuje sygnały długu i ustala priorytety na kolejne sprinty.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.