Agent onboarding
Give a new teammate or agent a named Pack of the context, examples, and workflows needed to start useful work.
Build a Pack around a job
Choose a concrete role or project, such as frontend engineering or release preparation. Gather the current docs, conventions, examples, and checks that apply to that work. Use source content for instructions the agent needs to follow; a saved link points to a page and does not preserve its contents.
Keep the Pack focused. Explain when each item is useful, which instructions take priority, and who maintains the material. A clear name such as frontend-onboarding makes it easier to ask for the right context.
Share it with the right workspace
Put company material in the company workspace. The owner invites the teammate, and the teammate connects their agent to that workspace. Access to a Pack follows the workspace access; a personal library stays private.
Ask the agent: Use the frontend-onboarding Pack from Sirro, then explain the setup and checks for this project. Review its understanding before handing it a task.
Start with a real task
Give the teammate a small piece of work that uses the Pack. Check whether the agent found the right examples, followed the conventions, and ran the required checks. Record missing context and confusing instructions.
Onboarding gives the agent a shared starting point. It still needs the current repository, the task requirements, and permission for any actions that require approval.
Maintain the starting point
Update the shared material when a workflow changes. Keep names stable so teammates can ask for the same Pack next time. Have a responsible person review changes before the team treats them as its standard.
The planned company Playbook workflow will add recorded outcomes and owner-approved improvements for recurring tasks. Packs already let teams collect the working knowledge that those methods depend on.