Finish One Real Job First

On this machine, pick work with speakable rules and a rollback. Write the object, where outputs go, and how you will accept it. Install no skills yet.

Put the five-step loop onto the workbench. The blue book puts “finish one real job” before skills and connectors because without a comparison, packed capability cannot be accepted.workbuddy-guide

After reading, you should be able to answer:

• How do you write the five things for a local job?
• Why install no skills on the first loop?
• What does on-the-spot acceptance look at?

Point the five things at a result on this machine

A sample skeleton (WorkBuddy, not a universal spell):

• Object: this batch of files in Downloads, inspect read-only.
• Result: sort by the rule into three new folders; leave a list in the original place.
• Format: the list has old path and new path.
• Bounds: do not delete, do not overwrite same-name files, stop and list anything unsure.
• Accept: sample ten files; paths match the list; originals are still findable.

Skills later

Install every skill first, and the process will show a lot of capability without showing which step is executing your five things. Permission may also open before the job exists. Finish the loop, then pack this skeleton into a container — that order is the next article.