Project Manager Template

• What it does: The Project Planner agent gathers project type, objectives, industry, team, and detailed requirements, breaks them into tasks with scope, timelines, deliverables, and dependencies, and can produce a Gantt-style timeline. It then hands off to the PM Agent, which cleans and structures the task list and creates Linear tickets with estimates and assignees.
• Best for: project managers, team leads, ops teams that use Linear (or a similar issue tracker) and want a plan-to-ticket flow
• Apps used: Web Search, Linear (MCP)
• Setup time: 10 to 15 minutes

Project Manager is a no-code, two-agent workflow that turns project details into a structured plan and then into Linear tickets. The Project Planner does not create tickets; it only gathers requirements, breaks down tasks (with scope, timelines, deliverables, dependencies), and produces a task list and Gantt or timeline view, then hands off to the PM Agent. The PM Agent receives the task data, cleans and structures it, and creates tickets in Linear with estimates and assignees. You can also use the PM Agent alone (e.g. to create, update, or review tickets by message). Linear requires an API key in the MCP tool config. This template acts as a starting point: any app, instructions, and agents can be updated as required for your own use case—simply ask Max (Agent Builder) to update the workflow as needed. Last verified from workflow config on March 2026. Includes common failure modes and fixes.

---

Problem this solves

• Turning a project brief into a clear task list and timeline is manual and inconsistent.
• Creating tickets one by one in Linear (or similar) from a plan is slow and error-prone.
• You want one flow: provide project details, get a plan and then tickets with estimates and assignees.
• Requirements gathering, breakdown, and ticket creation in one workflow keep the plan and tracker in sync.

---

What this agent does

This template can:

• Project Planner: Require project type, objectives, industry, team members, and detailed requirements before planning. Analyze requirements, break them into individual tasks with descriptions, scope, achievable timelines, and deliverables. Identify dependencies between tasks. Produce a comprehensive task list and a Gantt chart or similar timeline visualization. Hand off to the PM Agent (task list + timeline); the Planner does not have access to the PM/Linear tool and does not create tickets.
• PM Agent: Receive the task list and timeline from the Planner (or receive a user request to create/update tickets). Clean and structure the content into clear, actionable tasks. For each task, create a Linear ticket with time/resource/effort estimates, assignee (by matching skills and availability when possible), and clear descriptions. Complete ticket creation for all provided tasks. Support project tracking and execution.
• Web Search (Planner): Optional use for research (e.g. industry norms, estimates); the Planner can use web search to inform task breakdown or timelines.
• Linear (PM Agent): Create (and, if configured, update) issues in Linear via the Linear MCP; the template uses an MCP tool with URL https://mcp.linear.app/mcp and Bearer token (API key) in headers.

---

How it works

1. You provide project details via the text trigger: project type, objectives, industry, team members involved, and detailed project requirements. (Or you can ask the PM Agent directly to create tickets, update tickets, or review work if you use only that agent.)
2. Project Planner checks that required data (type, objectives, industry, team, requirements) is present. It analyzes requirements, breaks them into tasks (descriptions, scope, timelines, deliverables), identifies dependencies, and produces a task list and Gantt or timeline visualization. It then hands off the task list and timeline to the PM Agent. The Planner does not call the Linear tool.
3. PM Agent receives the task data, cleans and structures it into clear tasks, then for each task creates a Linear ticket with estimates, assignee, and description using the Linear MCP tool.
4. When the user needs to create tickets or check issues, the handoff to the PM Agent happens after the Planner has produced the plan (or you can invoke the PM Agent separately for ticket-only actions if you adapt the workflow).
5. You get confirmation and can see the created tickets in Linear; the plan (task list + timeline) is in the workflow output from the Planner handoff.

---

Requirements

