sdlc-handoff
/sdlc-handoff
Przygotowuje zwięzłe przekazanie pracy z celem, stanem i następnym krokiem albo wznawia pracę z takiego przekazania.
- Autor
- phongtn89 ↗
- Repozytorium
- sdlc-kit ↗
- 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
Przygotowuje zwięzłe przekazanie pracy z celem, stanem i następnym krokiem albo wznawia pracę z takiego przekazania.
Wyzwalacze z opisu
Argumenty
/sdlc-handoff pause | pickup [path]
Oryginalny opis (EN)
Pause safely or pick up work: write a compact handoff (goal, state, evidence, blocker, next action, ruled-out paths) so a fresh session or another person can continue without re-deriving anything; or resume from one. Use when blocked, near the context or turn budget, switching phases or sessions, or when the user says 'hand off', 'pause', 'pick up' or 'continue from'.
Jak działa
- When to use
- Inputs
- Process
- Rationalizations
- Red flags
- Verification
- Principles applied
Podgląd SKILL.md
--- name: sdlc-handoff description: "Pause safely or pick up work: write a compact handoff (goal, state, evidence, blocker, next action, ruled-out paths) so a fresh session or another person can continue without re-deriving anything; or resume from one. Use when blocked, near the context or turn budget, switching phases or sessions, or when the user says 'hand off', 'pause', 'pick up' or 'continue from'." argument-hint: "pause | pickup [path]" user-invocable: true --- # sdlc-handoff: stop cleanly, start fast ## When to use - **Pause**: blocked; nearing `budget.max_turns` or the context limit; ending the session mid-task; between T3 phases when a fresh session would help. - **Pickup**: starting a session that continues earlier work (the `sdlc` router calls this when it finds a handoff). - Not a status report for stakeholders. That goes in the PR or issue. ## Inputs - `.sdlc/templates/handoff.md`. - The current state: `git status`, `git log -1`, the branch, and the `tasks.md` progress log. - For pickup: the handoff file (default: the newest `.sdlc/handoff-*.md`, or one inside the feature folder). ## Process **Pause** 1. **Preserve the work** (see `.sdlc/principles/fail-safe-keep-work.md`). Don't reset or discard anything. Commit only intended files, and only if committing is permitted; otherwise leave the working tree as it is and list the dirty files. 2. **Write the handoff** from the template to `specs/NNN-slug/handoff.md` for a feature, or to `.sdlc/handoff-<slug>.md` otherwise: - The goal, and the track. - The state: branch, SHA, dirty files. - What's done, with its evidence (commands and results). - What's in progress. The exact blocker: the sanitized error, the command, and who can unblock it. - The **next action**, phrased as the first concrete step. - The decisions made, and **what's been ruled out** (so nobody redoes it). - The files to read first, with line ranges. 3. **Keep it short**: the facts a newcomer needs, under ~60 lines. Link to artifacts; don't copy them. 4. **Leave the blocked tasks unchecked** in `tasks.md` and reference the handoff from them. 5. **Stop.** Make no more autonomous retries. Tell the user where the handoff is and what's needed from them. **Pickup** 1. Read the handoff. Check its state against reality: is the branch and SHA still the same, and are the dirty files still present? Report any differences before acting. 2. Re-verify any claimed evidence you'll rely on (the evidence-over-claims principle). Don't repeat the ruled-out paths. 3. Start the *Next action*. Update the handoff, or delete it when the work completes (deleting it is part of finishing). ## Rationalizations | Excuse | Reality | |---|---| | "I'll remember where I was" | The next session won't. Context doesn't survive; files do. | | "Dump the whole conversation into the handoff" | Nobody reads 500 lines. Facts, evidence and the next step. | | "Reset to a clean state before pausing" | That destroys the evidence and the work. Preserve, describe, stop. | | "Retry once more before handing off" | If the blocker is deterministic (auth, a missing access), retrying burns budget and changes nothing. | | "The handoff says the tests pass, so they pass" | That was true at its SHA. Re-check at the current one. | ## Red flags - The handoff would contain secrets, tokens or personal data. Redact them. - On pickup, the branch has moved or the dirty files are gone. Reconcile with the user before continuing. - The same blocker appears in two successive handoffs. Escalate to a human owner. ## Verification - The handoff file exists at the stated path, and every section is filled in or marked N/A. - `git status` shows the work preserved, and the dirty files listed match. - On pickup, the state check against the handoff is reported before the first edit. ## Principles applied fail-safe-keep-work, guard-context, evidence-over-claims
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · phongtn89/sdlc-kit | 90 | MIT |
| tscarpe/claude-sdlc-skills | 100 | MIT |
| blueskyxn/codex-is-all-you-need | 90 | GPL-3.0 |
Migawka bazy z 13.11.2026 · wersja paczki 16574903b857 (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
- 100handoff
Przygotowuje przekazanie między sesjami: zapisuje plik continue.md w katalogu bieżącego wycinka pracy i dba o aktualność STATE.md oraz podsumowań. - 95handoff
Przygotowuje lub wznawia zwięzłe przekazanie pracy, aby nowa sesja albo inny model kontynuowały zadanie. - 90handoff
Pisze dokument przekazania, by inny agent lub nowa sesja mogła kontynuować pracę bez ponownego tłumaczenia. - 100handoff
Zapisuje plik przekazania, gdy użytkownik kończy pracę lub prosi o zapis postępu, i wznawia pracę z takiego pliku w nowym oknie. - 90safe-resume
Wznawia wstrzymaną pracę od miejsca, w którym ją zostawiono, gdy istnieje plik RESUME.md lub stan z safe-pause. - 90handoff-writer
Pisze przekazanie, dzięki któremu kolejna osoba lub sesja może kontynuować pracę bez odtwarzania ustaleń.