Push to ClickUp

Synchronize local roadmap files to ClickUp, creating or updating epics and milestones.

Arguments

$ARGUMENTS - Scope: "all", "epics", "sprint", or specific epic ID

Instructions

Phase 1: Gather Changes

1. Read configuration from .roadmap/clickup-config.json

2. Determine scope:

   • "all" or empty: Sync everything
   • "epics": Sync all epics and milestones
   • "sprint": Sync current sprint's milestones
   • Epic ID: Sync specific epic

3. Collect items:

   • Read epic files from .roadmap/epics/
   • Extract milestones from each epic

4. Compare with ClickUp:

   • For each epic/milestone, check sync mapping
   • Identify new items (no mapping)
   • Identify changed items (modified since last sync)

Phase 2: Present Changes

5. Show proposal:

   Push to ClickUp
   ===============
   
   CREATES (2 new items):
   | Type | Name | Parent |
   |------|------|--------|
   | Epic | Dashboard | - |
   | Milestone | M1: Charts | Dashboard |
   
   UPDATES (3 items):
   | Item | Field | Change |
   |------|-------|--------|
   | User Auth | M2 status | in-progress → done |
   | API v2 | M1 points | 8 → 13 |
   
   Proceed? [Y/n]
   

6. Wait for confirmation

Phase 3: Execute

7. Create new epics:

   • Use ClickUp MCP to create task (type: Epic)
   • Store mapping in config

8. Create new milestones:

   • Use ClickUp MCP to create subtask under epic
   • Store mapping in config

9. Update existing items:

   • Use ClickUp MCP to update task fields

10. Show summary:

    Push Complete
    =============
    Created: 2 items
    Updated: 3 items
    
    New mappings:
    - dashboard → cu_abc123
    - dashboard:M1 → cu_def456
    

Phase 4: Manual Sprint Assignment

11. Show milestones needing sprint assignment:

    After push completes, collect all milestones that have a sprint assigned locally but were just created or updated in ClickUp. Group by sprint and show:

    Manual Action Required
    ======================
    
    The following milestones need to be added to sprints in ClickUp:
    (ClickUp MCP doesn't support moving tasks to lists)
    
    Sprint 2025-W01:
    - [ ] Auth M1: Auth foundation (cu_abc123)
          → Add to Sprint 2025-W01 list in ClickUp
    - [ ] Dashboard M1: Chart components (cu_def456)
          → Add to Sprint 2025-W01 list in ClickUp
    
    Sprint 2025-W03:
    - [ ] Auth M2: OAuth providers (cu_ghi789)
          → Add to Sprint 2025-W03 list in ClickUp
    
    Quick links:
    - cu_abc123: https://app.clickup.com/t/abc123
    - cu_def456: https://app.clickup.com/t/def456
    - cu_ghi789: https://app.clickup.com/t/ghi789
    

12. Only show this section if there are milestones to assign. If all milestones are already in correct sprints or have no sprint, skip this section.

Mapping

Local	ClickUp
Epic	Task (type: Epic)
Milestone	Subtask under Epic
Status: planned	To Do
Status: in-progress	In Progress
Status: done	Complete
Start date	start_date field
End date	due_date field

Date Sync for Gantt

When milestones have Start/End dates (set via /roadmap-planner:schedule):

• Start → ClickUp start_date
• End → ClickUp due_date

Important: These are the milestone's estimated work dates, NOT the sprint dates.

Example:

• Sprint 2025-W01: Jan 6-17 (the 2-week window)
• Auth M1 (8 pts): Jan 6-10 (estimated 4 days of work)
• Dashboard M1 (5 pts): Jan 8-13 (different milestone, may overlap)

This enables accurate Gantt chart visualization in ClickUp showing when each milestone is actually planned to be worked on.

Important: Sprint Assignment

Milestones are created as subtasks under their parent Epic only.

ClickUp MCP doesn't support "move to list", so sprint assignment must be done manually in ClickUp. The push command shows which milestones need sprint assignment after sync completes.