• Linear account and API key: Required for the PM Agent to create tickets. Obtain a Personal API key from Linear (Workspace settings → API → Personal API keys). Configure the Linear MCP tool: URL https://mcp.linear.app/mcp, header Authorization: Bearer <your-api-key>, and enable the tool. See the template’s Linear MCP sticky note for step-by-step instructions.
• Project input (for full plan → tickets flow): Project type, objectives, industry, team members, and detailed requirements. The Planner will not start until these are provided.
• Web Search: Optional for the Planner; enabled by default. No key required.
• Optional: customize the Planner and PM Agent instructions for your company’s SOPs, PM structure, and how you assign (e.g. by skill, availability).

---

Setup guide

1. Clone the template and open it in AgentSpace.
2. Configure Linear MCP: Click the Linear tool node (linear_tools). Set URL to https://mcp.linear.app/mcp. In headers, add Authorization: Bearer <your-linear-api-key>. Obtain the API key from Linear: Workspace settings → API → Personal API keys → Create new, then paste. Enable the tool. Fill any other required fields (e.g. MUST FILL) in the MCP config.
3. Web Search: Leave enabled for the Project Planner if you want it to use web search for research or estimates.
4. Optional: Update the Project Planner instructions with your company’s objectives, industry defaults, or SOPs. Update the PM Agent instructions for how to assign (e.g. assignee selection rules) and for any required Linear project or team IDs if your tool config needs them.
5. Run Test Workflow with full project details (type, objectives, industry, team, requirements). Confirm the Planner produces a task list and timeline and hands off to the PM Agent, and that the PM Agent creates Linear tickets with estimates and assignees. Check Linear to verify tickets.
6. (Optional) Use the PM Agent alone: if you remove or bypass the Planner for some runs, you can send messages like "Create tickets for the following tasks: …" and have only the PM Agent run; ensure the handoff and trigger are wired for that use case if you want it.

Common issues and fixes

• Linear tickets not created: verify the Linear MCP tool is enabled and the Authorization header has a valid Bearer token (API key). Check Linear API docs and the MCP allowed_tools if the tool supports create-issue or similar. Ensure the PM Agent is receiving task data (from handoff or user) and calling the Linear tool with the right parameters.
• Planner does not start or says data missing: the Planner requires project type, objectives, industry, team members, and detailed requirements. Provide them in the trigger message or in a structured way the Planner can parse.
• Wrong assignees or estimates: the PM Agent assigns by matching skills and availability as per its instructions; refine the instructions or provide assignee hints in the task list. Estimates come from the PM Agent’s logic; you can add rules or examples in the instructions.
• Want to use Jira instead of Linear: replace the Linear MCP tool with a Jira tool from the SketricGen marketplace (or another MCP/integration) and update the PM Agent instructions to create Jira issues with the same fields (description, estimate, assignee).

Customization knobs

• Add or change planning outputs (e.g. risk section, resource load) in the Project Planner instructions.
• Replace Linear with Jira or another issue tracker: swap the tool and update the PM Agent to create issues in that system.
• Use only the PM Agent for ticket creation/updates without the Planner by triggering the PM Agent directly and providing task list or instructions in the message.
• Tune the Planner for your industry or PM structure (SOPs, terminology) in the agent instructions; see the template’s Customisation Options sticky.

---

Apps used

(Linear scopes depend on the MCP and your API key. See Linear API documentation.)

---

Use cases

• Project kickoff: One run with project type, objectives, team, and requirements to get a task list, timeline, and Linear tickets. Best for PMs and team leads.
• Sprint or release planning: Feed scope and team; get broken-down tasks and tickets with estimates and assignees. Best for agile teams.
• Cross-functional projects: Planner breaks down by phase and dependency; PM Agent creates tickets and assigns. Best for ops and product.
• Ticket creation from a list: Skip or shorten the Planner and send a task list to the PM Agent to create tickets only. Best for quick backlogs or imports.
• Ongoing PM: Use the PM Agent to answer questions, update tickets, or review work (extend the workflow so the trigger or another agent can send such requests to the PM Agent). Best for daily PM use.

