Use cases
People
Build onboarding guides, answer ownership and policy questions and schedule recurring reminders.
Merlin recipes for people and operations teams. Build a first-week guide from the sources the team owns, answer "who owns what" from an org skill, keep policy answers in an intake channel, draft internal announcements, save working agreements to memory and schedule the recurring reminders.
How people prompts work
People teams answer the same questions many times, and the answers live in documents that drift. The recipes below run in the channels where those questions arrive: the onboarding channel, the people-ops intake channel and each team's own channel. Each prompt is a Slack message. Merlin posts progress in that thread and the result lands there: a guide, an answer with its source, a draft or a scheduled reminder.
What you need
| Requirement | Why it matters here |
|---|---|
| Merlin in the onboarding and intake channels | Questions and drafts run where they are asked. |
| Org-chart, team-topology or onboarding skills | "Who owns what" and "how we work" come from a maintained source, not a guess. |
| A runtime with the repositories' READMEs (for engineering hires) | Code layout and release process are read from the current repository. |
| A channel appropriate for organization information | Team and role details stay with the audience allowed to see them. |
Do not put credentials or confidential personnel records into a shared skill or memory.
Prompts to paste
Build a first-week guide
Give the role, the team and the outcome, and name the sources.
@Merlin create a first-week guide for a new backend engineer. Cover who owns what, where the code lives, how on-call works and how releases ship. Use the team-topology skill and current repository READMEs.
Naming the sources keeps the guide tied to things the team maintains. The hiring manager can extend it in the same thread:
Add the access requests they should complete on day one and mark anything that still needs an owner.
To plan a new hire's first two weeks, see it step by step.
Answer "who owns what"
Route ownership questions to the org skill instead of the channel.
@Merlin who owns the billing service and who approves changes to it? Answer from the team-topology skill and say when it was last updated.
Asking for the update date shows when the skill needs refreshing.
Give an intake channel a standing role
Other teams bring people-ops their policy questions. Save the role once to the channel's memory so requests are answered from the policy docs.
@Merlin remember for this channel: when someone tags you on a policy question, answer from the people-handbook skill, name the section you used, and route anything it does not cover to the people-ops lead with a one-line summary.
A fact answered by a person in the thread can be saved the same way when it will come up again:
@Merlin remember for this channel: conference budget is 1,500 per person per year and the team lead approves each request.
Draft an internal announcement
A decision is made in a leadership thread. Ask for the announcement in the team's voice.
@Merlin turn this thread into an all-hands announcement under 150 words: what changes, from when, and where to ask questions. Use the internal-comms skill.
Refresh onboarding material when the code moves
Guides go stale when repositories are reorganized. Ask for the diff.
@Merlin compare the engineering onboarding guide against the current repository READMEs and list every step that no longer matches, with the replacement.
Schedule recurring reminders
The reminders that people-ops sends by hand can be scheduled to the right channel.
@Merlin every Monday at 10am, post the new starters this week from the onboarding skill with their buddy and the checklist items still open.
Scheduled automations deliver to Slack and run on behalf of their creator. Fixed times run in the workspace timezone for a channel automation and in your personal timezone for a direct-message automation.
Save working agreements to memory
Each team channel can save its own agreements. In a public channel, Merlin reads them in every later conversation in the workspace, so keep each one specific to the team.
@Merlin remember for this channel: standup is async in this channel by 10am, Fridays are meeting-free, and PTO goes in the shared calendar before it goes in Slack.
Memory in a private channel is visible only to that channel's current members.
Limits
Skills and memory can become stale. Ask Merlin to distinguish current repository facts from team guidance and to flag conflicts rather than choosing silently.
Merlin answers from the sources it is given. A policy that is not written down is not something it can look up.