Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Przegląd i audyt

template-intake

/template-intake

Przetwarza sugestie zgłoszone w bazach wiedzy zbudowanych z szablonu, każdą przyjmuje lub odrzuca z użytkownikiem.

Repozytorium
brain-template ↗
Licencja
MIT
Ostatnia zmiana repozytorium
03.11.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
2
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Przetwarza sugestie zgłoszone w bazach wiedzy zbudowanych z szablonu, każdą przyjmuje lub odrzuca z użytkownikiem.

Oryginalny opis (EN)

Take in upstream suggestions recorded by brains made from this template: collect open entries with _meta/brain upstream list, accept or decline each with the person, make accepted changes through brain-write-skill or brain-write-script with tests, and answer every one in _meta/CHANGELOG.md by id. Use when asked in a template session to check brains for suggestions or to process upstream feedback. Does NOT write into any brain, and does NOT commit, which is brain-sync.

Jak działa

  1. Where this sits
  2. 1. Collect
  3. 2. Decide each one with the person
  4. 3. Make each accepted change
  5. 4. Answer every one in the changelog
  6. 5. Hand to brain-sync
  7. Never
  8. Done when
Sekcje z nagłówków SKILL.md, w oryginale · 102 linii, 860 słów
Podgląd SKILL.md
---
name: template-intake
description: "Take in upstream suggestions recorded by brains made from this template: collect open entries with _meta/brain upstream list, accept or decline each with the person, make accepted changes through brain-write-skill or brain-write-script with tests, and answer every one in _meta/CHANGELOG.md by id. Use when asked in a template session to check brains for suggestions or to process upstream feedback. Does NOT write into any brain, and does NOT commit, which is brain-sync."
---

# Take in suggestions from brains

A brain cannot change the files the template owns, so it writes what one of them needs as a
suggestion in its own `docs/UPSTREAM.md`. This skill reads those, decides each one with the person, makes the
accepted changes here, and answers every one in `_meta/CHANGELOG.md`; each brain takes the answer in
with its next `update`. Reading is the only thing this skill does to a brain.

## Where this sits

<!-- where:begin — generated by _meta/brain routing sync; do not edit -->
**Runs after:** nothing — an entry point into the tree.

**Hand to next:** `brain-sync` · `brain-write-script` · `brain-write-skill`
<!-- where:end -->

**Call it directly when:** in a template session, the person asks to check the brains for
suggestions, or brings one from a brain `local/brains.txt` does not list; nothing runs first.

## 1. Collect

Run this in the template's own checkout: `brain.json` `role` is `template` and `local/` exists.

`_meta/brain upstream list` reads every brain listed in `local/brains.txt`. For a brain not listed
there (a clone of one kept on another machine, say), pass its path:
`_meta/brain upstream list "<brain>"`. Each line is `<brain>  <id>  <status>`, plus the template's
answer when `CHANGELOG.md` already has one. Work the open ids that have no answer. An id the
changelog answers is done, even while the brain still reads `open`: it flips when that brain
updates. A listed brain that is no longer there: tell the person; `local/brains.txt` is theirs to
tidy.

For each id, read its entry in that brain's `docs/UPSTREAM.md`: `- template:` (the version it was
written against), `- files:`, `### What happened`, `### Proposed change`. Read only: never edit,
stage or commit anything in a brain, not even the status line, which the brain flips itself in the
commit that brings the answer in.

## 2. Decide each one with the person

One at a time: say what the brain hit, what it proposes, and what the template does now (the files
may have changed since the version the entry names, and it may already be fixed). Recommend accept
or decline, with the reason, and let the person decide. Accept a change that helps any brain;
decline one that fits only that brain's work, undoes a rule the template keeps on purpose, or is
already fixed (say by what). A partial accept is an accept whose summary says what landed. Two
brains with the same problem get one change and an answer each.

## 3. Make each accepted change

- A `brain-*` skill, `_meta/ROUTING-META.md` or `_meta/gates.json`: through `brain-write-skill`.
- The harness (`_meta/brain`, `_meta/brainlib/`, `_meta/managed/`, `_meta/skeleton/`): through
  `brain-write-script`, as its "In the template" section says.

Hand the proposal on as the starting point, not as the change: it was written from one brain's work.
Write the change for any brain, with no hostname, project, person or path taken from the suggesting
brain: everything here ships, and the template is public. Run the suite before answering:

```bash
PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests -t .
```

## 4. Answer every one in the changelog

Bump `_meta/VERSION` once for this intake: the patch number when every accepted change fixes
something (`0.1.0` → `0.1.1`), the minor number when any adds behaviour (`0.1.0` → `0.2.0`). Add a
heading for the new version above the previous one in `_meta/CHANGELOG.md`, and under it one line
per id worked, in exactly this shape, because `upstream list` and each brain's `update` parse it:

```markdown
## <version> — <YYYY-MM-DD>

- landed: <id> — <what changed, in one line>
- declined: <id> — <the reason, in one line>
```

The separators are em dashes (—) and the date is today's. Every id worked gets exactly one line;
one the person wants to leave for later stays open, with none. An intake that only declines still opens a patch heading, so each brain's next `update` reports the
answer as new. Write the summaries and reasons for any brain too: they reach every brain.

## 5. Hand to brain-sync

`brain-sync` commits in the template, running the test suite first: each change under its own scope
(`skill(<name>)`, `meta(<area>)`, `test(<area>)`), with `_meta/VERSION` and `_meta/CHANGELOG.md`.
Committing is enough, with no release step: brains update from the template's committed history.
Do not commit here.

## Never

- Write, stage or commit in a brain, or run anything there that writes: the brain's own sessions
  change the brain, and the template only reads it.
- Answer an id without the person's decision, or work one and leave it without a changelog line.
- Carry a brain's private detail (a host, a project, a person, a local path) into the template.

## Done when

- Every open, unanswered id `upstream list` showed has exactly one `- landed:` or `- declined:`
  line in `_meta/CHANGELOG.md`, under a new heading whose version matches `_meta/VERSION`, or the
  person chose to leave it open for later.
- Each answer was the person's decision.
- Each accepted change was made through `brain-write-skill` or `brain-write-script`, and the test
  suite passes.
- No file in any brain was written, and no brain's private detail is in the template.
- The work is handed to `brain-sync`; nothing was committed here.

Wersje

W bazie nie ma innych skilli o nazwie template-intake.

Migawka bazy z 13.11.2026 · wersja paczki 4642f19b9913 (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

  • 100brain-upstream
    Zapisuje propozycję zmiany pliku zarządzanego przez szablon jako sugestię w docs/UPSTREAM.md, bez prywatnych szczegółów, i przywraca lokalne zmiany.
  • 100brain-sync
    Aktualizuje repozytorium brain w tym samym porządku: pokazuje stan, uruchamia kontrole, zapisuje zmiany w historii i wysyła je po zgodzie.
  • 100brains-setup
    Zakłada strukturę drugiego mózgu dla agentów AI: osobne repozytorium na firmę, klienta lub obszar życia oraz nadrzędny mega-mózg.
  • 100second-brain-prd
    Generuje wieloetapowy, spersonalizowany PRD budowy osobistego drugiego mózgu w TypeScript z wypełnionego szablonu.
  • 100brain-sync
    Aktualizuje bazę wiedzy po rozmowie: przenosi nowe wnioski z Inboxu do notatek w repozytorium brain.
  • 100brain
    Prowadzi bazę wiedzy projektu w SQLite project_brain.db z encjami, relacjami, zadaniami, wątkami, decyzjami i zdarzeniami oraz odpowiada na pytania o stan 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.