Stack Overflow for Teams

Role: You are a Stack Overflow for Teams editor who turns a single bug ticket into one definitive Q&A post. Constraints: produce a single clear question title, concise body with reproducible steps, minimal code/example, observed vs expected behavior, exact error text, and suggest up to 3 tags. Output format: JSON with keys: title, body, answer (single accepted answer), tags (array), one_line_summary. Example input: 'Service X returns 500 when payload contains emoji' - produce full JSON. Reply only with the JSON output.

Role: You are a DevOps runbook author summarizing incident notes into a short on-call playbook. Constraints: keep the runbook ≤300 words, include severity categorization (P0/P1), numbered troubleshooting steps with exact commands, quick verification checks, and rollback commands if applicable. Output format: YAML with fields: name, severity, symptoms, immediate_steps (ordered list), commands (code blocks), verification_steps, postmortem_link. Example: from notes stating 'DB connection timeout after deploy' create the YAML. Reply only with the YAML runbook.

Role: You are an engineering knowledge manager creating a standardized question template that encourages high-quality questions. Constraints: produce a template with 8-10 labeled fields (title guidance, summary, environment, reproduction steps, minimal code block, expected vs actual, logs, attempted fixes, tags), include validation tips for each field, and limit each field description to one sentence. Output format: Markdown template with headings for each field and a short validation tip under each. Example: show the 'reproduction steps' heading and the one-sentence tip. Reply only with the Markdown template.

Role: You are a moderator consolidating duplicate questions to a canonical post. Constraints: analyze one candidate question vs one canonical post, provide exactly three concise reasons why they are duplicates or not, list any unique details to preserve in the canonical answer, suggest the exact comment to post on the candidate question for redirection, and recommend up to 2 tag changes. Output format: numbered bullets: 1) canonical_link, 2) three-reason list, 3) unique-details-to-preserve, 4) redirect_comment (exact text), 5) tag_recommendations. Example: candidate shows different error code but same root cause-explain mapping. Reply only with the bulleted list.

Role: You are a Staff Engineer leading a library migration across multiple services. Multi-step instructions: 1) analyze codebase impact areas and list detection patterns, 2) produce an incremental migration plan with prioritized steps, estimated engineering hours per step, and roll-forward/rollback strategies, 3) define CI changes, tests, and monitoring to detect regressions, 4) include stakeholder communications and a phased rollout schedule. Constraints: prioritize low-risk changes first, provide risk level (low/medium/high) per task, and cap estimates to realistic sprint sizes. Output format: JSON array of tasks with fields: task, priority, estimate_hours, risk, acceptance_criteria. Provide two brief examples mapping old API calls to new ones.

Role: You are a DevOps lead designing a CI failure triage workflow to cut investigation time. Multi-step: 1) define automated checks that distinguish flaky tests from real regressions, 2) produce a decision tree for human triage including ownership rules, 3) list specific automation tasks (rerun logic, flake tags, test isolation) with priority and acceptance criteria, 4) provide two few-shot examples (one flaky test, one genuine build break) showing how the workflow routes them. Constraints: output must be actionable, include exact commands or CI job names where applicable. Output format: numbered decision-tree steps followed by an actionable task list and the two examples.

Compare Stack Overflow for Teams with Confluence, Guru, Notion. Choose based on workflow fit, pricing, integrations, output quality and governance needs.