The team for this work
Which agents to hire, which Marketplace templates start them, and the order they need each other in.
✦ Guide · Intermediate
Agents for product and design
Feedback analysis, research, presentation and code triage as a team of agents around a product decision.
Start guideYOUR OUTCOME
You will run a product pod that turns feedback into themes, researches the options, presents the decision and triages the issues that follow.
Themes from feedback before any decision Research with citations, then the deck Triage issues on a routine with evidence
4 min
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
The group and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
What each lesson covers
The guide, lesson by lesson.
The team for this work
Which agents to hire, which Marketplace templates start them, and the order they need each other in.
Start from the work, not the tool: Feedback analysis, research, presentation and code triage as a team of agents around a product decision. The team is Fay · Feedback (Customer feedback analysis), Ren · Research (Research assistant), Noor · Decks (Presentation building), Kit · Triage (Code review and issue triage). Each starts from a Marketplace template, imported as your own copy, renamed and re-goaled on the setup card; nothing personal and no creator credentials come with a template.
Practice. Open Marketplace, Agent templates, and read the Instructions and Integrations of each template on this list before you import anything. Note which sources each one will ask you for.
Marketplace → Agent templates → open Customer feedback analysis. Read Instructions, then Integrations.
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
Import agent creates your copy and opens the setup card. Rename it, replace the goal with yours, and choose When to work. Feedback analysis is the first hire: the themes it finds decide what the researcher and the deck are about.
Practice. Import Customer feedback analysis, rename it Fay · Feedback, and paste your goal on the setup card. Choose Now, once, and Continue. Check its first deliverable in Doc Manager before the next hire.
Name: Fay · Feedback. Goal: Read the attached support export for August and cluster the feedback into themes: for each theme, how many tickets, two verbatim quotes, and the severity. Deliver a document with a table sorted by count and a one-paragraph recommendation. Use only the export; never invent a quote. When to work: Now, once.
The group and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
Create group chat, name it Product pod, add Fay · Feedback, and post what the team is for. Then hire the second wave with goals that start by reading the first wave's document. @Name directs one member, @everyone the room, Work ↗ opens a member's session. The researcher checks how others solved the top theme; the deck builder turns both into the decision for the room.
Practice. Create Product pod, add each hire as it joins, and ask every member to post what it made and the one thing it would flag.
@everyone Welcome to the product pod. Fay's August themes are in the workspace. Ren: research how three comparable products handle the top theme, with sources. Noor: build an eight-slide decision deck from Fay's report and Ren's research. Post what you made and what you'd flag.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
Issue triage repeats daily; a routine reads the new issues and labels them with evidence. Every run is a session under Finished today. Close each cycle with a status round, "@everyone one line each", and a grade against the acceptance checks each agent wrote first.
Practice. Create the routine, use Run now to get today's first report, then run one status round in Product pod.
New routine. Name: Issue triage. Instructions: Read the new issues in the attached repository since the last run, label each with area and severity, link the file the stack trace points at, and list any duplicate of an open issue. Say nothing if there are no new issues. Frequency: Every day, 08:30.
Keep going
Make the learning stick
Start with one real piece of work.
Open Oppermind beside the lesson, apply each step, and leave with something you can use.