What it does
Builds a new joiner's first ninety days as something that actually exists in the tools the team uses: a plan page they can read, dated tasks on the board with owners, and one announcement that tells the team who has arrived and what they will be working on. The plan is built backwards from a single question — what should this person be able to do on their own by day ninety — so each phase earns its place. The first thirty days are for context and one small shipped thing, because nothing shortens the settling-in period like completing something real in week two. Days thirty to sixty add ownership; sixty to ninety remove the scaffolding. It assigns the tasks that get forgotten and cost the most: the buddy, the accounts, the first one-to-one, the introductions to the people this role will depend on. Each has a named owner and a date, because an onboarding checklist with no owner is a document nobody executes. It never provisions access to anything. It creates the task saying who should grant what; a person with the authority does the granting.
Example prompts
- New backend engineer starts on the 12th. Build the 30-60-90.
- What should this person be able to do on their own by day ninety?
- Create the onboarding tasks with owners and dates from the plan.
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 2 credentials (2 required) to connect. See setup
