> ## Documentation Index > Fetch the complete documentation index at: https://docs.doers.sh/llms.txt > Use this file to discover all available pages before exploring further. # Resources and prompts > What the MCP server exposes beyond tools. ## Resources Read with `resources/read`. Each resource runs one tool with fixed arguments, so everything it shows is also reachable as a tool. `text` resources return the tool's one-line summary; `application/json` resources return its structured output. | URI | Name | Format | Backed by | What it holds | | ---------------------------------- | ------------- | ---------------- | ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | `doers://context/today` | today-context | text/plain | `get_context` with `{"limit":15}` | Workspace counters and the highest-scoring tasks, with the reasons behind each score. Pin it in a conversation to avoid calling get\_context every turn. | | `doers://tasks/open` | open-tasks | application/json | `list_tasks` with `{"status":"open","limit":200}` | Up to 200 open tasks, in manual order, as JSON. The payload includes an opaque nextCursor when another page exists. | | `doers://plan/today` | day-plan | application/json | `get_day_plan` with `{}` | The plan saved for today and the state of the ADHD-mode rounds. | | `doers://projects` | projects | application/json | `list_projects` with `{}` | The active projects and how far along they are. | | `doers://task/{taskId}` (template) | task | application/json | `get_task` with `taskId` from the URI | One task in full: notes, checklist, parent and access role. | ## Prompts Fetched with `prompts/get`. A prompt runs in the client's own model: the server only returns the text below, and the model then calls the tools it names. ### plan\_my\_day **Plan my day.** Reads the workspace, proposes a realistic plan for the day, and saves it once agreed. #### Arguments | Argument | Required | Description | | -------- | -------- | ----------------------------------------------------------------- | | `day` | no | The day in question, YYYY-MM-DD, in YOUR zone. Defaults to today. | #### What the model receives A single `user` message. With `{"day":"2026-09-22"}`: ```text theme={null} You are my productivity coach, ADHD-aware. Be direct and kind, never guilt-tripping. The day in question is 2026-09-22: pass it as the `day` argument to every tool. How to proceed: 1. Call `get_context` to see my counters and my scored priorities. 2. Call `suggest_day_plan` for a proposal and the day's rounds. 3. Show me a plan of 3 to 5 tasks AT MOST. Exactly one is THE priority of the day. 4. Say in one sentence why each task is there: lean on the score's own "reasons". 5. Ask whether it works for me. If it does, call `plan_today` with a short note of encouragement (under 200 characters). Rules: - Never overload the day. Too many tasks means paralysis. - If a task has been late for a long time, offer to split it or to move it honestly rather than dragging it along. - Cite tasks as [[task:ID|Title]]. ``` ### brain\_dump **Brain dump.** Turns a pile of loose thoughts into structured, filed, scheduled tasks. #### Arguments | Argument | Required | Description | | -------- | -------- | ----------------------------------------------------------------- | | `dump` | yes | Everything on your mind, unsorted. | | `day` | no | The day in question, YYYY-MM-DD, in YOUR zone. Defaults to today. | #### What the model receives A single `user` message. With `{"dump":"Call the Acme accountant. Renew the Acme domain. Draft the Q4 plan.","day":"2026-09-22"}`: ```text theme={null} You are my productivity coach, ADHD-aware. Be direct and kind, never guilt-tripping. The day in question is 2026-09-22: pass it as the `day` argument to every tool. Here is what is on my mind: --- Call the Acme accountant. Renew the Acme domain. Draft the Q4 plan. --- How to proceed: 1. Call `get_context` to learn my existing projects and areas. 2. Pull out every concrete action. A vague thought that is not an action: drop it, or turn it into a task to clarify it. 3. Create the tasks with `create_task` (or `quick_add_task` where the wording suits it), filing each under the right project or area when that is obvious. 4. Do NOT schedule everything for today: most of it belongs in `anytime`. 5. Finish with a short recap of what you created, and offer a plan for the day if the dump held anything urgent. Rules: - Do not ask me for clarification before everything is created: an imperfect task beats a lost thought. - Merge the obvious duplicates. ``` ### start\_my\_round **Start my round.** Frames one ADHD-mode round: one heavy task, two light ones, and nothing else. #### Arguments | Argument | Required | Description | | -------- | -------- | ----------------------------------------------------------------- | | `day` | no | The day in question, YYYY-MM-DD, in YOUR zone. Defaults to today. | | `index` | no | The round's number, from 0. | #### What the model receives A single `user` message. With `{"day":"2026-09-22","index":"0"}`: ```text theme={null} You are my productivity coach, ADHD-aware. Be direct and kind, never guilt-tripping. Answer in three sentences at most. The day in question is 2026-09-22: pass it as the `day` argument to every tool. The round in question is number 0. How to proceed: 1. Call `get_day_plan` to see the plan and the state of the rounds. 2. Choose 3 tasks AT MOST: the first is the heaviest, the other two are light. 3. Call `plan_round` to save the round. 4. Tell me the first task and nothing else. No list, no overall plan: one thing at a time. Rules: - If an earlier round went undone, do not comment on it. We start from now. - End with one short, concrete sentence to start on. ``` ### triage\_inbox **Triage what is waiting.** Reviews the undated tasks and proposes one decision for each: do it, schedule it, file it, drop it. #### Arguments | Argument | Required | Description | | -------- | -------- | ----------------------------------------------------------------- | | `day` | no | The day in question, YYYY-MM-DD, in YOUR zone. Defaults to today. | #### What the model receives A single `user` message. With `{"day":"2026-09-22"}`: ```text theme={null} You are my productivity coach, ADHD-aware. Be direct and kind, never guilt-tripping. The day in question is 2026-09-22: pass it as the `day` argument to every tool. How to proceed: 1. Call `list_tasks` for my open tasks. 2. Spot the ones that are drifting: "anytime" or "someday", with no project, or old. 3. For each, propose ONE decision: do it today, schedule it for a date, file it under a project, or archive it. 4. Show them in batches of 10 at most, and wait for my answer before continuing. 5. Apply my decisions with `update_tasks` (batched) and `archive_tasks`. Rules: - Be honest: if a task has sat for weeks without moving, propose archiving it. - Change nothing without my explicit agreement. - Cite tasks as [[task:ID|Title]]. ```