MCP Prompt Library

Give me a full overview of my Puzzle workspace — list all tabs, all sections within each tab, and all steps within each section. For each section, tell me what process it covers, which roles are involved, and which tools are used.

List all the tabs in my Puzzle workspace. For each tab, tell me how many sections it contains and give me a one-line summary of what that tab covers based on its sections and steps.

Show me everything inside the [tab name] tab — list every section and summarize the steps within it. Reference each step, tell me the role responsible, the tool used, and any notes attached.

Audit my Puzzle workspace. List every tab, section, and step. Flag anything that looks incomplete — steps with no roles assigned, steps with no tools linked, sections with no steps, or tabs that appear empty.

Go through all steps in my Puzzle workspace and identify any that are missing key details — no role assigned, no tool linked, no notes, or no step type set. Group them by section so I know where to focus.

Give me a summary count of my Puzzle workspace — how many tabs, sections, steps, roles, tools, people, and entities do I have? I want a quick snapshot of the size and scope of my operational blueprint.

List all tools in my Puzzle workspace. For each tool, summarize the steps it's linked to and how many times it appears across my workflows. Highlight the top 5 tools that have the most amount of steps — these are my most critical systems.

List all roles in my Puzzle workspace. For each role, summarize steps they're assigned to and across which sections. Who has the most steps, and are there any roles that appear very rarely? Which steps have no role assigned at all?

Walk me through the [section/workflow name] process from start to finish. For each step, explain what happens, who does it, which tool is used, and how it connects to the next step. 

Explain it so that I can execute the process following your directions, and ask questions if there are conditional paths that determine which process branch to follow for a given run. 

In my [section name] workflow, what happens after the [step name] step? Trace the downstream steps and explain how the process continues from that point.

In my [section name] workflow, what needs to happen before the [step name] step can begin? Trace the upstream dependencies.

Go through my [section/workflow name] and tell me who owns each step — list the step name and the role responsible. Highlight any steps that have no owner assigned.

Show me every tool used in the [section/workflow name] process. For each tool, summarize the steps it appears in and what it's being used for based on the step context.

How does [team/role A] hand off to [team/role B] in my workflows? Find every step where this transition happens and describe what gets passed between them.

Search my entire Puzzle workspace for every step that uses [tool name]. Summarize the section, step name, and role assigned to each one. I want to understand the full footprint of this tool across my operations.

List all teams and roles in my Puzzle Teams canvas. For each team, show me the roles within it and describe what each role is responsible for based on the steps they're assigned to in my workflows.

Give me a complete job descriptions of what the [role name] role does across my entire Puzzle workspace — summarize every step they're involved in, which section it belongs to, and what tool they use at each step like a standard job description.

I'm a [role name]. Based on all the steps assigned to my role in Puzzle, create a custom onboarding playbook for my first week — what processes I'm part of, what I'm responsible for at each step, and how my work connects to the rest of the team and roles.

Go through all steps in my Puzzle workspace and list any that have no role assigned. Group them by section. These are ownership gaps I need to fill.

List all people in my Puzzle People canvas. For each person, tell me their name, type (Employee, Contractor, etc.), and which roles they're assigned to. Show me how they connect to each other based on the connectors between their people cards.

Based on my Puzzle People canvas, map out the reporting structure. Who reports to whom?

Generate a process optimization proposal for [workspace, tab, or section name — leave blank to scan everything]. Pull a full picture first: use list_sections and list_steps to map every workflow, list_roles and list_teams and list_people to see who runs what, list_tools and list_tool_groups for the tech stack, and list_entities and list_attributes to understand the data model and how information flows

Then analyze across these angles and rank findings by ROI (frequency × duration × ease of change): 

Automation candidates (Person-executed steps that are repetitive, rules-based, or already touch automatable types like email, form, notification, database, payment); 

AI agent candidates (research, drafting, classification, summarization steps still done manually); 

Tool expansion (tools used in only one or two steps that likely have broader capabilities being missed); 

Tool consolidation and compatibility (overlapping tools doing similar jobs, gaps where a connector or integration would remove a manual handoff); 

Quality control gaps (workflows missing review, approval, conditional, or verification steps before high-stakes actions); 

Role overload (roles linked to many high-frequency or long-duration steps, single points of failure); handoff friction (steps where work transitions between roles or tools with no clear trigger); 

