plane-workflow

Plane Workflow

Use the plane-workflow MCP tools as the primary path for Plane work. The tools resolve the active local Plane connection and apply a generic workflow with optional project-specific profiles.

Start Safely

1. For a first-time connection, call get_plane_workflow_setup_status. If it returns needs_setup, tell the user to run plane-workflow setup; do not ask them to paste an API key into the chat or a client config file.
2. Call get_active_plane_context before work-item changes. If the workspace or project is wrong, use list_configured_plane_workspaces and activate_plane_workspace, then list_plane_projects and activate_plane_project.
3. For an existing connection or unexpected failure, call diagnose_plane_connection with the project ID. Do not guess which Plane capabilities are enabled.
4. Call get_project_workflow_context before writing. Use get_workflow_options for state, cycle, assignee, and Plane estimate-point IDs.
5. Use get_project_workflow_profile to inspect local project rules. Use validate_workflow_profile and save_project_workflow_profile to preview and explicitly save a project override.

Understand Existing Work

1. Use get_project_briefing for a bounded overview of active work and overdue, stale, unassigned, unestimated, or unscheduled items.
2. Use list_work_items for explicit filters. Assignee, module, and cycle filters match any supplied ID; label filters require all supplied IDs. Use offset and max_results when has_more is true.
3. Use find_work_items for a title, UUID, or project reference lookup rather than as a project listing tool.
4. Use get_work_item_relations before discussing dependency direction. blocking means the source blocks the target; blocked_by means the target blocks the source.
5. Use add_work_item_relation as a preview first. Relation targets must belong to the selected project. Set confirm=true only after reviewing the source, targets, and direction.

Reports