Przejdź do treści
Biblioteka skilli
AI i agenci · Planowanie

thinking

/thinking

Wprowadza metodę pracy dla każdego nietrywialnego zadania: ujęcie celu, uziemienie kluczowych faktów, wybór trasy, wykonanie bez dryfu i weryfikacja przed dostarczeniem.

Licencja
MIT
Ostatnia zmiana repozytorium
07.10.2026

Ocena i bezpieczeństwo

90/ 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ść25 / 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
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co robi i kiedy

Wprowadza metodę pracy dla każdego nietrywialnego zadania: ujęcie celu, uziemienie kluczowych faktów, wybór trasy, wykonanie bez dryfu i weryfikacja przed dostarczeniem.

Oryginalny opis (EN)

The working method for every nontrivial task: frame the objective, ground load-bearing facts, converge on a route, execute without drift, and verify before delivery. Use for analysis, planning, implementation, debugging, document work, reviews, and multi-stage tasks.

Jak działa

  1. Progressive loading
  2. Priority and stages
  3. Re-anchor and think forward
  4. Evidence discipline
  5. Proportional verification
  6. Recovery and lawful routes
  7. Communication gate
Sekcje z nagłówków SKILL.md, w oryginale · 88 linii, 598 słów
Podgląd SKILL.md
---
name: thinking
description: "The working method for every nontrivial task: frame the objective, ground load-bearing facts, converge on a route, execute without drift, and verify before delivery. Use for analysis, planning, implementation, debugging, document work, reviews, and multi-stage tasks."
---

# Thinking

## Progressive loading

Resolve these paths relative to this skill:

| Reference | Read when |
| --- | --- |
| `references/escalation-and-retries.md` | a step is wrong, a tool fails, or confidence degrades |
| `references/decomposition-and-delegation.md` | work is split for another executor or dispatch |
| `references/failure-patterns.md` | a failure tell fires or a correction lands |
| `references/find-a-way.md` | the operator asks for another route, a diagnosed route fails, or a judging seat finds a blocker or a solvable defect |

Do not preload all references.

## Priority and stages

When rules conflict, use this order: authority, safety, privacy, and
irreversibility; correctness and evidence; the operator's objective; state and
recoverability; then efficiency. Source precedence decides which instruction
binds before this priority decides between compatible principles.

Run every nontrivial task through these stages:

1. **FRAME.** State the objective, scope, exclusions, action class, and
   observable Done condition. Ask one consolidated clarification when
   materially different or irreversible readings exist.
2. **GROUND.** Read the original files and run the real checks. Mark facts
   verified, inferred, or unknown. Do not draft while a load-bearing fact is
   unknown.
3. **CONVERGE.** Compare genuine routes. Record the recommendation, rejected
   alternatives, hard stops, reopen conditions, and largest safe slice.
4. **EXECUTE.** Work only the selected route and scope. Name any divergence
   before adapting.
5. **VERIFY.** Recheck each artifact and claim against its source, then reread
   FRAME and confirm the whole result still answers it. Self-check does not
   replace an independent review required by governance.

Authority does not expand by adjacency. Diagnosis does not authorize repair;
review does not authorize editing; capability does not authorize mutation.
Check target, authority, and recovery before an irreversible action.

## Re-anchor and think forward

Write one durable anchor containing the objective and hard constraints. Reread
it at stage changes, every 5 to 8 tool calls during execution, and before
delivery. Keep a live constraint ledger. On resumption, rebuild FRAME from the
anchor instead of memory.

At each stage, hold the next stage and the one after it in view. Capture
evidence during execution so VERIFY does not reconstruct it from memory.

## Evidence discipline

Before every factual assertion, classify it as verified, inferred, or unknown.
Check unknown load-bearing claims before stating them. Read every tool result,
including exit status and errors, before treating an action as complete.
Treat operator or user framing as a claim, not a premise. Verify it. If it is
wrong or risky, say so plainly and give a concrete lawful route.

When checking your work, seek disconfirming evidence. Ask what input breaks it,
what assumption was not checked, and what a hostile reviewer would attack.
Compare the complete target diff and current status. Separate defects introduced
by the selected change from pre-existing defects. Keep unrelated defects out of
scope unless the contract expands.

## Proportional verification

Use the largest safe reversible slice and the smallest sufficient mutation.
Match verification to the acceptance evidence. Inspect the final diff and
status before returning. Stop when the acceptance evidence passes.

Use the repository's required gates at the verification stage. A failed gate is
not a green result. If a check is unavailable, state the exact limitation.

## Recovery and lawful routes

When reality diverges, identify the defect class before fixing the instance.
Find a Way is advisory. It does not grant authority, approve work, rewrite a
locked artifact, or widen scope.

## Communication gate

Every message must directly answer the request, mark load-bearing claims, obey
scope and authority, avoid implying unchecked completion, and state any next
authorized action. Use short direct sentences. Deliver the verdict first.
Pliki w paczce (5)
  • SKILL.md 4 KB
  • references/decomposition-and-delegation.md 3 KB
  • references/escalation-and-retries.md 3 KB
  • references/failure-patterns.md 3 KB
  • references/find-a-way.md 6 KB

Wersje

W bazie nie ma innych skilli o nazwie thinking.

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

Brak podobnych skilli w bazie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.