Hire an AI project planning manager

Everything it can hand back

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

• A short summary that quotes the key requirements from your spec
• A numbered task list, each task sized for under an hour, with an acceptance check
• The gaps and unclear points in the spec, as questions to settle
• Assumptions the plan takes as true
• A quality checklist and the evidence still missing before you accept the plan

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: You have a written spec or brief for a website or app and need a task list a developer can start on.

• Scoped project plan. The work split into tasks, with what is in and out of scope.
• Acceptance checks. A check for each task that tells you whether the work is done.
• Assumptions. What the plan takes as true that you have not confirmed.
• Source references. Where each fact in the plan came from, such as your files or the role profile.
• Checks still needed. Missing evidence and steps to run before you accept the plan.

How the work is checked

• Every requirement can be tested.
• Assumptions and risks are listed with how each will be checked.
• Dependencies and owners are named.
• 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.

Capabilities

• Read the spec. It quotes the exact requirements and the stack, and lists any gaps or unclear points.
• Split the work. It breaks the spec into specific tasks, each small enough for under an hour, with no added extras.
• Add acceptance checks. It gives each task a clear, testable check, so you know when it is done.
• Review the result. It separates facts from assumptions and lists the evidence still missing.

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 project-manager-senior 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/project-manager-senior/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

• The project goal and the spec or brief, pasted or attached
• The deadline, budget and limits
• The team and who owns what
• Your tech stack, such as the framework and tools in use
• An existing plan or a tracker export, if you have one
• Anything the spec leaves out that you already know, such as a client request

Helpful context (optional)

• A written spec with the must-haves marked.
• Your deadline, budget and the people who will do the work.

Functions and deliverables

• Project planning manager: Give it a website or app spec. You get small tasks, each with an acceptance check, plus the gaps to settle first.
  • A short summary that quotes the key requirements from your spec
  • A numbered task list, each task sized for under an hour, with an acceptance check
  • The gaps and unclear points in the spec, as questions to settle
  • Assumptions the plan takes as true
  • A quality checklist and the evidence still missing before you accept the plan
  Source: Michael Sitarzewski and Agency Agents contributors.
• Notion build task planner: Turn a spec in Notion into a clear implementation plan and linked tasks, with gaps and assumptions listed before work starts.
  • A list of gaps and assumptions in the spec
  • A plan page, quick or full
  • Tasks created in your database
  • Links between spec, plan and tasks
  • Status updates as work moves
  Source: OpenAI.
• Project kickoff brief writer: Turn a rough idea into a project kickoff brief with goal, audience, tone and limits that your team can sign off. Under two pages.
  • One-page brief
  • Clear goal, audience and tone
  • Scope and limits
  • A list of open questions to settle
  Source: RampStack.
• AI task handover writer: Write a task handoff brief for another AI agent: goal, files it owns, limits and a done check. Plus a plan to track its progress.
  • A handoff brief with scope and limits
  • A check for success
  • A polling plan with sensible gaps
  • A report of changes and open issues
  Source: sickn33.
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.

Tasks you can use it for

• You have a written spec or brief for a website or app and need a task list a developer can start on.
• Your tasks are too big or too vague to estimate, and you want them split with a check for each.
• You suspect the spec has gaps and want them listed before work starts.

Limits to check before starting

• You need live project data or a tracker updated. Your AI cannot reach your tools here, so use your project tool and paste in what it shows.
• You want someone to approve spending, send messages or change live systems. Ask a person on your team to do that.
• You only need a short to-do list for one day. Write it by hand or ask your AI for a quick list instead.
• You have no written brief yet. Write down the goal and the must-haves first, then run this.

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 pack and open SETUP.md. Add it to your AI as a skill, or paste SKILL.md and then references/source-agent.md into a chat.
• Paste your spec, goal, deadline, budget, team and tech stack. Attach an existing plan if you have one.
• Ask for the task list. Say "Quote my spec and mark every gap. Do not add features."
• Check each task against the spec. Answer the gap questions, then ask it to update the list.
• Look for tasks with no acceptance check or no clear owner, and have them fixed.
• Copy the accepted tasks into your project tool. The agent cannot update it for you.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/project-manager-senior 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.