> ## Documentation Index
> Fetch the complete documentation index at: https://docs.augmentcode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Signal → Ticket

> Turn feedback and incident findings into actionable follow-up.

## How it works

The ready-made **Feedback Triager** uses Slack: it responds to new top-level messages in a configured channel, investigates reports, checks for duplicates, and follows the thread. It creates tickets automatically when quality checks pass, or only on request, according to your settings. Otherwise, it answers or asks for missing evidence.

This diagram shows the **Slack setup**:

```mermaid theme={null}
flowchart TD
    feedback["👤 Human: post a top-level Slack report"] --> triager["🤖 Triager: investigate and check duplicates"]
    triager -->|Ready; automatic mode| ticket["Ticket"]
    triager -->|Ready; on-request mode| request["👤 Human: request ticket creation"]
    request --> ticket
    triager -->|No ticket needed or more evidence needed| answer["🤖 Triager: answer or request evidence"]
    classDef human fill:#fff7ed,stroke:#c2410c,color:#7c2d12;
    class feedback,request human;
```

**Incident Investigator** supports two Slack-based modes: **alert-thread mode** investigates new reports in configured alert channels, and **stationed-channel mode** follows an incident channel. In both modes, code fixes require explicit human approval before it launches PR Author; ticket creation is not automatic.

## Where you participate

* **Choose the filing policy.** Select automatic or on-request tickets, the tracker destination, and routing rules.
* **Provide context.** Supply expected behavior, a reproduction, and missing evidence. Review findings separately from hypotheses.
* **Authorize implementation.** Explicitly request a specific code fix or delegate a ticket. Ticket creation alone is not approval to implement. Investigation does not authorize production changes.

## Template Experts

* [Feedback Triager](/cosmos/experts-feedback-triager): investigates Slack feedback and files in Linear, Jira, or GitHub Issues under your policy; it does not edit code.
* [Incident Investigator](/cosmos/experts-incident-investigator): provides incident findings, recommended actions, and follow-up.
* [PR Author](/cosmos/experts-pr-author): implements a human-requested fix and carries it into review.
* [Ticket Manager](/cosmos/experts-ticket-manager): coordinates work explicitly delegated from the tracker.

## Set it up

For the ready-made Slack setup:

1. **Connect Slack, your tracker, and code host.** Make sure the Slack app can access the channel and the Experts can access your repository and evidence sources.
2. **Configure [Feedback Triager with Cosmos Advisor](/cosmos/advisor/overview).** Advisor configures the channel, ticket destination, filing policy, repository, and required Author worker. That worker still needs your request before starting a fix.
3. **Complete setup and approve activation.** Post a top-level report in the configured channel. Inspect the thread and [automation run history](/cosmos/manage-automations) for evidence, duplicate handling, and the next step.

Example Advisor prompt:

> Set up Feedback Triager for \[Slack channel] and \[ticket tracker]. Create tickets \[automatically / only when requested].

## Next step

Delegate ready work to [Ticket → PR](/cosmos/software-factory/ticket-to-pr), or take broader needs to [Requirements → Ticket](/cosmos/software-factory/requirements-to-ticket). Code fixes continue through [PR → Merge](/cosmos/software-factory/pr-to-merge).

## Further reading

* [Feedback triage with Cosmos](https://www.augmentcode.com/blog/feedback-triage-with-cosmos)
* [Scaling incident management with Cosmos](https://www.augmentcode.com/blog/scaling-incident-management-for-an-ai-native-organization-using-cosmos)
* [Why bug fixing is the least important part of a bug-fixing software factory](https://igoro.com/archive/bug-fixing-software-factory/)