Shape the graph
Put signals and features on the roadmap, file bugs, track your requests, and see what's coming next — without leaving Claude.
The Signal Graph grows in the direction its users pull it — and /watt:help is how you pull. Put new signals and features on the roadmap, file bugs, get a human when you need one, and track all of it from the same chat you work in.
Start
A few asks that land here:
/watt:help how can I improve my audience?/watt:help what am I allowed to build with Watt?/watt:help I wish there was more granular data on LinkedIn engagement./watt:help what signals are coming to the graph next?/watt:help what's going on with my ticket 212?
One nuance: wondering whether the graph holds something today is Explore the graph's job — it searches the graph live. /watt:help is for using Watt, and for changing what Watt becomes.
Why shaping lives inside /watt:help
Shaping the graph lives underneath /watt:help on purpose: the conversation that helps you is the same one that shapes the graph. Bring a problem and Watt works it with you before suggesting the graph expand — and that pays you twice. With hundreds of thousands of signals in play, most issues are how-to-use-them issues, and a direct answer or a sharper approach resolves them on the spot. When something genuinely is missing, having worked the problem first means your request lands with a proper delta: what you wanted, what the graph holds today, and exactly where it falls short. That delta is what the team builds from.
The same goes for plain questions — "what can Watt do", "how do I improve my audience", "what do I need to do to stay compliant" — you get a direct answer and the command that does the job, honest limits included.
Shape the graph
The graph's coverage is a living decision, and your requests drive it:
| You want | Say |
|---|---|
| A signal the graph lacks | "I wish there was more granular data on LinkedIn engagement." |
| A capability Watt lacks | "I wish Watt could push audiences straight to my CDP." |
| Something's broken | "This audience is returning wrong sizes." |
| A human on it | "Get me a person." |
Nothing files without your go-ahead. Watt drafts the request from your conversation — for a bug, the symptom and steps from the session; for a signal request, the delta it just helped you define — and shows you the exact text before anything is sent. You file it, edit it, or drop it. A filed request comes back with an ID and a status.
Then track it — and watch the roadmap:
- "What's going on with my ticket 212?" — its status, plus any updates from the team.
- "What have I filed?" — everything you've sent in, with statuses.
- "What's coming next?" — the public roadmap: the signals and capabilities on their way to the graph.