ow-start

Topics in the source

• ow-start: the fit call, its recap, and the logs
• Welcome (first run: nothing in the CRM or the cache)
• Verbs
• Questions and the one approval
• Where it lives in the CRM
• Phases
• Where files live
• Reading files

ow-start 2.0.1 · protocol 2 · Core bundle Open references/ow-protocol.md first and keep to it. If you cannot open it, say so and stop. Asking the user: every question and approval goes through AskUserQuestion, batched into one call per verb with your recommendation first; never a question or numbered menu typed into chat (references/ow-protocol.md §1). ow-start prepares the 20-minute call, then writes the recap the client receives: Today · What needs to change · Next step · What I need from you, one recommended path, due within one business day. It also keeps the logs: the meetings no other ow- skill records, and the decisions, per client and for your business. Read first. Every verb starts from the latest saved version of what it depends on in the CRM (below), never its own earlier file; prices, numbering, client profile and terms come from there. Where the CRM cannot be read or a route is not built, use the scratch cache in opchain-work/ (profile.md, offers.md, handoffs.yaml) and say so in the output. Never claim a publish the call did not confirm. Go with the flow: the user may skip a step, redo one, or jump straight to the recap from a transcript. Ask only what no file answers,

This is an excerpt. Refer to the complete source and its current requirements.