--- name: workflow-complete-7559237c8d2f 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//` (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///dossier.md` [required] -- verify acceptance criteria status. 2. `.agents/workflows///handoff.md` [required] -- current state. 3. `.agents/workflows///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///acceptance.sh ``` **If it exits non-zero, stop.** Report: "Cannot complete workflow — acceptance.sh exited . 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 ### - **Actor**: - **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**: - **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: - Next Exact Step: N/A — workflow complete. - Active Risks / Blockers: none. 7. **Move the packet directory.** Relocate the entire workflow directory from `.agents/workflows///` to `.agents/workflows/done//`. 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//`. - 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//`. - `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. --- Source attribution: AMDResearch Original project: https://github.com/AMDResearch/omniprobe/blob/913ae319f727f8014e4db442a80e84915c8cf3a0/.agents/skills/workflow-complete/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice ------------------------------------------------------------------------------- MIT License Copyright (c) 2026 Advanced Micro Devices, Inc. All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ------------------------------------------------------------------------------- # Mega AI Hub resource metadata Creator / publisher: AMDResearch Original project: https://github.com/AMDResearch/omniprobe/blob/913ae319f727f8014e4db442a80e84915c8cf3a0/.agents/skills/workflow-complete/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Project & Program Management Roles: Business Process Analyst, Operations Manager, Project Manager Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b3269a10f44f1b4b34355be4f8bd2c4892f5fdb6596e27c8d7af2eb02183d3c9