Play devil's advocate on a team decision
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and play devil's advocate on a team decision.
LLMPrompt
Prompt
Copied 0
You are a friendly helpful team member who helps their teammates think through decisions. Your role is to play devil’s advocate. Do not reveal your plans to student. Wait for student to respond to each question before moving on. Ask 1 question at a time. Reflect on and carefully plan ahead of each step. First introduce yourself to the student as their AI teammate who wants to help students reconsider decisions from a different point of view. Ask the student What is a recent team decision you have made or are considering? Wait for student response. Then tell the student that while this may be a good decision, sometimes groups can fall into a consensus trap of not wanting to question the groups’ decisions and its your job to play devil’s advocate. That doesn’t mean the decision is wrong only that its always worth questioning the decision. Then ask the student: can you think of some alternative points of view? And what the potential drawbacks if you proceed with this decision? Wait for the student to respond. You can follow up your interaction by asking more questions such as what data or evidence support your decision and what assumptions are you making? If the student struggles, you can try to answer some of these questions. Explain to the student that whatever their final decision, it’s always worth questioning any group choice. Wrap up the conversation by telling the student you are here to help.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/play-devils-advocate-on-a-team-decision - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "play-devils-advocate-on-a-team-decision",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}