notion-sync

Query a Notion database for tasks, display them to the user, and allow updating task status. Uses the Codepresso Notion MCP server for API access.

<Use_When>

• User says "codepresso notion sync" or "sync notion tasks"
• User wants to see their Notion task board
• User wants to update a task status in Notion </Use_When>

<Do_Not_Use_When>

• Notion is not configured (direct user to codepresso:setup first)
• User wants PR logging only (that's automatic) </Do_Not_Use_When>

1. **Verify Notion configuration** - Load config and check `notion.apiKey` and `notion.defaultDatabaseId` exist - If `notion.userId` or `notion.displayName` are missing, warn user and suggest running `codepresso:setup` to set their identity - If missing API key or DB ID, inform user to run `codepresso:setup` first

2. Query Notion database

   • Use MCP tool notion_query_db with the configured database ID
   • The MCP server automatically limits results to the last notion.syncWindowDays days (default: 14). This prevents oversized responses. Users can adjust this in config or set to 0 to disable.
   • If notion.userId is configured, default to filtering tasks assigned to the user via the notion.assigneeProperty (default: "Assignee") using a people filter: { "property": "<assigneeProperty>", "people": { "contains": "<userId>" } }
   • If user explicitly asks for all tasks (e.g., "show all tasks"), skip the assignee filter
   • Apply additional filters if user specified (e.g., "show in-progress tasks")

3. Display tasks

   • Format tasks as a readable table or list
   • Show: title, status, assignee, due date (if available)
   • Highlight tasks assigned to the current user (based on notion.displayName)

4. Handle updates (if requested)

   • User selects a task to update
   • Use AskUserQuestion for new status
   • Use MCP tool notion_update_page to apply change

5. Create tasks (if requested)

   • When creating new tasks via notion_create_page, auto-assign to the configured user by setting the assignee property to notion.userId
   • Example property: { "<assigneeProperty>": { "people": [{ "id": "<userId>" }] } }

6. Link to PR (optional)

   • If a PR is detected, offer to add PR link to the Notion task
   • Use notion_update_page to set a URL property

<Tool_Usage>

• Use MCP tools: notion_query_db, notion_update_page, notion_create_page, notion_search
• Use AskUserQuestion for task selection and status updates
• Use Read to load config </Tool_Usage>

User: "codepresso notion sync" Action: Query DB, display tasks, offer to update User: "show my notion tasks for this sprint" Action: Query with sprint filter + assignee filter (using configured userId), display results User: "show all notion tasks" Action: Query without assignee filter, display all tasks User: "mark task X as done in notion" Action: Find task, update status to Done

<Final_Checklist>

• Notion API key configured
• User identity configured (userId + displayName), or warning shown
• Database queried successfully (filtered by assignee if userId configured)
• Tasks displayed to user
• Updates applied (if requested)
• New tasks auto-assigned to configured user (if created) </Final_Checklist>