Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

brainstorming

/brainstorming

Prowadzi interaktywną eksplorację projektu przed implementacją, zadając po jednym pytaniu, zapisując specyfikację i blokując kod do jej zatwierdzenia.

Repozytorium
code-virtuoso ↗
Licencja
MIT
Ostatnia zmiana repozytorium
23.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
10
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 23.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 interaktywną eksplorację projektu przed implementacją, zadając po jednym pytaniu, zapisując specyfikację i blokując kod do jej zatwierdzenia.

Wyzwalacze z opisu

I want to buildlethelp me spec out

Argumenty

/brainstorming [optional: one-line topic]
Oryginalny opis (EN)

Interactive design exploration before implementation. Use when the user has a vague idea or feature request and no written spec. Asks one focused question at a time, writes a spec, and blocks implementation until approved. Triggers include 'I want to build', 'let's brainstorm', 'help me spec out'.

Jak działa

  1. When to use
  2. Quick start
  3. Workflow
  4. Critical rules
  5. Question technique
  6. Anti-patterns
  7. Reference files
  8. Integration with other skills
Sekcje z nagłówków SKILL.md, w oryginale · 110 linii, 828 słów
Podgląd SKILL.md
---
name: brainstorming
description: Interactive design exploration before implementation. Use when the user has a vague idea or feature request and no written spec. Asks one focused question at a time, writes a spec, and blocks implementation until approved. Triggers include 'I want to build', 'let's brainstorm', 'help me spec out'.
user-invocable: true
argument-hint: "[optional: one-line topic]"
---

# Brainstorming

Structured pre-implementation design exploration. It turns a vague idea into a written spec through focused, one-at-a-time questions, before any code is written, any plan is made, or any architecture is chosen. The spec is the deliverable, and everything else follows from it.

**No code until the spec is written and approved.**

## When to use

- The user says "I want to build X" but has no written requirements
- A feature request exists as a sentence or two with no detail
- The user asks "how should I build X" before defining what X actually is
- Someone says "let's brainstorm" or "help me figure this out"
- A problem statement exists but the solution space is unexplored

## Quick start

```
/brainstorming user authentication for a SaaS app
/brainstorming migrate our monolith to services
/brainstorming                                     # asks what to explore
```

If `$ARGUMENTS` is provided, use it as the initial topic and skip straight to Phase 1. If no argument, ask: "What idea, feature, or problem would you like to explore?"

---

## Workflow

This skill runs in guided phases. Each phase is a separate file, loaded one at a time. Every phase ends with a gate: wait for user confirmation before you proceed. Do not skip phases or merge them.

| Phase | File | What it covers |
|---|---|---|
| 1 | [Intake](phases/01-intake.md) | Read context, classify maturity, summarize understanding |
| 2 | [Divergence](phases/02-divergence.md) | Expand problem space with one-at-a-time questions across 7 categories |
| 3 | [Convergence](phases/03-convergence.md) | Narrow to concrete scope, lock must-haves and non-goals |
| 4 | [Spec writing](phases/04-spec-writing.md) | Write the full spec from the gathered material, run the quality checklist |
| 5 | [Approval](phases/05-approval.md) | Get explicit user approval, hard-gate implementation |

Start by loading Phase 1. After the user confirms each phase, load the next. Never load more than one phase at a time, and never skip one.

---

## Critical rules

1. **No code until the spec is approved.** That includes pseudocode, scaffolding, and "just a quick example."
2. **One question per message.** Compound questions produce shallow answers.
3. **Open questions before closed questions.** Explore before narrowing.
4. **Challenge assumptions, not people.** "Is X a hard requirement, or an assumption we should test?"
5. **The user defines scope, not the agent.** Surface possibilities through questions, let the user decide.
6. **Non-goals are as important as goals.** A spec without explicit non-goals has undefined boundaries.
7. **Acceptance criteria must be testable.** "It should be fast" is not testable. "Under 200ms at p95" is.
8. **Scale depth to complexity.** Simple features get short specs. System redesigns get thorough ones.
9. **Resolve contradictions before locking scope.**
10. **The spec is a living document until approved.**

