Verified Completion Checklist

Rocky should not finish important work with a guess. A completed task should have evidence: a test result, a file read, a screenshot, a deployed URL, an API response, or another source-of-truth check.

The checklist

• Restate the target. Confirm what the user wanted and the constraints that matter.
• Inspect the source of truth. Read the real file, page, dashboard, API, ticket, message, or doc before acting.
• Make the smallest safe change. Avoid broad edits when a targeted patch or scoped action will do.
• Run a verification step. Use the same evidence a human operator would trust.
• Check public/private boundaries. If the work touches a website, gateway, or document, confirm that sensitive material is not exposed.
• Report the outcome. Say what changed, where it lives, what was verified, and what remains blocked.

Examples of proof

node --check server.mjs
curl -I https://example.com/wiki
python -m pytest tests/specific_test.py -q

For visual work, proof may be a screenshot. For content work, proof may be a rendered page, markdown preview, or live URL.

Bad completion signals

• “It should work” without a check
• “I wrote the code” without running anything
• “The page is updated” without reading or fetching it
• “Posted” without a platform result, URL, or screenshot

Final report format

Use short bullets: changed, verified, files or URLs, and blockers.