---

Example prompts and outputs

Example 1: Full plan and tickets

Prompt (input): "Project: Website redesign. Objectives: New homepage and pricing page live by Q2. Industry: B2B SaaS. Team: Alice (frontend), Bob (backend), Carol (design). Requirements: Responsive design, A/B test on pricing, CMS integration, analytics. Create the plan and tickets."

Output: Project Planner produces a task list (with scope, timelines, deliverables, dependencies) and a Gantt or timeline, then hands off to the PM Agent. PM Agent creates Linear tickets for each task with estimates and assignees. You see the plan in the run and the tickets in Linear.

Example 2: Tickets only (if workflow supports it)

Prompt (input): "Create Linear tickets for: (1) Set up staging env, 2 days, Alice; (2) Design homepage mockups, 3 days, Carol; (3) Implement homepage, 5 days, Alice."

Output: If the trigger routes to the PM Agent with this content, the PM Agent can create the three tickets in Linear with the given estimates and assignees. (This assumes you have adapted the workflow to allow direct PM Agent invocation.)

Example 3: Plan only (no Linear)

If the Linear tool is not connected, the Project Planner still runs and produces the task list and timeline; the PM Agent will not be able to create tickets. You can use the plan as a doc or paste it into another tool.

---

Why you need this template

• One flow from project details to a plan and to tickets (with estimates and assignees) in Linear.
• Consistent breakdown and ticket structure; you can tune the Planner and PM Agent for your process.
• Editable in AgentSpace: change planning outputs, swap Linear for Jira or another tracker, or use the PM Agent alone for ticket-only actions.
• Optional web search in the Planner for research or estimation support.

---

FAQs

1) Is this an AI agent template or a fixed automation?

It is a multi-agent workflow (Project Planner, PM Agent) you can edit in AgentSpace. You control what the Planner requires and what the PM Agent writes to Linear (or another tracker). This template acts as a starting point: any app, instructions, and agents can be updated for your own use case—simply ask Max (Agent Builder) to update the workflow as needed.

2) Do I have to use Linear?

No. You can replace the Linear MCP with another issue tracker (e.g. Jira) from the SketricGen app marketplace and update the PM Agent instructions to create issues there with the right fields.

3) Where do I get the Linear API key?

Linear: Workspace settings (click workspace name) → API → Personal API keys → Create new API key. Copy the key and paste it in the Linear MCP tool config as Authorization: Bearer <your-api-key> in headers. The template’s Linear MCP sticky has the exact steps.

4) Can I use only the PM Agent without the Planner?

Yes. You can adapt the workflow so the trigger or another agent sends a task list (or "create tickets for…") directly to the PM Agent. The Planner is optional for runs where you already have a plan and only need tickets.

5) What input does the Planner need?

Project type, objectives, industry, team members involved, and detailed project requirements. The Planner will not start the planning process until these are provided.

6) Does the Planner create tickets?

No. The Planner only produces a task list and Gantt/timeline and hands off to the PM Agent. The PM Agent has access to the Linear tool and creates the tickets.

7) What are the main failure modes?

Linear MCP not configured (missing or invalid API key, wrong URL or headers), Planner not receiving required project data, or PM Agent not receiving task data from the handoff. Fix by checking Linear config, providing full project details, and ensuring the handoff passes the task list and timeline to the PM Agent.

8) Can I add more agents (e.g. risk or resource)?

Yes. Add another agent (e.g. Risk Agent) that consumes the plan or task list and produces risk or resource output; add handoffs and optionally feed that into the PM Agent or a doc. You can also add a step to save the plan to Google Docs or Notion.

---

Related templates

• Internal Team Support – internal Q&A from knowledge bases.
• Github Code Review – structured code review output.
• Pre-Meeting Preparation – meeting briefs with context.
• Personal Ops AI Assistant – calendar, comms, and retrieval.
• AI Receptionist – route inbound to Q&A, booking, or escalation.