# Flare use cases

> Each page covers one job Flare does, with a worked example, the exact MCP tools, and what it replaces.

- [Turn meeting notes into tickets automatically](https://flares.in/use-cases/meeting-notes-to-tickets) — A call ends. Decisions and bugs are staged on the project with the quote.
- [Give Claude Code your project’s decisions](https://flares.in/use-cases/decision-log-for-coding-agents) — Decisions, and what was rejected, read by every agent before it codes.
- [Project management your AI agents can use over MCP](https://flares.in/use-cases/mcp-project-management) — Your agent lists its stories, reads the criteria, and reports progress back.
- [Turn a PRD into epics, stories, and acceptance criteria](https://flares.in/use-cases/prd-to-user-stories) — A PRD becomes epics, stories, and acceptance criteria, in shipping order.
- [An AI support agent that files bugs with evidence](https://flares.in/use-cases/ai-customer-support-that-files-bugs) — A customer reports a bug. The ticket arrives with the screen and the console.
- [Find the gaps in your help center from real questions](https://flares.in/use-cases/support-knowledge-gaps) — What customers couldn’t find, counted, with an article drafted for the top gap.
- [Send production errors from the browser to your IDE](https://flares.in/use-cases/production-errors-to-ide) — Fourteen crashes become one incident, handed to your IDE with the evidence.
- [Tell the customer when their bug is fixed](https://flares.in/use-cases/close-the-loop-with-customers) — Resolve with a public note and the person who reported it is told.
- [From client discovery call to delivery plan](https://flares.in/use-cases/agency-discovery-to-delivery) — The discovery call becomes a plan. Later calls become change requests.
- [Replace the standup with a drafted update](https://flares.in/use-cases/async-standups) — The week’s movement drafts the update. The meeting covers only blockers.
- [Hand work off between Claude Code and Cursor](https://flares.in/use-cases/multi-agent-handoff) — A session ends with a note. The next agent, in any tool, starts from it.
- [Audit what your AI agents changed](https://flares.in/use-cases/agent-audit-trail) — Every agent write has a name, a token, and a scope on it.
- [Hand software over without losing the why](https://flares.in/use-cases/software-handover) — Hand software over without losing the reasons it was built that way.
- [Review code against the story, not just the diff](https://flares.in/use-cases/intent-aware-code-review) — The reviewer reads the story and decisions first, then the diff.
- [Onboard a new engineer or agent in an afternoon](https://flares.in/use-cases/onboard-engineers-and-agents) — Explain a module with its decisions, open bugs, and incidents attached.
- [Move from Excel or WhatsApp to an app without losing users](https://flares.in/use-cases/replace-excel-with-an-app) — Keep people on the new app by fixing what sent them back to the sheet.
- [Launch with support and bug capture from day one](https://flares.in/use-cases/launch-support-for-new-apps) — A support desk and bug capture for your first real users, on day one.

Flare (flares.in) is the context system for teams that build with AI agents.

---
Site map: https://flares.in/sitemap.xml · Machine-readable summary: https://flares.in/llms.txt · Start: https://flares.in/login?mode=signup