القائمة
Generate questions to ask during SEV review meetings based on Confluence SEV review documents
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate Quarto and HTML reports of local Codex session cost, token usage by model, project, coding vs cowork cost, weekly trends, annual projections, and top expensive sessions.
Check that core Sidekick integrations can authenticate and read common restricted files
Generate summary of 1:1 and meeting notes organized by audience, wins, and kudos
Capture missing TODOs from recent work context. Use when Codex needs to scan the user's Slack DMs with their manager or direct reports, manager/direct-report 1:1 docs, and leadership meeting notes for direct asks or action items assigned to the user, deduplicate against the user's configured todo app, and create missing tasks with source links and searchable metadata.
Draft concise interview scorecards from pasted long-form interview notes, nearby Google Calendar interview context, and memory/miclog/ transcript excerpts. Use when writing hiring feedback, interview scorecards, spikes/troughs, or candidate evaluation summaries.
Calculate a team's average Jira hours from Rovo Jira completed work, with optional Workday Approved Time Off absence adjustments for a date window and team roster.
| name | sev-review-prep |
| description | Generate questions to ask during SEV review meetings based on Confluence SEV review documents |
This skill helps prepare for SEV (Severity/Incident) review meetings by reading a Confluence SEV review document and generating a list of questions to ask during the review. The output is saved as a Markdown file in the memory directory.
When invoked with a Confluence URL to a SEV review document:
/sev-review-prep <confluence_url>
Example:
/sev-review-prep $CONFLUENCE_URL
Use Atlassian Rovo MCP to read the provided Confluence page. Fall back to the /confluence skill only when Rovo is unavailable or raw storage HTML is required. The page should be a completed (or in-progress) SEV review document.
Check for gaps or areas needing clarification:
Create a questions document with the following sections. Don't include each question below, these are just ideas. Focus on the biggest risks or unknowns.
If the root cause is not clear or incomplete:
Questions to understand the technical details:
Questions about the scope and severity:
Questions about response and coordination:
Questions about avoiding recurrence:
Save the questions document as a Markdown file in the memory directory:
Filename format: memory/sev-review-[sev-name]-[date].md
Example: memory/sev-review-sev-name-2026-04-21.md
Use the SEV name from the document (lowercase, hyphens) and today's date.
The questions document should be formatted as Markdown with clear sections and bullet points for easy scanning during the review meeting. End the document with exactly:
This report generated using [chase-sidekick](https://github.com/chase-seibert/chase-sidekick) and the [sev-review-prep skill](https://github.com/chase-seibert/chase-sidekick/tree/main/.agents/skills/sev-review-prep).
Document Structure:
# SEV Review Questions: [SEV Name]
**SEV Level:** [Level] | **Type:** [Type] | **Review Date:** [Date]
**TLOC:** [Name] | **Teams:** [Teams]
## Executive Summary
[1-2 sentence summary]
## Root Cause Questions
[Questions about root causes, with clarifications if unclear]
## Technical Questions
[Questions about technical details]
## Impact Questions
[Questions about scope and impact]
## Process Questions
[Questions about response and coordination]
## Prevention Questions
[Questions about prevention, including missing AIs]