# Prompts

> Two packaged workflows — daily_standup and overdue_report — that surface as slash commands in supported clients.

> For the complete documentation index, see [llms.txt](https://helpdesk.orangescrum.com/llms.txt).

Source: https://helpdesk.orangescrum.com/guide/mcp/prompts

---
Alongside its tools, the server publishes **2 prompts**. In clients that support
MCP prompts these appear as slash commands; elsewhere you can invoke them by
name.

| Prompt | What it does |
| --- | --- |
| `daily_standup` | Assembles a standup summary — what moved, what is in flight, what is blocked |
| `overdue_report` | Finds work past its due date and groups it so you can act on it |

## Using them

In a client with slash-command support, type `/` and pick the prompt:

```
/daily_standup
```

Otherwise ask for it directly:

> Run the daily_standup prompt for the Website Redesign project.

Both prompts call the same [tools](https://helpdesk.orangescrum.com/guide/mcp/tools) your assistant already has,
so they respect your key's scopes — a read-only key runs both fine, since
neither writes.

## daily_standup

Pulls recent task activity and turns it into the three questions a standup
actually answers: what got done, what is being worked on, what is stuck.

Useful variations once the prompt has run:

- **Narrow it**: "Same thing, but only for the mobile team."

- **Reshape it**: "Rewrite that as bullet points I can paste into Slack."

- **Chase the blockers**: "For each blocked item, who is it waiting on?"

- **Compare**: "How does this compare with yesterday?"

## overdue_report

Finds everything past its due date. The follow-up is usually where the value is:

> Group those by assignee and tell me who has the worst backlog.

> For anything overdue by more than two weeks, draft a comment asking for a new
> estimate.

> **Drafting is not sending**
>
> Ask for drafts, review them, then approve. An assistant that decides on its own
> to comment on thirty tasks will do exactly that.

## Writing your own

Prompts are convenience wrappers, not a limit — anything you can describe, the
assistant can do with the underlying tools. Some that work well:

**Sprint hygiene check**

    "List tasks in the current sprint that have no assignee, no estimate, or no
    due date. Present as a table."

**Estimate versus actual**

    "For tasks closed in the last two weeks, compare estimated hours against
    logged time and flag anything more than 50% over."

**Handover note**

    "I'm away next week. Summarise my open tasks with current status and what
    the next action is for each."

**Backlog grooming**

    "Find tasks not updated in 60 days, and suggest which to close."

> **Tip**
>
> Save the ones you repeat as your client's own custom commands or project
> rules — that gets you the same convenience as the built-in prompts without
> waiting for the server to ship one.