Data model issues (entities referenced across many processes without a clear system of record, attributes captured in one process but needed in another);

Documentation gaps (Live steps with no notes, Draft or Testing steps that have been sitting stale). 

For each opportunity, give the specific step or section it applies to, why it matters, the proposed change, and a rough effort estimate. Group findings into Quick Wins, Medium Lifts, and Strategic Bets so we can sequence the work.

Review my [section/workflow name] workflow and identify the top 3 potential bottlenecks or inefficiencies. For each one, explain what's causing it and suggest a specific improvement I could make.

Compare my [section A] and [section B] workflows. What do they have in common? Where do they diverge? Are there steps in one that are missing from the other and should probably exist?

Look across all my workflows in Puzzle and find steps that appear to do the same thing — same tool, same role, similar name. List the duplicates and suggest which ones could be consolidated or replaced with an Alias step.

Look at my [section/workflow name] and identify any steps where only one role is responsible for something critical with no backup or alternative path. These are single points of failure — list them and suggest how to reduce the risk.

Review my [section/workflow name] and identify any steps that seem too broad (doing multiple things at once) or too granular (could be merged into a single step). Give me specific recommendations.

Look at my [section/workflow name] workflow. Based on the step names, roles, and tools, does anything seem like it's missing — a handoff that isn't documented, a decision point that isn't captured, or a step that should logically exist between two others? Suggest additional steps that could improve how the workflow works.

Review my [section/workflow name] workflow against general process design best practices. Are steps clearly named? Is ownership clear for each step? Are there decision points that should be conditional steps? Give me a structured assessment.

Look at the [section/workflow name] in my Puzzle workspace. Based on the step cost data already entered (time, frequency, and assigned roles), give me a cost breakdown — per run, per month, and annually. Flag any steps that are missing cost data.

Look across all my workflows and identify which sections or steps have the highest labor cost based on the time, frequency, and role rates entered. Rank them from most to least expensive, and suggest ways to streamline them.

I have a [current state section] and a [future state section] in my workspace. Compare the costs of both — what's the estimated cost difference per month and per year? What's the ROI of the future state?

Go through my [section/workflow name] and identify all steps executed by a Person (not Automation or AI Agent) that have the highest time and frequency values. These are my most expensive manual steps — list them with their estimated monthly cost.

List all tools in my Puzzle Tools canvas that have a cost entered. Give me the total monthly and annual spend, and show me which tools are the most expensive. Are there any tools that appear in very few workflow steps relative to their cost?

Go through my [section/workflow name] workflow and identify which steps are currently executed by a Person but could realistically be automated by a System or AI Agent. Prioritize by how often the step runs and how rules-based it is.

Look at all steps across my Puzzle workspace. What percentage are currently set to Person, System, or AI Agent? Break it down by section. Where is my automation coverage lowest?

Search my entire workspace for steps that run at high frequency (daily or more) and are still assigned to a Person. These are my best candidates for automation. List them with their section and frequency.

Look through my [section/workflow name] workflow and identify which steps would be best handled by an AI Agent — things like drafting, summarizing, routing, classifying, or generating outputs. For each one, describe what the AI agent would do and what it would need as input.

Based on all the manual steps across my workflows, build me a prioritized automation roadmap. Which automations would have the biggest impact on reducing time and cost? Rank them by effort vs. impact.

Look at the [section/workflow name] in my Puzzle workspace. Write a detailed summary I can share with a client — list every step, the role responsible, the tool used, any notes, and how steps connect. Format it clearly without requiring access to Puzzle.

Summarize the [section/workflow name] process for a non-technical stakeholder. Explain what it does, who's involved, what tools are used, and what the output is. Keep it clear and jargon-free.

Show me every Changelog entry associated with the [section/workflow name] workflow in my Puzzle workspace. For each entry, include the title, owner, status, date, and a summary of what changed. Present it chronologically so I can see how this workflow has evolved over time.

I just made changes to the [section/workflow name] workflow. Create a new Changelog entry documenting:
What changed and why
The rationale behind the decision
Any trade-offs considered
Steps and tools affected
Associate the entry with the relevant steps and tools, set the status to [idea / planned / in_progress / completed], and assign me as the owner.

Take the [section/workflow name] workflow in Puzzle and convert it into a written Standard Operating Procedure. For each step, write a paragraph explaining what happens, who does it, what tool they use, and what the expected output is. The SOP should allow a person to follow the process knowing what happens, and how the systems work beneath it, and why it's built that way. 

