Every piece of work is a run you can watch.
Sands does project work the way a careful operator would: read first, plan second, write last, and show the evidence at every step. This page is how that actually looks.
The run is the interface
Each step announces itself, works in the open, and settles with its evidence: the projects it checked, the numbers it found, the issue it created. You never wonder what happened; you watched it happen.
It reads your boards before it plans
Plans built in a vacuum die on contact with the backlog. Sands checks project state first: open load, recent completions, blockers. What it finds shapes the plan, and the finding is quoted in the trace, not asserted.
Let me check the existing boards to see what's already in play.
KSP already exists as an active project, so the About Page work slots directly into it.
Artifacts, not answers
A run ends in something you can hold: a spec with workstreams and deliverables, stored and versioned, ready to refine in place or send to your project tool. Chat scrollback is not a deliverable.
KSP About Page
Spec · design- Content & Visual Design
- Page Build & Integration
- QA & Launch
18 deliverables across three workstreams, stored as a queryable artifact and ready to send to the project tool.
You decide when Sands asks first
Writes follow your approval mode. By default, ordinary updates run and Sands pauses the risky ones, such as deletes, new projects, and sending a plan to your tool, to show exactly what it intends before it acts. Switch to manual approval and it asks before every change. After any write it reads the result back and reports what actually landed, never what it hoped happened.
- Preview before risky changes, or before every change in manual mode
- Verification read-back after every write
- Deep link to each created artifact
- Idempotent injection: re-running a send never duplicates work