use-cases/feedback-synthesis.md +150 −0 added
1# Turn feedback into actions | Codex use cases
2
3Codex use cases
4
5
6
7
8
9Codex use case
10
11# Turn feedback into actions
12
13Synthesize feedback from multiple sources into a reviewable artifact.
14
15Difficulty **Easy**
16
17Time horizon **30m**
18
19Connect Codex to multiple data sources such as Slack, GitHub, Linear, or Google Drive to group feedback into a reviewable Google Sheet, Google Doc, Slack update, or recurring feedback check.
20
21## Best for
22
23- Analyzing feedback from Slack channels, issue threads, survey exports, support-ticket CSVs, or research notes.
24 - Teams that need to turn feedback into actionable insights.
25
26# Contents
27
28[← All use cases](https://developers.openai.com/codex/use-cases)
29
30Copy page [Export as PDF](https://developers.openai.com/codex/use-cases/feedback-synthesis/?export=pdf)
31
32Connect Codex to multiple data sources such as Slack, GitHub, Linear, or Google Drive to group feedback into a reviewable Google Sheet, Google Doc, Slack update, or recurring feedback check.
33
34Easy
35
3630m
37
38Related links
39
40[Codex plugins](https://developers.openai.com/codex/plugins) [Codex automations](https://developers.openai.com/codex/app/automations) [Agent skills](https://developers.openai.com/codex/skills)
41
42## Best for
43
44- Analyzing feedback from Slack channels, issue threads, survey exports, support-ticket CSVs, or research notes.
45 - Teams that need to turn feedback into actionable insights.
46
47## Skills & Plugins
48
49- [Slack](https://github.com/openai/plugins/tree/main/plugins/slack)
50
51 Read approved feedback channels or thread links.
52- [GitHub](https://github.com/openai/plugins/tree/main/plugins/github)
53
54 Read issues, PR comments, and discussion threads.
55- [Linear](https://github.com/openai/plugins/tree/main/plugins/linear)
56
57 Read bug or feature queues.
58- [Google Drive](https://github.com/openai/plugins/tree/main/plugins/google-drive)
59
60 Read feedback docs, exports, and folders, then create a Google Doc or Sheet.
61- [Google Sheets](https://developers.openai.com/codex/plugins)
62
63 Create a feedback sheet the team can sort, comment on, and update.
64
65| Skill | Why use it |
66| --- | --- |
67| [Slack](https://github.com/openai/plugins/tree/main/plugins/slack) | Read approved feedback channels or thread links. |
68| [GitHub](https://github.com/openai/plugins/tree/main/plugins/github) | Read issues, PR comments, and discussion threads. |
69| [Linear](https://github.com/openai/plugins/tree/main/plugins/linear) | Read bug or feature queues. |
70| [Google Drive](https://github.com/openai/plugins/tree/main/plugins/google-drive) | Read feedback docs, exports, and folders, then create a Google Doc or Sheet. |
71| [Google Sheets](https://developers.openai.com/codex/plugins) | Create a feedback sheet the team can sort, comment on, and update. |
72
73## Starter prompt
74
75Can you synthesize the beta feedback on [feature or product area] into a @google-sheets review sheet?
76 Use these sources:
77 - @slack [feedback channel or thread links]
78 - @github [issue search or issue links]
79 - @google-drive [survey export, notes doc, or Drive folder]
80In the sheet, group repeated feedback, include source links or IDs, mark confidence, and call out which items need product or engineering follow-up.
81Keep names and private quotes out of the visible summary unless I approve them. Do not post, send, create issues, or assign owners.
82
83[Open in the Codex app](codex://new?prompt=Can+you+synthesize+the+beta+feedback+on+%5Bfeature+or+product+area%5D+into+a+%40google-sheets+review+sheet%3F%0A%0AUse+these+sources%3A%0A-+%40slack+%5Bfeedback+channel+or+thread+links%5D%0A-+%40github+%5Bissue+search+or+issue+links%5D%0A-+%40google-drive+%5Bsurvey+export%2C+notes+doc%2C+or+Drive+folder%5D%0A%0AIn+the+sheet%2C+group+repeated+feedback%2C+include+source+links+or+IDs%2C+mark+confidence%2C+and+call+out+which+items+need+product+or+engineering+follow-up.%0A%0AKeep+names+and+private+quotes+out+of+the+visible+summary+unless+I+approve+them.+Do+not+post%2C+send%2C+create+issues%2C+or+assign+owners. "Open in the Codex app")
84
85Can you synthesize the beta feedback on [feature or product area] into a @google-sheets review sheet?
86 Use these sources:
87 - @slack [feedback channel or thread links]
88 - @github [issue search or issue links]
89 - @google-drive [survey export, notes doc, or Drive folder]
90In the sheet, group repeated feedback, include source links or IDs, mark confidence, and call out which items need product or engineering follow-up.
91Keep names and private quotes out of the visible summary unless I approve them. Do not post, send, create issues, or assign owners.
92
93When feedback is spread across a Slack channel, a survey export, and a few issue threads, Codex can pull it together into a Google Sheet or Doc that the team can review.
94
95[
96Your browser does not support the video tag.
97](https://cdn.openai.com/codex/docs/developers-website/use-cases/feedback-synthesis-into-gsheets.mp4)
98
99## Create the first version
100
1011. Give Codex the feedback sources and one sentence of context.
1022. Ask for a Google Sheet or Doc with themes, evidence links, questions, and follow-ups.
1033. Use the same thread to turn the reviewed sheet into a Slack update or issue draft.
1044. Pin the thread and add an automation if the feedback source keeps changing.
105
106Use the starter prompt on this page for the first pass. The sources can be plugin links, attached files, or files in Google Drive.
107
108## Turn the sheet into the next draft
109
110Once the sheet exists, use the same thread to make it useful for the next person. Ask Codex to add a column, split a theme, draft a Slack update, or turn a reviewed theme into an issue draft.
111
112Using the reviewed feedback sheet, draft a short Slack update.
113Audience: [team or channel]
114Include:
115- what changed
116- the top feedback themes
117- link to the sheet
118- the decision or follow-up needed
119Draft only. Do not post it.
120
121## Keep a feedback channel current
122
123For a Slack channel or issue queue that keeps getting new reports, pin the thread and ask Codex to check it on a schedule.
124
125Check this feedback source every [weekday morning / Monday / release day].
126Source: [Slack channel, GitHub search, Linear view, or Google Drive folder]
127Use this reviewed Sheet or Doc as the running summary: [link]
128Only update me when there is a new theme, stronger evidence for an existing theme, or a source you cannot read. Keep the Sheet or Doc current. Do not post, send, create issues, or assign owners.
129
130## Related use cases
131
132[
133
134### Coordinate new-hire onboarding
135
136Use Codex to gather approved new-hire context, stage tracker updates, draft team-by-team...
137
138Integrations Data](https://developers.openai.com/codex/use-cases/new-hire-onboarding)[
139
140### Query tabular data
141
142Use Codex with a CSV, spreadsheet, dashboard export, Google Sheet, or local data file to...
143
144Data Knowledge Work](https://developers.openai.com/codex/use-cases/analyze-data-export)[
145
146### Clean and prepare messy data
147
148Drag in or mention a messy CSV or spreadsheet, describe the problems you see, and ask Codex...
149
150Data Knowledge Work](https://developers.openai.com/codex/use-cases/clean-messy-data)