I'm onboarding a new [role name]. Based on their role assignments in Puzzle, generate a structured onboarding document — what processes they'll be part of, what each step requires them to do, who they'll hand off to, and what tools they'll need access to.

Give me a high-level summary of my entire Puzzle workspace that I could share with a new team member on their first day — what tabs exist, what each one covers, the key roles involved, and the most important workflows to understand first.

Create a new Shared View in my Puzzle workspace called [View Name]. Include:
Workflow sections: [Section 1, Section 2, ...]
Teams: [Team 1, Team 2, ...]
Tool groups: [Group 1, Group 2, ...]
People tabs: [Tab 1, Tab 2, ...]
Save the view and return the shareable link.

Create a Shared View for [audience — e.g., "our client Acme Corp", "new hires in Sales", "the finance team"]. Include only the content they need to see:
The relevant workflow sections that show the process they're involved in
Any teams or tool groups they interact with
Any People Canvas tabs that show their point of contact
Name the view something clear like "[Audience] View", save it, and give me the shareable link.

Update my [View Name] Shared View:
Add: [sections, teams, tool groups, or people tabs to add]
Remove: [content to remove]
Keep everything else as is and return the updated shareable link.

Duplicate my [Existing View Name] Shared View. Save the copy as [New View Name]. Then remove [X content] and add [Y content] so it fits [new audience or use case].

List every Shared View in my Puzzle workspace. For each one, show me:
The view name
What's included (sections, teams, tool groups, people tabs)
The shareable link
Present it as a table so I can scan quickly.

Here is an SOP for [process name]: [paste SOP text]. Build this as a new workflow in my Puzzle workspace using 1 section — create the section and steps needed to map this process end to end, assign the relevant roles and tools based on what already exists in my workspace, and add the relevant notes from the SOP to each step. Be detailed. 

[Optional]
It's important for you to use conditional steps where there might be logical branches to the process flow. Also, ask me any clarifying questions where there might be gaps in my SOP as it relates to the details and interconnectivity needed to make Puzzle documentation powerful, then after I answer your question proceed with building it in Puzzle. 

Create a new workflow in Puzzle for [process name]. The process works like this: [describe the process]. Build it using 1 section only and steps, connect them in the correct order, and assign roles and tools from my existing workspace where relevant.

[Optional]
It's important for you to use conditional steps where there might be logical branches to the process flow. Also, ask me any clarifying questions where there might be gaps in my SOP as it relates to the details and interconnectivity needed to make Puzzle documentation powerful, then after I answer your question proceed with building it in Puzzle. 

Create a team structure on my Puzzle Teams canvas for a [team type, e.g. Sales team]. Include the following roles: [list roles]. Set up reporting lines between them and connect them to the relevant steps in my workflows where possible. Build it like an organization chart style where the more senior roles are above the more junior roles branching in a organized fashion.

Create person cards on my Puzzle People canvas for the following team members: [list names, types, roles]. Connect them to reflect the reporting structure and assign them to their relevant roles on the Teams canvas. Build it like an organization chart.

Create a tool group on my Puzzle Tools canvas called [group name] and add the following tools to it: [list tools]. Link each tool to the relevant steps in my workflows where it's already being used, and add notes in the tool's notes based on what the tool is known to do. 

Create a data model in Puzzle for the [process name] process. The key entities are [list entities, e.g. Contact, Deal, Invoice]. For each entity, create the following attributes: [list attributes per entity]. Then link the relevant attributes to the steps in my [section name] workflow.

[Optional] Fill out the attribute description to your best knowledge about what the field represents in the data model.

Move the following sections into [tab name] tab: [list section names]. This tab will represent [describe what this tab covers].

Go through all steps in my [section/workflow name] that have no notes. For each one, generate a clear description explaining what the step does, who does it, and why it matters — based on the step name, role, and tool already assigned.

[Optional] If it ambiguous which steps do what, or which roles are responsible for what,  give bulk suggestions that I can approve before you go make those changes.

Look through my [section/workflow name] and find all steps that have no role assigned. Based on the step name and tool used, suggest which existing role from my Teams canvas should own each one — then make the assignments.

