keel-interview
/keel-interview
Zadaje pytania o luki w specyfikacji, czyli przypadki brzegowe, rzeczy poza zakresem i ograniczenia, a odpowiedzi zapisuje jako propozycje kryteriów.
- Autor
- rickflashman ↗
- Repozytorium
- Keel ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zadaje pytania o luki w specyfikacji, czyli przypadki brzegowe, rzeczy poza zakresem i ograniczenia, a odpowiedzi zapisuje jako propozycje kryteriów.
Argumenty
/keel-interview [feature or area to focus on]
Oryginalny opis (EN)
KEEL 2.2.1 SPEC interview: asks the developer a few questions at a time about the gaps in docs/SPEC.md (edge cases, non-goals, trade-offs, constraints, glossary terms, acceptance criteria) and writes the answers as PROPOSED blocks for acceptance. Use in a KEEL project when the developer runs keel-interview (/keel:keel-interview or /keel-interview), asks to interview them about the spec, or wants to fill the gaps in SPEC.md.
Jak działa
- Steps
- The interview rule
Podgląd SKILL.md
--- name: keel-interview description: "KEEL 2.2.1 SPEC interview: asks the developer a few questions at a time about the gaps in docs/SPEC.md (edge cases, non-goals, trade-offs, constraints, glossary terms, acceptance criteria) and writes the answers as PROPOSED blocks for acceptance. Use in a KEEL project when the developer runs keel-interview (/keel:keel-interview or /keel-interview), asks to interview them about the spec, or wants to fill the gaps in SPEC.md." argument-hint: "[feature or area to focus on]" metadata: version: "2.2.1" source: "https://github.com/rickflashman/keel" --- # KEEL 2.2.1: SPEC interview Fill the gaps in `docs/SPEC.md` by interviewing the developer, under KEEL version 2.2.1 (November 12, 2026), https://github.com/rickflashman/keel. If the developer gave instructions with the command, such as a feature to focus on, follow them: $ARGUMENTS ## Steps 1. **Confirm the project uses KEEL** (`AGENTS.md` has an `Aligned to KEEL` stamp and `docs/SPEC.md` exists). If not, stop and tell the developer to run `keel` first. 2. **Read `docs/SPEC.md`** and the area map in `docs/ARCHITECTURE.md`. List the gaps by section: Goals, Users, Glossary, Features & user stories, Constraints, Acceptance criteria & test cases, Non-goals, Open questions. The SPEC template is in `templates/docs/SPEC.md`. 3. **Interview.** Ask a few questions at a time, and skip questions the docs already answer. Cover edge cases, non-goals, trade-offs, constraints, glossary terms, and acceptance criteria. The developer may stop at any time. 4. **Write the answers as PROPOSED blocks** in `docs/SPEC.md`, next to the text they change, never only in chat (the rule and the block format are below). Give each new acceptance criterion the next `AC-n` ID and its test cases, and note that `docs/RELEASE-CHECKLIST.md` needs a matching row once the block is accepted. 5. **Report** the PROPOSED blocks by file and AC ID or heading, and list them in `docs/HANDOFF.md` under Waiting at the next session close. Never edit accepted SPEC text. The standard is in `references/standard.md`. ## The interview rule **SPEC interview:** Interview the developer about the gaps in `SPEC.md`: edge cases, non-goals, trade-offs, constraints, glossary terms, and acceptance criteria. Ask a few questions at a time, and skip questions the docs already answer. Write the resulting SPEC changes as PROPOSED blocks for acceptance (rule 1). The developer may decline. **Proposed changes to SPEC and DESIGN:** The AI never edits accepted text in `SPEC.md` or `DESIGN.md` (rule 1). It writes each proposal in the file, next to the text it changes, as a PROPOSED block, never only in chat: ```md > PROPOSED 2026-10-31 (Claude Code): change AC-3 to allow an empty email. > Reason: the form now has a guest path. Code: src/forms/signup.js. ``` A PROPOSED block is not a requirement and not a design. The developer accepts it by applying the edit and deleting the marker, rejects it by deleting the block, or tells the AI to do either. The developer may decide on several blocks at once, for example "accept all PROPOSED blocks in SPEC.md". The developer may also accept the blocks of a ready card together with the card, but only by saying so; approval of the card alone does not accept its blocks. A block is named by its file and the AC ID or heading it changes (`SPEC.md AC-3`). The AI lists pending blocks in its task summary and, at the next close, in `HANDOFF.md` under Waiting. No block may remain at a release (rule 6). --- This skill is generated from `KEEL.md` in https://github.com/rickflashman/keel. Do not edit it by hand; change `KEEL.md` and run `python3 build/build.py`.
Pliki w paczce (7)
- SKILL.md 4 KB
- references/migration.md 13 KB
- references/standard.md 42 KB
- templates/README.md 2 KB
- templates/docs/HANDOFF.template.md 2 KB
- templates/docs/RELEASE-CHECKLIST.template.md 2 KB
- templates/docs/SPEC.template.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie keel-interview.
Migawka bazy z 13.11.2026 · wersja paczki ddfba0c62a7f (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
- 100keel
Ustawia, migruje i ulepsza dokumentację projektu tworzonego z AI: README, SPEC, architekturę, plan i listy kontrolne, dobierając ścieżkę. - 100keel-init
Tworzy podstawową dokumentację nowego projektu z szablonów KEEL, w tym README, SPEC, ARCHITECTURE i AGENTS.md, a potem przechodzi listę startową. - 96keel
Podłącza lub przywraca środowisko projektu Keel, utrzymuje wejścia agentów i skille, sprawdza postęp zadań oraz notatki. - 85team-work
Dostarcza playbooki specjalistów do zakresu funkcji, projektu architektury, przeglądu zmian i testów zmian w zespole Keel. - 100spec-elicitation
Prowadzi przechwytywanie zamiaru w nowym projekcie: cel, ograniczenia, architekturę, kryteria akceptacji, zadania i rzeczy poza zakresem. - 100interview
Uzgadnia zakres prośby przed planowaniem: bada kod, wskazuje niewiadome, cele poza zakresem i kryteria sukcesu, zadaje pytania zbiorczo tylko gdy badanie ich nie rozstrzyga, i zapisuje potwierdzony brief.md.