Hire an AI team goal and responsibility planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A few goals, each with key results that have a number and a date
• A one-on-one plan with how often to meet each person, how long, an agenda they write, and how to follow up
• A decision plan with one named owner, who to hear from, the strongest case against, a date and what everyone does after the call

How it does the job well

• Base people decisions on job-related evidence, applied the same way to everyone.
• Write in plain, respectful language the person affected could read.
• Keep personal data to what the task needs, and handle it privately.
• Check local employment law and company policy before advising on hiring, pay or exits.

Mistakes it avoids

• Biased wording in job ads, reviews or interview questions.
• Plans with no owner, timing or way to check progress.
• Treating a template as legal advice.

What a good result looks like

An example, not your task: You manage a team and each person is working on something different, with no shared goal to pull it together.

• step-01-okr-goal-writer.md. A few goals for the period, each with key results that have a number and a date.
• step-02-one-on-one-meeting-planner.md. How often to meet each person, how long, the agenda they write and how to follow up.
• step-03-informed-captain-decisions.md. One named owner, who to hear from, the strongest case against, a decision date and next actions.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Andy Grove and Jeff Bezos would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Write goals and key results. Turns what you want into a few short goals for the period. Gives each one dated key results that can be marked done or not done.
• Plan the one-on-ones. Uses the goals to set how often to meet each person, how long, and what they bring. Adds a follow-up routine so actions get checked.
• Settle the decision. Takes the goals and your stuck decision. Names one owner, collects the best case against, sets a date and says what everyone does after the call.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id team-goals-one-on-ones only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/team-goals-one-on-ones/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your team, meaning who is on it, what they do and how experienced they are
• What you want to get done in the period (a quarter or a month)
• Last period's results, if you have them (optional)
• A current plan or list of priorities (optional)
• The decision that is stuck, if there is one (step 3 skips without it)

Helpful context (optional)

• Last period's results
• A short note on how each person is doing
• The goals of the team above you

Tools and access

• Any good chat AI: Holds your team notes and writes all three plans in one run.
• A shared document: Gives each person somewhere to write their one-on-one agenda.
• Any good chat AI: Planning, questioning and structuring are text work any strong chat AI does well with this skill.
• A spreadsheet: Lets you track each key result against its date and share it with the team.
• Any good chat AI: Structuring decisions and writing plans is text work any strong chat AI does well with this skill.
• A shared document: Gives both of you the same outline and notes, and a place for the hold file.

Functions and deliverables

• Team goal and responsibility planner: Share your team, quarterly goals and constraints. Get measurable goals, a one-to-one meeting plan and named decision-owner rules.
  • A few goals, each with key results that have a number and a date
  • A one-on-one plan with how often to meet each person, how long, an agenda they write, and how to follow up
  • A decision plan with one named owner, who to hear from, the strongest case against, a date and what everyone does after the call
• Objectives and key results writer: Write team goals and key results for the quarter. Give it your team and aim. You get a few objectives with dated, numbered key results.
  • A few short objectives
  • Key results for each, with a number and a date
  • A link from each to the level above
  • A list of what you will not do, and a note on how to use the set
• One-on-one meeting planner: Plan a one-on-one meeting with someone who reports to you. Get how often to meet, an outline they write, meeting rules and follow-up.
  • How often to meet, and how long
  • A meeting outline they write, with the parts you require
  • Rules for the meeting: questions, notes, the hold file
  • A follow-up routine for actions
• Team decision ownership planner: Plan a big team decision with one named owner. Get a plan to hear the strongest case against, a decision date and a review date.
  • One named owner, with the reason
  • A list of who knows most and who disagrees
  • A request for the strongest case against, per person
  • A decision date, an attendee list, ground rules and a review date
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up
• Andy Grove: Set team goals or examine a business threat using Andy Grove’s recorded approach. Find the limiting step, paired measures and the right decision owner.
  • Your problem worked on the way Andy Grove would: their questions, their method, their push-back
  • The answer or the work, in Andy Grove's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jeff Bezos: Review a product or stuck decision through Jeff Bezos’s recorded approach. Start with the customer, test what can be undone and write the reasoning.
  • Your problem worked on the way Jeff Bezos would: their questions, their method, their push-back
  • The answer or the work, in Jeff Bezos's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You manage a team and each person is working on something different, with no shared goal to pull it together.
• Your one-on-ones are dull, rushed or skipped, and you suspect they should do more.
• Two people disagree on a decision and it has been stuck for days.

Limits to check before starting

• You work alone with no team: write your own goals with the Objectives and key results writer, or use a simple to-do list.
• You need one quick decision with no ongoing team: ask a trusted colleague to argue against it, then pick a date and decide.
• You only want better one-on-ones and already have goals: use the One-on-one meeting planner by itself.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It has HANDOFF.md and three skill files, in the order they run: Objectives and key results writer, One-on-one meeting planner and Informed captain decision planner.
• Open Claude Code, or a Claude Project with the files added, and say "Follow HANDOFF.md". With only a chat window, paste each skill in order and carry each result to the next.
• Describe your team and the period. Add the stuck decision if you have one.
• Check the key results first, since the other two steps use them.
• Share the goals with your team before your first one-on-one.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/team-goals-one-on-ones for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.