workflow-complete
/workflow-complete
Domyka zakończony workflow: aktualizuje dossier, zapisuje końcowy log i przekazanie, przenosi katalog i archiwizuje wpis.
- Autor
- AMDResearch ↗
- Repozytorium
- omniprobe ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.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 27.10.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
Domyka zakończony workflow: aktualizuje dossier, zapisuje końcowy log i przekazanie, przenosi katalog i archiwizuje wpis.
Oryginalny opis (EN)
Perform the full completion sequence for a finished workflow. Use when all acceptance criteria are met and the workflow is ready to move to done state. Updates dossier, writes final run-log and handoff entries, moves the packet directory, and archives the entry in active-workflows.md.
Jak działa
- Purpose
- Preconditions
- Required Reads
- Procedure
- Output
- Completion Criteria
- Error Handling
Podgląd SKILL.md
--- name: workflow-complete description: | Perform the full completion sequence for a finished workflow. Use when all acceptance criteria are met and the workflow is ready to move to done state. Updates dossier, writes final run-log and handoff entries, moves the packet directory, and archives the entry in active-workflows.md. --- # workflow-complete ## Purpose This skill ensures all completion steps are performed together when a workflow reaches `done` state. It prevents the common failure where a workflow is marked done in `active-workflows.md` but the packet directory is not moved, the run-log has no closing entry, or the handoff is stale. ## Preconditions - A workflow packet exists in `.agents/workflows/active/<workflow-id>/` (or `blocked/`, `suspended/`). - The packet's `acceptance.sh` exits 0. This is a precondition, not a formality: a packet does not become done because an agent believes it is done. ## Required Reads 1. `.agents/workflows/<current-state>/<workflow-id>/dossier.md` [required] -- verify acceptance criteria status. 2. `.agents/workflows/<current-state>/<workflow-id>/handoff.md` [required] -- current state. 3. `.agents/workflows/<current-state>/<workflow-id>/run-log.md` -- execution history. 4. `.agents/state/active-workflows.md` [required] -- coordination index. 5. `.agents/state/current-focus.md` [required] -- project focus. ## Procedure 1. **Run `acceptance.sh`.** Before reading anything else about criteria status, run the packet's acceptance script and capture its full output: ``` bash .agents/workflows/<current-state>/<workflow-id>/acceptance.sh ``` **If it exits non-zero, stop.** Report: "Cannot complete workflow — acceptance.sh exited <N>. Unmet criteria: [the FAIL lines]." Do not proceed with any other completion step. Do not edit `acceptance.sh` to make it pass, and do not weaken a criterion in the dossier -- record a proposed spec change in `handoff.md` instead and take it to the user. If the packet has no `acceptance.sh` -- it predates the convention -- say so explicitly in the closing run-log entry, and fall back to reading the dossier and confirming each criterion against verification evidence. An absent gate is not a passed gate; it just means the evidence is manual. 2. **Acknowledge every `JUDGE` line.** A judgement criterion is non-gating by design, so `acceptance.sh` can exit 0 with judgement criteria unresolved. Each one must be explicitly human-acknowledged in `artifacts.md` before the packet moves: quote the `JUDGE` line, state who reviewed it, and state the finding. A packet with unacknowledged `JUDGE` lines is not complete. Record `WEAK` lines in `artifacts.md` too. They do not require sign-off, but the completion record should show which criteria were established by an indirect check rather than a direct one. 3. **Verify remaining acceptance criteria.** Read `dossier.md` and confirm every criterion not covered by the script is met with verification evidence. If any criterion is unmet and the failure policy is not `best_effort`, stop: "Cannot complete workflow — unmet criteria: [list]. Resolve or change failure policy first." 4. **Update dossier metadata.** Set the `Lifecycle State` field in `dossier.md` to `done`. Verify the update was written: re-read the `Lifecycle State` line from `dossier.md` and confirm it now says `done`. If it does not, stop and report the error. 5. **Write final run-log entry.** Append a closing entry to `run-log.md`: ```markdown ### <timestamp> - **Actor**: <agent identifier> - **Planned step**: Workflow completion - **Action taken**: All acceptance criteria verified. Workflow marked done. - **Result**: success - **Files touched**: dossier.md, handoff.md, active-workflows.md, current-focus.md - **Verification**: <summary of criteria verification> - **Criteria impact**: All criteria met - **Blocker / Risk**: none ``` 6. **Write final handoff.** Update `handoff.md` with final status: - Current Status: **Done. All acceptance criteria met.** - Last Verified: <timestamp and summary> - Next Exact Step: N/A — workflow complete. - Active Risks / Blockers: none. 7. **Move the packet directory.** Relocate the entire workflow directory from `.agents/workflows/<current-state>/<workflow-id>/` to `.agents/workflows/done/<workflow-id>/`. 8. **Archive completed entry in active-workflows.md.** Move the workflow's row from the main table to a `## Completed` section at the bottom of the file. If the `## Completed` section does not exist, create it with a minimal table header (`| ID | Type | Completed |`). The archived row needs only the workflow ID, type, and completion date — strip the owner, write scope, dependencies, and blocker columns. If the Completed section exceeds 30 rows, remove the oldest rows (they remain discoverable via the `done/` directory). 9. **Prune current-focus.md.** Remove this workflow from "Current Focus Areas" and "Active Workflows" sections entirely. If this workflow appears in "Recent Decisions" only as a completion notice (not a substantive decision), remove that entry too. Add a one-line entry to "Recent Decisions" only if a durable project decision was made during this workflow (technology choice, architecture decision, scope decision). Keep the total "Recent Decisions" section under 15 entries by removing the oldest non-architectural entries when the limit is reached. 10. **Verify state consistency.** After completing all updates, perform a quick check: - Confirm the workflow directory is now at `.agents/workflows/done/<workflow-id>/`. - Confirm `active-workflows.md` shows the workflow in the Completed section. - Confirm `dossier.md` lifecycle state reads `done`. - If any check fails, report which step was incomplete and fix it before finishing. ## Output No separate output file. The skill modifies existing state files in place and moves the packet directory. ## Completion Criteria - `acceptance.sh` was run and exited 0, and its output is recorded in `artifacts.md`. - Every `JUDGE` line in that output is acknowledged in `artifacts.md` with a reviewer and a finding. - `dossier.md` lifecycle state is `done`. - Run-log has a closing entry. - `handoff.md` reflects final state. - Packet directory is in `.agents/workflows/done/<workflow-id>/`. - `active-workflows.md` shows the workflow as `done`. - `current-focus.md` is updated. ## Error Handling - If the workflow directory does not exist at the expected path, search other lifecycle directories and report the actual location. - If `acceptance.sh` exits non-zero, stop and report — do not mark as done, and do not touch the script or the criteria to change that. - If `acceptance.sh` crashes rather than reporting failures, treat it as a broken gate, not a passed one. Fix the script, then re-run. - If acceptance criteria are unmet, stop and report — do not mark as done. - If `.agents/workflows/done/` does not exist, create it. - If a workflow with the same ID already exists in `done/`, append a timestamp suffix to avoid collision.
Wersje
W bazie nie ma innych skilli o nazwie workflow-complete.
Migawka bazy z 13.11.2026 · wersja paczki a81f5a87a293 (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
- 100workflow-create
Tworzy kompletny pakiet workflow z jasnego zlecenia lub briefu: dossier, log, przekazanie, artefakty i kryteria akceptacji. - 95gdd-complete-cycle
Zamyka cykl projektowy: oznacza wpis jako ukończony, archiwizuje artefakty, generuje EXPERIENCE.md i resetuje stan. - 100run
Prowadzi pierwsze produkcyjne uruchomienie gotowego workflow: pisze Run Card, zakłada dziennik przebiegów i wyznacza pierwszy termin przeglądu. - 90workflow-resume
Wznawia pracę nad istniejącym workflow w nowej sesji: wczytuje przekazanie, dziennik przebiegu i wykonuje kolejny krok. - 92gsd-complete-milestone
Archiwizuje ukończony kamień milowy: przenosi roadmapę i wymagania do .planning/milestones/, aktualizuje PROJECT.md, taguje wersję i przygotowuje następną. - 100account-dossier
Ustala standard i proces budowy dossier konta klienta: strukturę, styl, wiarygodność źródeł, pochodzenie danych i brandowany render HTML.