intake
/intake
Zamienia nowe zlecenie w pozycję pracy: nazywa jej typ, streszcza zamiar i zapisuje SPEC.md z dowodami akceptacji.
- Autor
- vanducng ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 22
- Skrypty
- 14
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 14 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: evals/01-bug-report/checks.sh, evals/01-bug-report/fixture/src/cart.js, evals/01-bug-report/fixture/tools/records.cjs, evals/02-question/checks.sh, evals/02-question/fixture/tools/records.cjs, evals/03-already-shaped/checks.sh, evals/03-already-shaped/fixture/src/cart.js, evals/03-already-shaped/fixture/tools/records.cjs, evals/04-stateful-retry/checks.sh, evals/04-stateful-retry/fixture/src/webho
Co robi i kiedy
Zamienia nowe zlecenie w pozycję pracy: nazywa jej typ, streszcza zamiar i zapisuje SPEC.md z dowodami akceptacji.
Wyzwalacze z opisu
Argumenty
/intake <the ask, a ticket, or a bug report>
Oryginalny opis (EN)
Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape).
Jak działa
- Steps
- Rules
Podgląd SKILL.md
--- name: intake description: "Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape)." license: MIT argument-hint: "<the ask, a ticket, or a bug report>" metadata: author: vanducng version: "0.2.1" --- # intake The first gate. It decides what kind of work this is and what will prove it done, before anyone designs or builds. It does not plan, design or code. `C=<this skill's directory>/scripts/contract.cjs` ## Steps 1. **Find the record.** - In an OpenRig rig, the record is the slice folder from `rig scope slice create`, created by the lead. - Elsewhere, the bench record the workbench skill resolves (`records.cjs resolve --id <id>`), where `<id>` is a short kebab name for the task. 2. **Already taken in?** Read the intents of the records beside it first. If one already covers this ask, use it, whatever its id. If its `SPEC.md` has an authored intent and a proof contract, change nothing: say it is shaped and stop. 3. **Classify:** pick one work type from `node "$C" --list`. - If two types fit, choose by what would prove the work done. - If the ask is too thin to tell, ask one question with your best guess, and write nothing. 4. **Write `SPEC.md`:** - frontmatter: `id`, `type` (the work type), and `intent` (the ask restated in one or two plain sentences); - `lenses: [statechart]` in the frontmatter only when the work has three or more states, or a rule about events over time (their order, a duplicate or late event, a retry). A pure calculation or a one-shot request gets no lens; - `## Mini-requirements`: numbered, observable outcomes taken from the ask, nothing invented; - `## Proof contract`: the lines from `node "$C" <type>`, made concrete for this ask (name the test, surface or number); - one more contract line: door type (one-way or two-way), blast radius, and the undo step. No `TODO` lines are left behind. 5. **Rig kind** (only in an OpenRig workspace): feature, bug fix or SOP maps to a rig template through the workspace skill's `rig-kind.cjs`. Name it. 6. **Hand off:** a queue row to the seat that owns the build: `--tags project:<org>.<project>`, `--mission <mission> --slice <slice>` when a slice exists; not the owner seat, hand the row's text to the lead. After every create, `rig queue show <id>`. 7. **Report:** the work type, the record path, the lens if you named one, and the open question if there is one. The next gate is `vd:shape`, which draws the lens's charts. ## Rules - The proof comes from the work type. A bug fix is proved by a check that fails on the old code and passes on the new. An investigation is proved by cited claims, each labelled measured, inferred or guess. - Restate the intent in your own words; never paste the ask. - One record per ask. Never create a second record for work that already has one.
Pliki w paczce (22)
- SKILL.md 3 KB
- evals/common-checks.sh 1 KB
- evals/01-bug-report/checks.sh 1 KB
- evals/01-bug-report/prompt.md 1 KB
- evals/01-bug-report/fixture/src/cart.js 1 KB
- evals/01-bug-report/fixture/tools/records.cjs 1 KB
- evals/02-question/checks.sh 1 KB
- evals/02-question/prompt.md 1 KB
- evals/02-question/fixture/export.sql 1 KB
- evals/02-question/fixture/tools/records.cjs 1 KB
- evals/03-already-shaped/checks.sh 1 KB
- evals/03-already-shaped/prompt.md 1 KB
- evals/03-already-shaped/scenario.json 1 KB
- evals/03-already-shaped/fixture/.workbench/cart-coupon/SPEC.md 1 KB
- evals/03-already-shaped/fixture/src/cart.js 1 KB
- evals/03-already-shaped/fixture/tools/records.cjs 1 KB
- evals/04-stateful-retry/checks.sh 1 KB
- evals/04-stateful-retry/prompt.md 1 KB
- evals/04-stateful-retry/fixture/src/webhook.js 1 KB
- evals/04-stateful-retry/fixture/tools/records.cjs 1 KB
- scripts/contract.cjs 3 KB
- scripts/contract.test.cjs 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · vanducng/skills | 90 | MIT |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| alecs5am/ralphy | 100 | Apache-2.0 |
| lamngockhuong/aiteamkit | 100 | MIT |
| mathews-tom/armory | 100 | MIT |
| alecs5am/ralphy | 100 | Apache-2.0 |
| buriedsignals/splash | 100 | MIT |
| yuxqiu/loci | 90 | MIT |
| woditschka/agentic-coding-reference | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki cfd69ee0bd14 (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
- 90shape
Kształtuje zapis zadania przed budową: zamiar prostymi słowami, numerowane wymagania i listę dowodów w pliku SPEC.md, a także tryb przesłuchania. - 85intent
Pomaga przemyśleć, co budować i po co, zapisując zamiar i kontekst w luźnej formie, bez sztywnych wymagań. - 96new-work-item
Tworzy i zakresuje nowe zadanie w folderze work/items repozytorium, gdy pojawia się prośba bez wpisu. - 100echo-intent
Zakłada lub doprecyzowuje plik intent.md dla elementu pracy na podstawie zgłoszenia i krótkiego celu. - 100breakdown
Zamienia zamiar, dokument projektu lub zgłoszenie w zadania typu błąd, zadanie lub historia z podzadaniami, z odniesieniem do plików. - 95new-track
Prowadzi wstępny wywiad przed nową funkcją lub poprawką, zadając pytania i uściślając zakres przed specyfikacją.