A template sets up a project's types, workflows, fields, labels and filters in one step, and hands your agents the method as skills they follow. Manager comes with templates for many kinds of work, and whatever one sets up stays yours to change.
A template creates work item types with their statuses, custom fields, labels and shared filters. It also adds skills: the instructions your agents follow to work the method.
Skills reach every connected agent over MCP, not through your prompt. Ask for the flow check or the postmortem, and the agent works the steps the template lays down.
The Template step of a new project previews exactly what will be created: types, statuses with WIP limits, fields, labels, skills and filters. No guessing from a name.
A template applies once, when the project is created. From then on its setup is ordinary settings: rename statuses, add fields, edit or delete the skills.
Need an Incident or a Risk type in a running project? Import from Template adds just the types you tick, with statuses and fields, and overwrites nothing.
Shaped a project you like? Save it as a template, skills and filters included, and everyone in your organization can start from it. Admins choose the default.
They ship with Manager and are updated with it, so your next project starts from the latest version while running projects keep their own setup. Each card leads to a guide that puts the template to work.
The default: epics, goals, tasks and bugs, tuned for working with AI agents. The safe pick when no method calls for something else.
Read the guide →Backlog to Done with WIP limits, Expedite and Blocked labels, and two skills that keep work flowing. For support, operations and other continuous work.
Read the guide →Epics, stories, tasks and bugs with severity, plus skills to refine the backlog, plan sprints, review them and run the retro.
Read the guide →Bugs with severity and environment, feature requests with a workflow of their own, and tasks beneath both. For any product people report problems with.
Read the guide →Releases split into phases and atomic tasks, each phase run Discuss, Plan, Execute, Verify, Ship. Adapted from the open-source GSD method (MIT).
Read the guide →Features go from brainstorm to review, with small tasks built test-first and a definition-of-done gate. Adapted from the open-source Superpowers method (MIT).
Read the guide →Change an existing codebase one proposal at a time, with delta specs merged into living specs in your wiki. Adapted from the open-source OpenSpec method (MIT).
Read the guide →Every feature held to a project constitution, from specify and clarify through plan, tasks and analyze to implement. Adapted from GitHub Spec Kit (MIT).
Read the guide →Incidents graded SEV1 to SEV4 with a commander, a timeline in the comments and skills from declaring to the blameless postmortem. For on-call teams.
Read the guide →A risk register, Annex A controls with a Statement of Applicability, internal audits and corrective actions. Built around ISO/IEC 27001.
Read the guide →Documented processes, customer complaints, nonconformities with corrective actions and internal audits, run plan-do-check-act. Built around ISO 9001.
Read the guide →Records of processing, DPIAs, data subject requests, breaches on a 72-hour clock and processors in one project. Oriented to the GDPR; not legal advice.
Read the guide →Service requests, incidents, problems with known errors, and changes approved by a CAB, prioritized by impact and urgency. Follows ITIL practices.
Read the guide →Your agent reads the whole catalogue over MCP, with everything each template seeds, and creates the project from the one that fits. With the admin role, it also adapts the setup and borrows types from other templates.
Say to your agentManager: List the project templates and tell me which one fits a security review program, then create the project with the key SEC.
The agent compares what each template seeds, names the best fit and why, and creates the project from it, with types, fields, labels and skills in place.
Say to your agentManager: Create a project called Payments Rewrite with the key PAY from the Kanban template.
The project starts with Backlog through Done, WIP limits of 5 and 3, the Expedite and Blocked labels and two flow skills. The agent gets the full setup back, ready for the first stories.
Say to your agentManager: Add the Incident type from the Incident Response template to this project, and show me what would change first.
A dry run lists what would be added and what skipped. On your go-ahead the type arrives with its seven statuses and three fields, and nothing you have is touched.
Say to your agentManager: Our team finishes three cards at a time. Set the In Progress limit to 3 on every type and update the flow-check skill to match.
It changes the limit on each type's In Progress status and rewrites the numbers in the skill, in one call that leaves everything else as it was.
Everything a template carries, and what you can do with it before and after.
Guides that put this feature to work in a real project.
Pick a template, check the preview and create the project, by hand or through your agent. Shape it until it fits, then save it as a template of your own, so the next project starts where this one ended up.
Get early access