Capabilities / Plans
Plans
A plan is Sands' core artifact: a short, structured document drafted from your brief, edited by you and Sands together, and sent to Jira, Linear or Asana when it is ready.
Asking for a plan
Ask for a plan, a spec, a sprint plan or a project brief. Sands drafts one even from a short request; anything it does not know becomes a labeled assumption or an open question inside the plan instead of a round of questions first. It asks before drafting only when it cannot tell what the work is.
Try asking
Write a project plan for a marketing website for a roofing company, done in 6 weeks
Try asking
Plan a sprint Oct 5 to Oct 16 for the SMS back-in-stock feature. Team: Maya (designer), Ana (engineer), June (QA). Legal must sign off on the opt-in copy by Oct 12.
You do not need to choose a project tool first. The plan stays in Sands until you send it, and you pick the tool then.
What's in a plan
Plans are kept short so they read in a few minutes. A typical plan has:
| Part | What it holds |
|---|---|
| Title and dates | A plain name for the work, with the start and end dates under it. |
| Goal | One or two sentences on what the work achieves. |
| Capacity | When you name the team: each person, their share of time, days out, and the hours available. |
| Workstreams and tickets | One ticket table: priority, ticket, description, acceptance criteria, owner, estimate, due date, workstream and dependencies. |
| Risks | What could go wrong and how to handle it, with an owner. |
| Key dates | Milestones, sign-offs and the dates the brief fixed. |
| Open questions | What Sands could not know from the brief, for you to answer. |
| Out of scope | What the work leaves out, when your request says so. |
Sprint plans also get a definition of done. Ask for other sections by name, like a rollout plan or a budget, and Sands adds them.
One living plan
A conversation works on one plan at a time. Every change, yours in the document or Sands' from the chat, updates the same plan. There are no versions to manage: the plan is always the current one, and Undo reverses Sands' last change.
- Sands writes what your brief states exactly: names, dates and sign-off deadlines are kept as you gave them.
- Owners only come from people you named. Sands never invents a teammate.
- Anything Sands assumed is marked as a suggestion until you confirm it.
Ask what it would look like in your tool
“Is this ready for Linear?” or “How would this look in Jira?” gets an answer from the saved plan: what would be created and anything blocking it. Nothing is sent.
More on plans
How a plan is drafted
What Sands reads from your brief, and how it sets owners, dates and capacity.
Editing the document
Type anywhere, insert blocks with /, and work the ticket table.
Changing it in chat
Assign, reschedule and rewrite by asking, and watch each change land.
Sending and exporting
Send to Jira, Linear or Asana, or export to Word, PDF, Markdown or CSV.