/plan
Plan a task from a Notion page URL
> /plugin marketplace add makenotion/claude-code-notion-plugin > /plugin install notion-workspace-plugin@notion-plugin-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/plan
Context preview
What this command does when you run it.
Plan a task from a Notion page URL
Command definition
plan.mddescription: Plan a task from a Notion page URL
args: task_url
Build Task from Notion
You are planning a task that is tracked in Notion. Your end goal is to put a plan in the task doc in Notion. The user is only watching the Notion board and isn't watching this session, so all feedback to the user must be sent through the Notion MCP.
Input
The user has provided a Notion task URL: `$ARGS`
Your Task
1. **Fetch the task details** from Notion using the MCP tools
- Get the page content including title, description, and any relevant properties
- Look for acceptance criteria, requirements, or specifications
- Read any linked pages or references if needed
2. **Mark planning**
- Change the status of the task to "planning".
- Update the "Agent status" field to contain a short generic text description: π€ emoji followed by a word like "Starting..." or "Working..."
3. **Build it**
- Make a plan for how to work on the task per the specification. For example, if this a coding task,
- At each step, update the "Agent status" field to explain what's currently happening, so the user can see what's going on. Keep it brief: a relevant emoji followed by a few words. Examples: "π Searching relevant files...", "βοΈ Writing the plan..."
- For most complex tasks you will probably need to get some user input. If you need to get user input to clarify the spec or answer other questions, follow the Communication Protocol below. Try to ask just a few questions at a time, don't overwhelm the user with too many questions at once.
4. **Update the task status** Once complete:
- Write the plan into the task page, in a new section at the end of the page called "Plan"
- Update the task status in Notion to "Ready"
- Follow the Communication Protocol below and briefly tell the user the results of the task. Link to the diff explanation if appropriate for a code change.
Communication Protocol
Every time you want to communicate with the user, follow the following steps.
- Add a comment to the task. Prefix your comment with "Message from Claude:" on its own line in bold.
- Set the "Agent blocked" column to true, and the Agent Status column to a short message explaining the request, like "β Choose a color scheme" or "β Give architecture feedback"
- Poll every 10 seconds to see if the user has responded with their own comment. (Follow polling instructions below)
How to poll
- Always use a sub-agent to poll with max turns set to 100 to avoid polluting the parent content.
- You can use a Bash sleep interleaved with MCP tool call.
Notes
- If the URL is invalid or inaccessible, ask the user to verify the URL and their Notion connection
- If requirements are unclear, ask clarifying questions before writing the plan
Read more
description: Plan a task from a Notion page URL args: task_url
Build Task from Notion
You are planning a task that is tracked in Notion. Your end goal is to put a plan in the task doc in Notion. The user is only watching the Notion board and isn't watching this session, so all feedback to the user must be sent through the Notion MCP.
Input
The user has provided a Notion task URL: `$ARGS`
Your Task
1. **Fetch the task details** from Notion using the MCP tools
- Get the page content including title, description, and any relevant properties
- Look for acceptance criteria, requirements, or specifications
- Read any linked pages or references if needed
2. **Mark planning**
- Change the status of the task to "planning".
- Update the "Agent status" field to contain a short generic text description: π€ emoji followed by a word like "Starting..." or "Working..."
3. **Build it**
- Make a plan for how to work on the task per the specification. For example, if this a coding task,
- At each step, update the "Agent status" field to explain what's currently happening, so the user can see what's going on. Keep it brief: a relevant emoji followed by a few words. Examples: "π Searching relevant files...", "βοΈ Writing the plan..."
- For most complex tasks you will probably need to get some user input. If you need to get user input to clarify the spec or answer other questions, follow the Communication Protocol below. Try to ask just a few questions at a time, don't overwhelm the user with too many questions at once.
4. **Update the task status** Once complete:
- Write the plan into the task page, in a new section at the end of the page called "Plan"
- Update the task status in Notion to "Ready"
- Follow the Communication Protocol below and briefly tell the user the results of the task. Link to the diff explanation if appropriate for a code change.
Communication Protocol
Every time you want to communicate with the user, follow the following steps.
- Add a comment to the task. Prefix your comment with "Message from Claude:" on its own line in bold.
- Set the "Agent blocked" column to true, and the Agent Status column to a short message explaining the request, like "β Choose a color scheme" or "β Give architecture feedback"
- Poll every 10 seconds to see if the user has responded with their own comment. (Follow polling instructions below)
How to poll
- Always use a sub-agent to poll with max turns set to 100 to avoid polluting the parent content.
- You can use a Bash sleep interleaved with MCP tool call.
Notes
- If the URL is invalid or inaccessible, ask the user to verify the URL and their Notion connection
- If requirements are unclear, ask clarifying questions before writing the plan
This repository provides an official Claude Code plugin that bundles: Notion Skills (from the Notion Cookbook) that teach Claude how to work intelligently inside your Notion workspace The Notion MCP Server, which enables Claude to securely search, read, and
Other commands on notion.
- /create-database-row
Insert a new row into a specified Notion database using natural-language property values.
Open command - /create-page
Create a new Notion page, optionally under a specific parent, using the Notion Workspace Skill and Notion MCP server.
Open command - /create-task
Create a new task in the userβs Notion tasks database with sensible defaults.
Open command - /database-query
Query a Notion database by name or ID and return structured, readable results.
Open command - /find
Quickly find pages or databases in Notion by title keywords.
Open command - /search
Search the userβs Notion workspace using the Notion MCP server and Notion Workspace Skill.
Open command

