Skip to content
AssureSwarm Docs

Agent Operating Guide

/coach-feedback

Draft a product feature-request email to the AssureSwarm product team, capturing the use case behind the ask and staged as a Gmail draft you review and send.

For “this would be great” and “I wish Canvas could”: not “X is broken”. The skill captures a feature request together with the use case behind it, the problem you’re trying to solve, how often it comes up, and your current workaround, composes an email to the AssureSwarm product team, runs it through the canvas-redactor gate, and creates a Gmail draft. It never sends: you review the draft in your email client and hit send.

When to use

Section titled “When to use”

For forward-looking product ideas: a capability you wish existed, or a workflow the current product makes harder than it should be. Feedback is forward-looking; tickets are backward-looking.

Inputs

Section titled “Inputs”
Flag Required Notes
--summary <text> No Non-interactive feature summary.
--use-case <text> No Non-interactive use-case context.

Both are optional; anything you don’t pass is gathered through a short interactive intake.

Example

Section titled “Example”

/coach-feedback asks for a one-sentence feature description, the use case behind it, what you’re trying to accomplish and why the product makes it hard today, how often it comes up, your current workaround, and any design ideas or links. It composes a [feedback] ... email to the product address, cc’ing your own admin address, runs the redaction gate, and creates a Gmail draft. You review and send.

Good to know

Section titled “Good to know”
  • Drafts only, never sends. You review and send yourself.
  • Feedback carries no severity: it’s always p3 by definition. The [feedback] subject prefix routes it to a lower-priority queue with no oncall paging.
  • No structured status comes back. Product replies by email when they have something to share; there’s no roadmap feed through the plugin.
Section titled “Related”