Look through my [section/workflow name] and find all steps that have no tool linked. Based on the step name and role, suggest which existing tool from my Tools canvas should be linked to each one — then make the assignments.

I've just completed a process review of [section/workflow name]. Update the following steps to [Draft/In Progress/Testing/Live/Archived] status: [list step names and their new statuses]. Leave all other steps unchanged.

Look at all steps in my [section/workflow name]. Are there any that don't follow a clear verb-noun naming pattern (e.g. "Send Invoice", "Review Contract", "Update Record")? List any that are inconsistently named and suggest better names, then update them.

I'm replacing [old tool name] with [new tool name] across my workflows. Find every step in my workspace that uses [old tool name] and replace it with [new tool name]. Show me which steps will be affected before making any changes.

In my Puzzle data model, mark the following attributes as Deprecated: [list attribute names]. These fields are no longer in active use and I want to flag them without deleting them yet.

Cross-reference my Puzzle Teams canvas and Workflows canvas. Which roles own the most steps across all workflows? Which roles own the fewest? Give me a ranked list.

Cross-reference my Tools and Workflows canvases. For each tool in my workspace, tell me which roles are most frequently using it across my workflows. I want to understand who depends on what.

Cross-reference my People canvas and Workflows canvas. For each person in my workspace, list the roles they're assigned to and then the steps those roles are responsible for. I want to understand each person's operational footprint.

Search my entire workspace for steps that use [tool name] AND are assigned to [role name]. I want to see where these two things overlap.

I'm considering removing [tool name] from my tech stack. Look across all my workflows and tell me every step that would be affected. Which processes would break or need to be updated? Give me a full impact assessment.

I'm restructuring the [role name] role. Find every step, section, and workflow this role is involved in across my entire workspace. I want a full picture of what would be affected before making any changes.

I'm setting up a new Puzzle workspace for [company/team type]. Build the following for me: (1) a Workflows canvas with sections and steps for [process 1], [process 2], and [process 3]; (2) a Teams canvas with the relevant roles and reporting lines; (3) a Tools canvas with the tools used across these processes; (4) a People canvas with [list people/roles]. Connect everything together — link roles and tools to their relevant steps.

Run a complete audit of my Puzzle workspace and give me a structured report covering: (1) workflow completeness — are all steps documented with roles, tools, and notes? (2) team coverage — are all roles assigned to relevant steps? (3) tool coverage — are all tools linked to the steps that use them? (4) data model completeness — are entities and attributes linked to the workflows that use them? Prioritize issues by impact.

I want to document a process improvement project. Take my existing [section name] workflow and: (1) duplicate it into a new section called "[Section Name] — Future State"; (2) in the future state, update the following steps to reflect the changes I'm planning: [describe changes]; (3) add a note to each changed step explaining what's different and why.

Create a change management plan for improving [section name]. Start by pulling the current state to find the workflow, then check the roles, tools, and step-level details so you know who's affected and what's involved. 

The plan should cover what's changing [describe the change], why it matters, who gets impacted, a rollout sequence with owners and target dates, communication points for each affected role, training and documentation needs, success criteria, and risks with mitigations. 

Reference the Team Canvas and Tools Canvas so the plan reflects how the operation runs today, and any data model or data migrations changes that will be needed.

Map every handoff point in my workspace — places where one role passes work to another. For each handoff, tell me: which roles are involved, which step it happens at, which section it's in, and whether the handoff is clearly documented in the step notes.

Look across my entire Puzzle workspace and identify the processes most at risk — workflows with high step counts and low documentation, steps with no role owner, sections with no tool coverage, or processes that appear to be single points of failure. Give me a prioritized risk list.

Look at my [section/workflow name] workflow. Based on the steps, tools, and roles involved, suggest what entities and attributes should exist in my specific tool's data model to represent the data flowing through this process. First report back to me what you're suggesting to create. Do not building anything just yet. 

[Optional] Then create those entities and attributes and link the relevant attributes to the steps that use them.

Every week I want to review the state of my operations. Generate a weekly operations report for my Puzzle workspace covering: (1) any steps that changed status this week; (2) sections or workflows that appear incomplete; (3) roles that have the most active steps; (4) tools that appear most across live steps; (5) any data model attributes that are still in Draft status and most importantly (6) suggest 1-5 process optimization suggestions, ways I can expand how I'm using my current tech stack to improve my processes. 

Format it as a report I can share with my team.