jidoka-implement-balanced
/jidoka-implement-balanced
Wdraża specyfikację i zgłoszenia z testami zachowania, bez cykli czerwony-zielony, w etapie budowy zrównoważonego przebiegu jidoka.
- Autor
- TDSchreur ↗
- Repozytorium
- jidoka ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- 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.
Co robi i kiedy
Wdraża specyfikację i zgłoszenia z testami zachowania, bez cykli czerwony-zielony, w etapie budowy zrównoważonego przebiegu jidoka.
Oryginalny opis (EN)
Implement a spec and its tickets with project-directed behavior tests, without red-green cycles. Use for the Build stage of jidoka-balanced or when tested implementation without strict TDD is requested.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 21 linii, 484 słów
Podgląd SKILL.md
--- name: jidoka-implement-balanced description: Implement a spec and its tickets with project-directed behavior tests, without red-green cycles. Use for the Build stage of jidoka-balanced or when tested implementation without strict TDD is requested. --- # Implement Spec Balanced Implement the provided spec on a single feature branch. A clear user request with acceptance criteria can serve as the spec; tickets are optional. Use existing tickets when provided, without requiring new planning artifacts or tracker setup. 1. Read the request or spec, its acceptance criteria, and any tickets, identify dependencies, and inspect the relevant code and project instructions. Reuse context already gathered by the calling workflow. 2. Create or use the task's feature branch. Work sequentially in the current checkout, taking tickets whose dependencies are satisfied or implementing the agreed plan directly when there are no tickets. 3. Implement each ticket first, without invoking `jidoka-tdd` or running a red-green-refactor cycle. 4. Then add or update behavior tests for the ticket’s acceptance criteria when appropriate under the project’s instructions. Apply the test-quality rules from `jidoka-tdd` (its "What a good test is" and "Anti-patterns" sections, plus [tests.md](../jidoka-tdd/tests.md) and [mocking.md](../jidoka-tdd/mocking.md) when needed): - test through public interfaces, preferring existing seams; - take expected values from an independent source such as the spec or a worked example, never by recomputing them the way the code does; - do not mock internal collaborators, test private functions, or verify through a side channel. Choose the seams yourself; do not ask for seam approval. Follow the project’s instructions on test scope and explain any omission. 5. Run targeted or quick checks during iteration and fix failures, following the project's required cadence. Reuse passing results only while the checked code and its relevant inputs are unchanged; rerun affected checks after changes and honor stricter checks the project requires. Run the project's full verification at the point the calling workflow sets, or after the last ticket when used on its own; a missing tool or a failing check is a blocker, never something to skip. 6. When the change has a runnable entrypoint (application, server, CLI), start it once from the working directory a user would use, with its default configuration and no test overrides, and exercise the main path; report what you ran, or why no entrypoint applies. 7. Self-review the change before the final report: read its whole diff against the base, including uncommitted work, and check it against the project's documented coding standards and [standards-checklist.md](../jidoka-code-review/references/standards-checklist.md). Fix clear issues, such as an unclear name, an error or case skipped silently without a comment saying it is deliberate, or a parameter wider than the function uses, then rerun the affected checks. Report what the self-review found and fixed. 8. Verify the result against the acceptance criteria and end by listing each criterion with the test or evidence that shows it. Report the completed work, tests added, checks performed, and any remaining blockers. Leave commits, pushing, and PR creation to the calling workflow unless the user explicitly requests them. Do not require subagents, extra worktrees, a draft PR, or a separate code review as part of this skill.
Wersje
W bazie nie ma innych skilli o nazwie jidoka-implement-balanced.
Migawka bazy z 13.11.2026 · wersja paczki ffc248b44613 (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
- 96jidoka-implement-fast
Wdraża specyfikację i zgłoszenia bez TDD, w etapie budowy szybkiego przebiegu jidoka. - 86jidoka-implement
Wdraża w kodzie wynik specyfikacji i zadań, w etapie budowy jidoka-full, z testami najpierw, gdy instrukcje projektu na to pozwalają. - 100go-tdd
Wdraża zatwierdzoną specyfikację Go metodą test-first: pętla czerwony, zielony, refaktor z bramkami na każdym etapie. - 90test-first-implementation
Wdraża zachowania w pętli czerwony, zielony, refaktoryzacja, w małych pionowych krokach, także przy poprawkach regresji. - 842-implement
Implementuje funkcję metodą TDD, w cyklu czerwony, zielony, refaktoryzacja, aż do zakończenia zadania. - 100tdd
Buduje jedną funkcję lub jedną poprawkę w pętli czerwony, zielony, refaktor, z testami w uzgodnionych punktach styku.