Automated summary

This skill defines a completion protocol that verifies all plan steps are done, confirms success criteria, and produces a final completion summary.

Strengths

Breaks task closure into five explicit steps, from plan verification to user confirmation
Enforces a standardized summary format covering steps, phases, files, tests, and reviews
Uses existing code and security reviews as exit conditions before declaring work done

Limitations

Relies on an existing plan document; without one, step and criteria checks have nothing to verify against
Contains no real automation: verification stays a manual discipline guided by the agent
Designed to plug into rpikit-implement, which limits use outside that workflow

When to use it

Use it after implementation and reviews are finished, to close out work cleanly and produce a traceable recap.

When not to use it

Avoid invoking it mid-implementation or when no plan and success criteria were defined beforehand.

Security analysis

Safe

Quality score70/100

The skill is a pure completion/verification workflow. Declared tools (Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion) are powerful but are used only for legitimate purposes: checking plan status, updating the plan document, and generating a summary. There are no destructive commands, no network exfiltration, no obfuscated payloads, and no instructions to bypass safety or handle secrets. Risk is limited to normal file edits within the user's project.

No concerns found

How this analysis is made

Examples

Clôturer une implémentation

L'implémentation et la revue de code sont terminées. Vérifie que toutes les étapes du plan sont complètes, confirme les critères de succès et génère le résumé de complétion.

Vérifier les critères de succès

Avant de clôturer, repasse sur le plan document et dis-moi si chaque critère de succès est réellement satisfait, avec le statut des tests et des revues.

Récapitulatif final

Produis le résumé final de cette tâche : étapes et phases complétées, fichiers modifiés, statut des tests, verdict de revue et chemin du document de plan.

name: finishing-work description: Final completion discipline including summary generation, plan document updates, and confirmation that all success criteria from the original plan are satisfied. allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion

Finishing Work

Name: Finishing Work
Author: Skills Guide Bot

Overview

Final completion protocol ensuring implementation is properly wrapped up with summary, plan updates, and success criteria confirmation.

When to Use

After all implementation steps and reviews are complete
When transitioning from implementation to done
Final quality check before closing out work

Process

Verify all plan steps marked complete
Confirm all success criteria met
Update plan document with final status
Generate completion summary (steps, phases, files, tests, reviews)
Confirm with user that work is complete

Summary Format

Steps completed: N/M
Phases completed: N/M
Files changed: [list]
Test status: passing/failing
Code review: verdict
Security review: passed/failed
Plan document: path
All success criteria met: yes/no

Tool Use

Integrated into methodologies/rpikit/rpikit-implement (completion summary)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/finishing-work-mmio718s/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/finishing-work-mmio718s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/finishing-work-mmio718s/download' --output '.skill-downloads/finishing-work-mmio718s/SKILL.md.part' && mv '.skill-downloads/finishing-work-mmio718s/SKILL.md.part' '.skill-downloads/finishing-work-mmio718s/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/finishing-work-mmio718s/SKILL.md' && test -s '.skill-downloads/finishing-work-mmio718s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/finishing-work' && cp -R '.skill-downloads/finishing-work-mmio718s' '.claude/skills/finishing-work'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/finishing-work-mmio718s'

openskills read 'finishing-work-mmio718s'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/finishing-work-mmio718s/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot