Build
Building means writing down how the work is done, well enough that YAMO can follow it. There are two doors into that and they lead to the same place: copy a template that already works, or start from a description of what you deliver.
Either way you end up with a Playbook: a readable document with ordered steps, the tools it needs and the reference files it works from. The document is the interface, so what you can read is what will run.
- Build from a templateCopying a working Playbook into your account: what you get, what stays yours, and what the copy asks you to replace before it is really about you.
- Build from scratchStart a Service from a brief, shape its definition with YAMO, then build and review the steps. Learn what is saved and when it becomes runnable.
- Writing the stepsThe ordered steps that do the work: what each one declares, how they hand work along the chain, and how instructions are written and changed.
- The Skill libraryReusable steps kept in your account: what a Skill is, how one is imported into a Playbook as a step, and what a Skill file has to say for itself.
- Readiness: making a Service runnableHow readiness makes a draft Service private automatically, which setup belongs to its owner, and what an Instance must supply before a Run starts.