---

## Question technique

| Principle | Meaning |
|---|---|
| **One at a time** | One question, one message |
| **Open before closed** | "What" and "why" first; "which" and "would you prefer" later |
| **Challenge assumptions** | When something is stated as obvious, ask what would happen if it were not true |
| **Surface constraints early** | Constraints eliminate solution space - the sooner known, the less rework |
| **Offer options when narrowing** | Present 2-3 concrete choices instead of open-ended questions during convergence |
| **Name the silence** | If an important topic has not come up, ask about it explicitly |

See [question-playbook](references/question-playbook.md) for the full catalog.

---

## Anti-patterns

| Anti-pattern | Fix |
|---|---|
| Solution jumping | Stay in divergence until goals and constraints are clear |
| Compound questions | One question per message |
| Leading questions | Ask neutral: "What scale needs exist?" not "Should we use microservices?" |
| Premature implementation | Hard-gate: no code until spec is approved |
| Fake consensus | Probe: "Can you walk me through how you'd use this?" |
| Scope creep during convergence | Park in "future considerations", re-lock scope |

See [anti-patterns](references/anti-patterns.md) for the full guide.

---

## Reference files

| Reference | Contents |
|---|---|
| [question-playbook](references/question-playbook.md) | Full catalog of question types with example phrasings |
| [spec-template](references/spec-template.md) | Output template the spec must follow |
| [anti-patterns](references/anti-patterns.md) | Failure modes that derail brainstorming |
| [when-to-exit](references/when-to-exit.md) | Criteria for "done" versus "needs more rounds" |

## Integration with other skills

| Situation | Recommended skill |
|---|---|
| Spec approved, next step: turn it into a plan and tasks and build it | `spec-driven-development` |
| Spec approved, deliver it end to end from a ticket to a PR | `ticket-delivery` |
| Complex requirements, need stakeholder analysis | `product-manager` role |
| Spec reveals architectural decisions needed | `architect` role |
| Spec approved and small enough to build directly | `tdd`, or the `implementer` agent |
| Acceptance criteria need test plan detail | `qa-engineer` role |
| API design decisions | `api-design` |
| Database schema decisions | `database-design` |
Pliki w paczce (10)
  • SKILL.md 6 KB
  • phases/01-intake.md 1 KB
  • phases/02-divergence.md 2 KB
  • phases/03-convergence.md 1 KB
  • phases/04-spec-writing.md 2 KB
  • phases/05-approval.md 2 KB
  • references/anti-patterns.md 11 KB
  • references/question-playbook.md 10 KB
  • references/spec-template.md 8 KB
  • references/when-to-exit.md 7 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · krzysztofsurdy/code-virtuoso100MIT
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 1cf269ba20e6 (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

  • 100rb-brainstorm
    Prowadzi interaktywną burzę mózgów dla projektów ralph-ban, zamieniając niejasny pomysł w dokument projektowy w .agent-history przed planowaniem kart.
  • 100ia-brainstorming
    Prowadzi wstępną eksplorację pomysłu: wywiad, porównanie podejść i dokument projektowy przed rozpoczęciem kodowania.
  • 100brainstorming-gate
    Wymusza eksplorację projektu i zatwierdzenie użytkownika przed implementacją funkcji, komponentu lub zmiany zachowania.
  • 81brainstorm
    Prowadzi lekki dialog sokratejski o pomyśle na funkcję z niejasnym zakresem lub UX i zapisuje specyfikację w markdownie, blokując kod do zatwierdzenia projektu.
  • 81brainstorm
    Prowadzi lekki dialog sokratejski o pomyśle na funkcję z niejasnym zakresem lub UX i zapisuje specyfikację w markdownie, blokując kod do zatwierdzenia projektu.
  • 100ql-brainstorm
    Prowadzi pogłębioną rozmowę o pomyśle na funkcję przed implementacją: zadaje pytania pojedynczo, proponuje 2 do 3 podejść z kompromisami i zapisuje zatwierdzony dokument projektu.

Uwagi i zgłoszenia

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