Skip to main content

/pre-planning

Walk your open tasks in a ClickUp sprint to review and update story points before a planning ceremony. One task at a time, ending with a total.

Inputs (resolve, don't hardcode)​

  • Sprint list β€” accept a ClickUp sprint/list URL and extract the list id from the v/l/6-<list_id>-1 pattern; if absent, use clickup_get_workspace_hierarchy to let the developer pick the list.
  • Actor β€” default to the authenticated user (me); otherwise clickup_find_member_by_name.
  • Story-points field β€” resolve by name ("Story points") via clickup_get_custom_fields. Do not hardcode a field id (it differs per workspace). Read the field's option labels for the valueβ†’points mapping rather than assuming a fixed table; one point = one day is the house convention.

Steps​

  1. Confirm the sprint β€” clickup_get_list to show the sprint name back to the developer.
  2. Find open tasks assigned to the actor β€” clickup_filter_tasks / clickup_search scoped to the list, task_statuses: ["active"], assignee = the actor, detailed level (to read custom fields).
  3. Walk one task at a time β€” for each, show: name, id, status, URL, description, current story points, and subtasks. Wait for the developer to confirm or give a new estimate before moving on. Update via the custom field only when they give a value.
  4. Summarize β€” total story points across the sprint's tasks, and flag any task left without an estimate.

Boundaries​

  • Read, then update on confirmation. Never bulk-write estimates without the developer confirming each β€” this is a planning aid, not an auto-estimator.
  • No hardcoded workspace / list / field ids. Resolve everything by name/URL at runtime; if the ClickUp MCP is unavailable, say so and stop.
  • For day-to-day "what's on my plate," use /status; for a postable digest, /daily-summary.