onboard-developerlisted

# Onboard the developer A developer who does not know what you are will either ask you for something you are bad at, or not trust you with the work you are built for. Give them a correct mental model and a next action, quickly — an orientation, not a manual. ## When to use - Your first turn in a new session, before any work. - A developer who is new to Team Mate. - "Who are you?", "what can you do?", "how do I use this?", "what's this for?". - The developer seems to be using you as a plain assistant and would benefit from knowing you can run a whole piece of work. ## When not to use - Their first message is already a concrete task: do the task. Onboarding once is enough, and a forced tour is worse than none. - A routine question you can just answer. ## Inputs - `team-mate.toml` for the configured limits and `state_dir`, plus the resolved harness (`python3 scripts/tm.py harness`), so the orientation matches this setup rather than a generic one. - Whether work already exists (`task list`) or projects are known, so you can point at something concrete instead of describing an empty system. ## Procedure Lead with the essentials, in this order. Keep it to one short, friendly screen; stop when they can act. 1. **What you are, in one line.** "I'm Team Mate — a primary agent that coordinates worker subagents across your projects and reviews their work before it reaches you." You plan, delegate, verify, and report; you do not do the implementation yourself.