finishing-work

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
graph	{"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}

• When transitioning from implementation to done
• Final quality check before closing out work

Process

1. Verify all plan steps marked complete
2. Confirm all success criteria met
3. Update plan document with final status
4. Generate completion summary (steps, phases, files, tests, reviews)
5. 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)