@olegkoval/agent-skills 1.32.0 → 1.33.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-agent-skills",
   "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.",
-  "version": "1.31.0",
+  "version": "1.32.0",
   "author": {
     "name": "Oleg Koval"
   },
@@ -42,6 +42,7 @@
     "./packages/software-development/codexloop",
     "./packages/software-development/geminiloop",
     "./packages/software-development/add-to-my-skills",
+    "./packages/software-development/wrap-up",
     "./packages/software-development/ai-tools-setup",
     "./packages/software-development/changelog-generator",
     "./packages/software-development/wikipedia-uk-editor",

package/.cursor-plugin/index.json

@@ -151,6 +151,11 @@
       "source": "./packages/software-development/add-to-my-skills/adapters/cursor",
       "description": "Copy a newly created skill from another repo into this catalog, refresh the README and generated manifests, then commit and push."
     },
+    {
+      "name": "olko:wrap-up",
+      "source": "./packages/software-development/wrap-up/adapters/cursor",
+      "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+    },
     {
       "name": "olko:ai-tools-setup",
       "source": "./packages/software-development/ai-tools-setup/adapters/cursor",

package/.grok-plugin/index.json

@@ -161,6 +161,11 @@
       "source": "./packages/software-development/add-to-my-skills/adapters/grok",
       "description": "Copy a newly created skill from another repo into this catalog, refresh the README and generated manifests, then commit and push."
     },
+    {
+      "name": "olko:wrap-up",
+      "source": "./packages/software-development/wrap-up/adapters/grok",
+      "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+    },
     {
       "name": "olko:ai-tools-setup",
       "source": "./packages/software-development/ai-tools-setup/adapters/grok",

package/.kiro/steering/wrap-up.md

@@ -0,0 +1,77 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+---
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/.windsurf/rules/wrap-up.md

@@ -0,0 +1,76 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+---
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/README.md

@@ -3,7 +3,7 @@
   <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
   <p>
     <img src="https://img.shields.io/badge/license-MIT-16a34a" alt="MIT license">
-    <img src="https://img.shields.io/badge/skills-47-2563eb" alt="47 skills">
+    <img src="https://img.shields.io/badge/skills-48-2563eb" alt="48 skills">
     <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Grok%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Grok Copilot Windsurf Kiro">
     <img src="https://img.shields.io/badge/status-public%20catalog-16a34a" alt="Public catalog">
   </p>
@@ -139,15 +139,16 @@ packages/{category}/{skill}/SKILL.md
 
 </details>
 
-## All 47 Skills
+## All 48 Skills
 
 Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup name in a new agent session.
 
-### Software development (41)
+### Software development (42)
 
 | Skill | What it does | Use when |
 |-------|-------------|----------|
 | [add-to-my-skills](packages/software-development/add-to-my-skills/SKILL.md) | Copies a newly created skill from another repo into this catalog, refreshes the README and generated manifests, then commits and pushes | Adding a skill you wrote elsewhere into this catalog |
+| [wrap-up](packages/software-development/wrap-up/SKILL.md) | Verifies a completed task against its original objective, confirms applicable checks, and safely tidies task-owned artifacts, worktrees, and local branches | Periodic or end-of-task delivery and cleanup review |
 | [ai-tools-setup](packages/software-development/ai-tools-setup/SKILL.md) | Sets up, repairs, and reports on the RTK + ICM + Vox AI development toolkit — installs missing tools, fixes broken hooks and MCP config | Bootstrapping AI dev tools on a new machine or diagnosing broken integrations |
 | [apple-store-submit](packages/software-development/apple-store-submit/SKILL.md) | Handles App Store rejection emails end-to-end — parses rejection reasons, creates a fix plan, implements code changes, and prepares resubmission | Responding to App Store rejections for privacy strings, entitlements, or guideline violations |
 | [changelog-generator](packages/software-development/changelog-generator/SKILL.md) | Transforms git commits into polished user-facing changelogs by categorising changes and rewriting technical commit messages | Preparing release notes, app store update descriptions, or a public changelog |
@@ -294,7 +295,7 @@ See [docs/skill-anatomy.md](docs/skill-anatomy.md) for the package format.
 ```text
 agent-skills/
 ├── packages/
-│   ├── software-development/   (39 skills)
+│   ├── software-development/   (42 skills)
 │   ├── marketing/              (3 skills)
 │   ├── music/                  (1 skill)
 │   └── photography/            (1 skill)

package/catalog/skills.json

@@ -766,6 +766,30 @@
         "grok"
       ]
     },
+    {
+      "name": "wrap-up",
+      "lookupName": "olko:wrap-up",
+      "category": "software-development",
+      "path": "packages/software-development/wrap-up",
+      "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches.",
+      "tags": [
+        "delivery",
+        "verification",
+        "cleanup",
+        "git",
+        "worktrees",
+        "release-hygiene"
+      ],
+      "adapters": [
+        "codex",
+        "claude",
+        "cursor",
+        "copilot",
+        "windsurf",
+        "kiro",
+        "grok"
+      ]
+    },
     {
       "name": "ai-tools-setup",
       "lookupName": "olko:ai-tools-setup",

package/collections/software-development.json

@@ -12,6 +12,7 @@
     "product-builder",
     "mvp-oneshot",
     "wikipedia-uk-editor",
+    "wrap-up",
     "vinted-listing",
     "shared-knowledge-artifact"
   ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@olegkoval/agent-skills",
-  "version": "1.32.0",
+  "version": "1.33.0",
   "private": false,
   "publishConfig": {
     "access": "public"

package/packages/software-development/add-to-my-skills/adapters/codex/README.md

@@ -1,3 +1,17 @@
-# Codex adapter
+# Codex Adapter for add-to-my-skills
 
-Use the canonical skill directly from `packages/software-development/add-to-my-skills/SKILL.md`.
+This is the Codex-specific adapter for the `olko:add-to-my-skills` skill. The canonical workflow is in
+`../../SKILL.md`.
+
+## Usage
+
+Invoke it when a skill from another repository or a catalog page should become a first-class package:
+
+```text
+Use the olko:add-to-my-skills skill to bring this skill into the catalog, generate all adapters, validate it, and publish the change.
+```
+
+For Codex, resolve a supplied `skills.olegkoval.com/skills/<name>/` URL to its canonical GitHub or local
+source before copying. Preserve unrelated dirty work, prefer an isolated worktree, update the canonical
+`SKILL.md` before generated adapters, run `npm run build` and `npm test`, and report commit/push/PR state
+separately from local validation.

package/packages/software-development/wrap-up/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: wrap-up
+description: Verify that a completed implementation matches its original objective, all applicable checks are green, and task-owned temporary files, worktrees, and local branches are safely tidied.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, Grok, and other Agent Skills compatible tools.
+metadata:
+  author: Oleg Koval
+  tags:
+    - delivery
+    - verification
+    - cleanup
+    - git
+    - worktrees
+    - release-hygiene
+---
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/packages/software-development/wrap-up/adapters/claude/plugin.json

@@ -0,0 +1,5 @@
+{
+  "name": "olko-wrap-up",
+  "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches.",
+  "skills": "./skills"
+}

package/packages/software-development/wrap-up/adapters/claude/skills/wrap-up/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: wrap-up
+description: Verify that a completed implementation matches its original objective, all applicable checks are green, and task-owned temporary files, worktrees, and local branches are safely tidied.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, Grok, and other Agent Skills compatible tools.
+metadata:
+  author: Oleg Koval
+  tags:
+    - delivery
+    - verification
+    - cleanup
+    - git
+    - worktrees
+    - release-hygiene
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/packages/software-development/wrap-up/adapters/codex/README.md

@@ -0,0 +1,17 @@
+# Codex Adapter for wrap-up
+
+This is the Codex-specific adapter for the `olko:wrap-up` skill. The canonical workflow is in
+`../../SKILL.md`.
+
+## Usage
+
+Invoke it manually or after a completed task:
+
+```text
+Use the olko:wrap-up skill to verify the completed task, clean task-owned artifacts, and report the delivery receipt.
+```
+
+For Codex, keep the receipt fields required by the agent operating contract and treat local correctness,
+remote state, PR state, CI, deployment, and human/device QA as separate gates. Use `git worktree list`
+before removing worktrees, preserve unrelated dirty files, and never claim completion from a local green
+check alone.

package/packages/software-development/wrap-up/adapters/cursor/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:wrap-up",
+  "version": "0.1.0",
+  "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches.",
+  "skills": "skills/"
+}

package/packages/software-development/wrap-up/adapters/cursor/skills/wrap-up/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: wrap-up
+description: Verify that a completed implementation matches its original objective, all applicable checks are green, and task-owned temporary files, worktrees, and local branches are safely tidied.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, Grok, and other Agent Skills compatible tools.
+metadata:
+  targets: ["cursor"]
+  author: Oleg Koval
+  tags:
+    - delivery
+    - verification
+    - cleanup
+    - git
+    - worktrees
+    - release-hygiene
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/packages/software-development/wrap-up/adapters/grok/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:wrap-up",
+  "version": "0.1.0",
+  "description": "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches.",
+  "skills": "skills/"
+}

package/packages/software-development/wrap-up/adapters/grok/skills/wrap-up/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: wrap-up
+description: Verify that a completed implementation matches its original objective, all applicable checks are green, and task-owned temporary files, worktrees, and local branches are safely tidied.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, Grok, and other Agent Skills compatible tools.
+metadata:
+  author: Oleg Koval
+  tags:
+    - delivery
+    - verification
+    - cleanup
+    - git
+    - worktrees
+    - release-hygiene
+---
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/packages/software-development/wrap-up/adapters/kiro/steering/wrap-up.md

@@ -0,0 +1,77 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+---
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.

package/packages/software-development/wrap-up/adapters/windsurf/rules/wrap-up.md

@@ -0,0 +1,76 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Verify a completed task against its original objective, confirm applicable checks, and safely tidy task-owned artifacts, worktrees, and local branches."
+---
+
+# Wrap Up
+
+Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work.
+
+## 1. Reconstruct the task
+
+- Read the original request, acceptance criteria, task plan, and final diff.
+- Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status.
+- Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete.
+- Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work.
+
+## 2. Verify the implementation
+
+- Inspect the final diff and confirm every requested behavior is implemented.
+- Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them.
+- Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling.
+- Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results.
+- If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass.
+- For user-facing behavior, require real browser/device or human evidence when that is part of acceptance; automated tests alone are not visual acceptance.
+
+## 3. Verify delivery state
+
+Keep these gates separate and evidence-backed:
+
+- Local worktree: branch, `HEAD`, tracked changes, and untracked files.
+- Remote: tracking branch and remote SHA, verified with Git or the existing provider CLI.
+- PR: current title/body, merge state, review threads, and required checks, when applicable.
+- CI: current-head status, not an old successful run.
+- Deployment: actual deployed version or endpoint health, when applicable.
+- Device or human QA: real acceptance evidence, when applicable.
+
+Do not claim remote, PR, CI, deployment, or QA completion from a local test or commit alone. Do not push, merge, deploy, or delete a remote branch as a side effect of this skill unless the task explicitly authorized it.
+
+## 4. Clean task-owned artifacts
+
+Clean only paths created by this task or explicitly named for cleanup.
+
+- Remove known temporary files, test output, logs, copied fixtures, and scratch directories after capturing any required evidence.
+- Never recursively delete a broad directory, the workspace root, an unresolved glob, or an unknown untracked file.
+- For dirty paths that predate this task or cannot be attributed confidently, leave them in place and report them.
+- Check the repository’s worktree list and remove only task-owned worktrees that are clean and no longer needed. Use an exact path; never remove a worktree containing uncommitted user work.
+
+## 5. Clean local branches safely
+
+- Confirm the task branch has the intended commit and that the remote branch contains the same work when remote delivery was required.
+- If the remote branch is merged, verify the merge state before deleting the local branch.
+- If the remote branch is pushed but unmerged, treat it as the recovery point. Delete the local branch only when the task is delivered, the remote branch is confirmed intact, the worktree is clean, and the user’s workflow permits local deletion. Otherwise preserve it and report why.
+- Never use force branch deletion or destructive checkout/reset commands unless the user explicitly requests that exact recovery operation.
+- Before deleting a branch, verify it is not checked out by another worktree and that no unique local commits would be lost.
+
+## 6. Report the result
+
+Lead with the outcome. Include concise evidence, cleanup performed, items intentionally preserved, and the smallest next action for any blocker. Always finish with this receipt, using `NOT_APPLICABLE` for out-of-scope gates and `NOT_RUN` for applicable checks that were not executed:
+
+```text
+OBJECTIVE:
+CHANGED:
+NOT_CHANGED:
+TESTS:
+BUILD:
+REMOTE:
+PR:
+CI:
+DEPLOYMENT:
+DEVICE_OR_HUMAN_QA:
+KNOWN_LIMITATIONS:
+FINAL_STATUS:
+```
+
+`FINAL_STATUS` must be exactly one of `DELIVERED`, `BLOCKED`, or `INTENTIONALLY_UNCHANGED`. Use `BLOCKED` when required evidence or cleanup cannot safely be completed; name the blocker and next action. Never promote a partial result to `DELIVERED`.