Capabilities

Everything Sands can do today. You never pick a capability: describe what you want and Sands chooses. This page helps you know what to ask for.

At a glance

Capability	When to use it	What Sands does	Works with
Plans	You have a brief and need a plan someone can build from.	Drafts a plan with capacity, tickets, owners, dates, risks and open questions; you edit it and send it.	Any tool, or none
Health and retros	You need to know where a project stands or how a period went.	Reads the board live and answers with counts it computed.	Jira, Linear, Asana
Lists and lookups	You need a slice of the board or one ticket's story.	Searches by project, person, status or text; summarizes tickets and comments.	Jira, Linear, Asana
Hours reports	You bill or report on time.	Builds an hours table from worklogs that pastes as a real table.	Jira
Work in your tools	You want a ticket created, assigned, moved, edited or commented on.	Makes the change under your approval mode and reads it back.	Jira, Linear, Asana
Messaging	You want to catch up on a channel or tell the team something.	Reads channels and threads; drafts, sends and reacts.	Slack
Web research	The answer is outside your tools.	Searches the web and answers with sources.	The web
Files	The context is in a document.	Reads attached PDFs, Word, text and Markdown files, and images.	Uploads

Combining capabilities

One request can use several. Sands runs them in order and shows each as a step:

You ask	Sands uses
Read the #qa thread and create a ticket for each bug in WEB	Messaging, then Work in your tools
Research gift wrapping options, then plan a two-week build	Web research, then Plans
Post what finished in WEB this week to #website	Lists, then Messaging

Reference

Every action, tool by tool, is on each integration's page: Jira, Linear, Asana and Slack.

Something Sands cannot do yet?

Sands tells you when a request needs something it does not have, rather than guessing. Send the request with the feedback button so we can see what you needed.