Overview

Finishing Work is the final completion protocol that wraps up implementation with a completion summary, plan updates, and confirmation that all success criteria from the original plan are satisfied. It ensures a documented handoff and quality closure.

How This Skill Works

The skill verifies that all plan steps are marked complete, confirms that all success criteria are met, updates the plan document with the final status, and generates a detailed completion summary including steps, phases, files, tests, and reviews. It is integrated into methodologies/rpikit/rpikit-implement (completion summary) to produce the final summary, and then confirms with the user that the work is complete.

When to Use It

• After all implementation steps and reviews are complete
• When transitioning from implementation to done
• Final quality check before closing out work
• Before releasing a feature or updating stakeholders
• During project handovers to ensure documented closure

Quick Start

1. Step 1: Verify all plan steps are complete and success criteria are met
2. Step 2: Update the plan document with final status and generate the completion summary
3. Step 3: Confirm with the user that the work is complete and closed

Best Practices

• Always cross-check each plan step against the original criteria before closing
• Maintain a clear, auditable completion summary with concrete statuses
• List changed files and test results explicitly in the summary
• Include outcomes from code reviews and security review
• Reference the final plan document path in the completion records

Example Use Cases

• Wrapping up a feature after all unit tests pass and code reviews are approved
• Closing a sprint item by updating the plan with final status and summary
• Generating a completion summary before stakeholder handoff
• Finalizing security and code-review statuses in the plan document
• Confirming with the product owner that all success criteria are satisfied

Frequently Asked Questions