brand_feedback
Send feedback on bugs, friction, feature requests, data quality, praise, or agent signals to the brandsystem team. Each submission gets a unique feedback ID.
Instructions
Report bugs, friction, feature ideas, data quality issues, praise, or structured agent signals to the brandsystem team. Use when a tool returns an error, extraction misses data, the workflow feels harder than it should, or something works particularly well. For structured agent telemetry, use category='agent_signal' with signal, tool_used, and signal_context fields — brand context is auto-populated from .brand/config. Stored locally in ~/.brandsystem/feedback/ for developer triage. Returns a feedback ID.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | Type of feedback. 'bug': something is broken. 'friction': it works but is harder than it should be. 'feature_request': a tool or capability that should exist. 'data_quality': extraction results seem wrong or incomplete. 'praise': something that works well and should be preserved. 'agent_signal': structured signal from an agent about tool usage (requires signal, tool_used, signal_context). | |
| signal | No | Signal type. Required when category is 'agent_signal'. 'positive': tool worked well, 'negative': tool failed or gave poor results, 'suggestion': improvement idea. | |
| tool_used | No | Which tool triggered this signal (e.g. 'brand_extract_web'). Required when category is 'agent_signal'. | |
| signal_context | No | What the agent was trying to do when this signal occurred. Required when category is 'agent_signal'. | |
| outcome | No | What happened as a result. Optional for positive signals. | |
| tool_name | No | Which brandsystem tool this feedback relates to (e.g. 'brand_extract_web', 'brand_compile'). Optional for general feedback. | |
| summary | Yes | One-line summary of the feedback. | |
| detail | No | Full context: what the agent was trying to do, what happened, what was expected, and any suggested fix. Use this for the complete feedback body — up to 10,000 characters. | |
| message | No | Alias for 'detail'. Full feedback body — what happened, what was expected, reproduction steps, suggested fix. Either 'message' or 'detail' can be used; if both provided, they are concatenated. | |
| severity | No | How much this impacts the agent's ability to serve the user. Defaults to 'suggestion'. | |
| context | No | Optional structured context about the session. |