overload
/overload
Uruchamia, wznawia lub konfiguruje zadanie deweloperskie Workflow Overload, tylko gdy użytkownik wpisze /overload.
- Autor
- enriconardo ↗
- Repozytorium
- workflow-overload ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.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 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
Uruchamia, wznawia lub konfiguruje zadanie deweloperskie Workflow Overload, tylko gdy użytkownik wpisze /overload.
Argumenty
/overload [request | setup]
Oryginalny opis (EN)
Starts, resumes or configures a Workflow Overload development task. Runs only when the user types /overload.
Jak działa
- Where to start
- Rules of every task
Podgląd SKILL.md
---
name: overload
description: Starts, resumes or configures a Workflow Overload development task. Runs only when the user types /overload.
disable-model-invocation: true
argument-hint: "[request | setup]"
allowed-tools: Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/status.sh), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/journal.sh:*), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/verify.sh:*), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/branch.sh:*), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/commit.sh:*), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/suite.sh:*), Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/red-check.sh:*)
---
# Workflow Overload
The user typed `/overload $ARGUMENTS`. You are the **main agent** of a task: you hold the intent, talk with the human, write the code on the S path and the spec on the L path, and direct the agents and the scripts. Noisy work (exploring, probing, implementing an L chunk, reviewing) goes to agents, which return only their result.
State of this project, read by a script as this skill loaded:
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/status.sh`
- Scripts: `${CLAUDE_PLUGIN_ROOT}/scripts/`. Run them from the project's root exactly as `bash ${CLAUDE_PLUGIN_ROOT}/scripts/<name> <arguments>`, unquoted and alone in the command: that form is allowed without a prompt for `branch.sh`, `journal.sh`, `verify.sh`, `commit.sh`, `suite.sh` and `red-check.sh`. `<scripts>` in the phases' files means this folder. `integrate.sh` asks the human's permission each time, on top of their go at the checkpoint.
- Phases: `${CLAUDE_SKILL_DIR}/phases/`. Read a phase's file in full when you enter it, and follow it.
## Where to start
1. Arguments starting with `setup`: read `phases/setup.md`; any text after `setup` is the human's guidance for it. Arguments that read as a request rather than as guidance for the config (`setup logging for the API`): ask the human which they meant.
2. No config: say so in one line and offer `/overload setup`. A config the status refuses: show what it says, which names each change and where to make it, and offer to make them; on the human's go, change the config and commit it on its own. Stop there.
3. A journal on this branch:
- no arguments: read `phases/resume.md`;
- arguments: ask the human whether they change the open task (then resume, and take them as new input to the phase the journal gives) or open a new one (then the open task must be integrated or stopped first).
4. No journal: with arguments, read `phases/brainstorm.md`; without, ask for the request.
## Rules of every task
- **Scripts do the mechanical steps**: `branch.sh` opens the task, `verify.sh` checks the tree, `commit.sh` commits the verified tree, `suite.sh` records the test-author's suite, `red-check.sh` checks it fails for the right reason, `integrate.sh` merges. Never `git commit` or `git merge` yourself: a hook refuses them while a journal exists. The scripts print only what you need: never pipe their output.
- **Every commit is green and holds one logical change.** Code, review fixes, lessons and backlog items are separate rounds of verify and commit.
- **Who writes does not judge.** Reviewers report and never fix. You fix on the S path. Give an agent exactly what its definition says it receives, and never a summary of your discussion with the human, which carries your drift toward their ideas.
- **Three rounds at most.** Any automatic loop (a red verify, a review that keeps finding blocking issues) stops at its third round and goes to the human, as `phases/escalate.md` says.
- **The journal is the task's memory** across sessions. Change the phase with `journal.sh set phase <phase>`, note in its sections the lesson candidates, backlog candidates and open findings as they come up, and log what the human decides with `journal.sh log`.
- **The backlog holds only what the human approves.** Agents and you propose candidates; the human picks at the checkpoint.
- **The project's rules** are the files of the config's `rules` (its CLAUDE.md files, ADRs): read those that bear on the change before you write code. Commands run as they say (a container, a wrapper).
- **Names and messages are the project's.** The branch's name and every commit's message follow its rules. Where they state no convention: a branch `<type>/<description>` in kebab-case (`fix/empty-cart-total`), a subject in the imperative of at most 72 characters. The project's hooks have the last word: when one refuses a name or a message, change it; never bypass the hook.
- **Talk to the human in their language.** Commits, the journal and the project's files follow the project's own conventions.
- **The human decides** the tier, the result, the lessons and backlog items to keep, and every escalation. A step that cannot be undone outside the branch waits for them.
Pliki w paczce (9)
- SKILL.md 5 KB
- phases/brainstorm.md 3 KB
- phases/close.md 5 KB
- phases/escalate.md 1 KB
- phases/l-chunk.md 5 KB
- phases/l-plan.md 5 KB
- phases/resume.md 1 KB
- phases/s-path.md 2 KB
- phases/setup.md 3 KB
Wersje
W bazie nie ma innych skilli o nazwie overload.
Migawka bazy z 13.11.2026 · wersja paczki 574e07b3bed8 (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
- 100handling-overload
Zapobiega przeciążeniom przez zrzucanie obciążenia, throttling, zarządzanie kolejkami i łagodną degradację usług wg Google SRE. - 100cognitive-overload-simplification-support
Wykrywa przeciążenie poznawcze u uczących się lub współpracowników i dzieli złożone architektury na przystępne pojęcia. - 100operational-overload
Wykrywa przeciążenie zespołu operacyjnego, np. przerwania i wezwania dyżurowe, i pomaga odzyskać równowagę według Google SRE. - 85zlua-method-overload
Rozstrzyga przeciążenia metod C# z Lua: domyślny dobór, klucze pełnej sygnatury i moment użycia LuaAlias. - 100python-typing-ops
Stosuje wzorce adnotacji typów w Python: TypeVar, Generic, Protocol, overload i TypedDict oraz sprawdzanie przez mypy i pyright. - 100using-superpowers
Wybiera skille workflow Superpowers, gdy użytkownik prosi o ten przepływ albo konkretne zadanie deweloperskie skorzysta z jego procesu.