π Auto Finish Work by Rose β Master page
Spot the missing pieces before you call a job finished. πΉ
π― The job
Spot the missing pieces before you call a job finished. The aim: less faff, more progress. The boss fight is still checking the result.
βοΈ How the approach works
Start with your goal, follow the documented steps, then inspect the result. You keep the final say on anything consequential.
β¨ Product-specific scope
- Compare requested deliverables with the final answer
- Suggest precise follow-ups for omitted work
- Preserve completed files and previous progress
- Respect retry limits and approval gates
π§ͺ Example
Check whether my requested checklist, file and summary were actually delivered.
π Boundaries and evidence
Recorded status: Planned. Availability labels describe the project record; they do not promise a public release.
Page art is illustration, not proof of a working interface.
β How to judge a good result
A good run gets you closer to the goal and changes nothing you did not approve. If the screen disagrees with this guide, stop and check the version.
πΉ Page art is decorative; it does not show the product UI.
