Summary
The plan lives outside the context window, so the next step survives a conversation that does not.
get_current_task_details is what the rest is arranged around: it returns the first uncompleted item together with the context shared by every item, which is what lets a fresh session pick the work up without re-reading a whole thread. Each item carries a detailed description and its own context and plan, so a checklist entry is a briefing rather than a line of text. Only one task is held at a time, and clearing it is how the next one begins.
What it is
A single-task workspace holding a description, context that applies to every item, an ordered checklist, notes, resources and metadata.
What you get
- A task initialised with a description, context for all its items, and an optional starting checklist.
- Checklist items added at a position, updated, marked done or undone, removed and reordered, each carrying its own detailed description and its own context and plan.
- Notes, and resources recorded with a name, URL and description.
- Metadata: priority, tags and an estimated completion time.
- A checklist summary with completion status, and the current item — the first uncompleted one — returned with its full context.
- The whole task cleared when the work is finished.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @landicefu/divide-and-conquer-mcp-server