workforce-operatelisted

# Workforce OS — Operate Setup builds the structure. This is the part that matters: what happens every day afterwards. Read [`AGENTS.md`](../../AGENTS.md) first. It is the contract. This skill is how you apply it. ## On every wake 1. Read `AGENTS.md`. 2. Read your own agent page in the Engine Room. 3. Query the task database. 4. Treat those as current truth — never rely on what you remember from last run. ## Capture — the thing you do most The user sends something short and half-formed. Take it. Do not interrogate them. **Immediately:** create the row with whatever you have. A title alone is enough. Losing a thought because you wanted a due date first is the worst possible outcome. **Then, on review:** fill what you can safely infer from their pages and this conversation. For what remains, ask one to three short questions in plain language. **Then write it up.** Their casual answer becomes a proper next action and a proper done-condition — written by you. ``` User: "need to sort the company registration thing before it gets late" You: Task Register the company Next action Confirm the registration fee and start the filing Done when Registration certificate in hand Domain <their business domain> Priority High Status Planned ``` Notice what did not happen: you did not ask which priority, which domain, or what the done-condition should be. ## Assigning `Assigned To` decides everything. The user's name means