Bulk operations
When you need to update many tasks at once — closing out a milestone, wiring up dependencies for a new goal, or recording work that finished but was never marked — bulk operations do it in a single action with one combined preview.
Bulk complete
Mark up to 50 tasks as done in one operation.
From Claude Code:
Other phrasings work too — “Mark all the dashboard widget tasks as complete” or “Close out the remaining tasks in the Dashboard MVP milestone.” Claude calls plenar_bulk_complete with the task IDs. The response includes:
- A single New Plan preview showing the combined impact of completing all the tasks
- One set of pending changes to apply
- A list of skipped tasks (already completed or not found)
Use cases:
- Milestone closure — complete remaining tasks when a milestone ships
- Catch-up — record tasks that were finished but not yet marked in Plenar
- End-of-period cleanup — mark a batch of finished work done at once
After reviewing the preview, use plenar_apply_changes to apply all completions at once.
Bulk add dependencies
Add several dependencies in a single call with one combined preview.
From Claude Code:
Claude calls plenar_bulk_add_dependencies with the full dependency map. You see one preview showing how all the new dependencies affect the plan together.
Use cases:
- Setting up a new goal with known task ordering
- Establishing dependencies after importing tasks from another tool
- Restructuring a goal’s task graph
Bulk remove dependencies
Remove several dependencies at once when restructuring.
From Claude Code:
Claude calls plenar_bulk_remove_dependencies. The preview shows freed tasks and any earlier finish dates that become possible.
Use cases:
- Removing unnecessary ordering constraints so Plenar can parallelize more work
- Restructuring after a scope change
Preview and apply
All bulk operations go through the same edit → preview → apply loop as individual changes. You always see the combined impact before anything is committed:
- The bulk operation computes a single New Plan preview.
- You review what moved, what improved, and what got worse.
- Apply to commit, or Discard to throw the New Plan away.
The only difference from a single edit is that the preview reflects every change at once, so you see the true combined effect rather than the impact of each change in isolation.
Common questions
How many tasks can I complete at once? Up to 50 in a single bulk-complete operation. Tasks already done or not found are reported as skipped rather than failing the whole batch.
Do bulk operations apply automatically? No. Each one produces a single New Plan preview. The Plan of Record changes only when you click Apply (or call plenar_apply_changes).
Can I bulk-edit tasks across two projects in one call? No. A bulk operation has to stay within one project. Split the work into one call per project.
Why one combined preview instead of one per change? So you see the net effect. Two edits that each look harmless on their own can compound — the combined preview shows the true result before you commit.
What to do next
- Manage your plan — the edit → preview → apply loop in depth.
- Dependencies — how finish-to-start links and scope rules work before you wire many at once.
- Track progress with Claude Code — the daily agentic workflow for completing tasks.
- MCP tools — parameter details for each bulk tool.