strata.build-task
/strata.build-task
Wykonuje pojedyncze zadanie z zamówienia: pisze kod w jednej warstwie, uruchamia testy i raportuje wynik z dowodami.
- Autor
- team-tatters ↗
- Repozytorium
- strata-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 9
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.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
Wykonuje pojedyncze zadanie z zamówienia: pisze kod w jednej warstwie, uruchamia testy i raportuje wynik z dowodami.
Oryginalny opis (EN)
Use when executing one task file from an order: implementing code within one layer, running its tests, and reporting with evidence; when the user says implement, build, do the task, write the code. Keywords - implement, build task, worker, single layer.
Jak działa
- Overview
- When to use
- Process
- Rationalizations
- Red flags
- Verification
Podgląd SKILL.md
--- name: strata.build-task description: Use when executing one task file from an order: implementing code within one layer, running its tests, and reporting with evidence; when the user says implement, build, do the task, write the code. Keywords - implement, build task, worker, single layer. --- # strata.build-task ```yaml skill: id: strata.build-task version: '0.2' owner: worker triggers: - a task file is assigned - the user asks to implement a planned change inputs: - task-NN.yaml - layer rules and naming convention of the profile - the files named in the task outputs: - code and tests within the task's layer - completion report with constraint compliance and evidence - a rejection with reasons when the task is incomplete required_context: - rec.architecture.no-layer-violation - rec.naming.follow-convention - rec.verify.evidence-not-impression allowed_tools: - read - edit - test - bash(build and test commands) validation: - the task's verification command passed and its output is in the report - no file outside the task's layer was changed - each constraint in the task is marked complied or not, with a reason failure_modes: - 'the task lacks files, constraints or a verification command: reject it, do not guess' - 'a change outside the layer is needed: stop and report the boundary' ``` ## Overview Executes one task: reads the specification the task carries, changes only the named files within one layer, runs the verification command, and reports completion with evidence and per-constraint compliance. ## When to use A task file from strata.order is assigned, or the user asks to implement a planned change. Not without a task: an incomplete task is rejected with the missing items listed. ## Process 1. Read the task and check it is complete (layer, files, constraints, verification). Evidence: the checklist. Reject if incomplete — but read the named files and the documents they point to first, and list the missing decisions as concrete choices with options and a recommendation; reading is not guessing, implementing is. Then claim the order (`python3 -m kb order claim <order-id>`); if another machine or session holds it, stop and ask the person. Evidence: the claim output. 2. Read the named files and one existing example of the same pattern. Evidence: paths. 3. Write the failing test first when the task adds behaviour, then the minimal code, then refactor. Evidence: test output before and after. 4. Run the task's verification command and the layer checker. Evidence: outputs and exit codes. 5. Report: files changed, constraint compliance table, evidence, anything not verified. ## Rationalizations | Thought | Rebuttal | |---|---| | "The task is almost complete, I can infer the rest." | Inference is how layers get crossed. Reject and ask for the missing items. | | "Tests after the code are fine." | The failing test is the evidence that the test tests something. | | "The checker warning is a false positive." | Report it as a warning with your reasoning; do not silence it. | ## Red flags - Edits to files not named in the task. - A report with no command output. - A constraint marked complied with no reason. ## Verification - Verification command output is in the report. - Only files within the layer changed. - Constraint compliance table is complete.
Pliki w paczce (9)
- SKILL.md 3 KB
- evals/scenarios.yaml 2 KB
- evals/results/2026-10-29.yaml 1 KB
- evals/results/2026-11-01-r4.yaml 2 KB
- i18n/es.md 2 KB
- i18n/fr.md 2 KB
- i18n/ja.md 3 KB
- i18n/ko.md 2 KB
- i18n/zh.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie strata.build-task.
Migawka bazy z 13.11.2026 · wersja paczki dc13ad30b9b0 (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
- 100implement
Realizuje pojedyncze zadanie z planu w dyscyplinie TDD: czyta specyfikację, pisze testy, minimalny kod przechodzący, refaktoryzuje i robi commit. - 100arn-code-execute-task
Wykonuje pojedyncze zadanie z listy zadań, z opcjonalnym przeglądem, także przy ponownym uruchomieniu lub ponowieniu próby. - 95strata.order
Zamienia zatwierdzoną specyfikację w zamówienie i zadania dla wykonawców, gdy zmiana dotyka kilku warstw lub osób. - 81task_implement
Wdraża jedno istniejące zadanie od początku do końca: pisze kod i testy, uruchamia weryfikację i oznacza wykonanie. - 90executing
Wykonuje spisany plan zadanie po zadaniu, z kontrolami i końcowym przeglądem, gdy plan istnieje i użytkownik prosi o jego wdrożenie. - 90task-implementation
Wdraża kolejne niezakończone zadanie z PLAN.md w podejściu TDD: najpierw testy, potem kod, gotowy do przeglądu i commita.