メニュー
Use when evaluating a sprint before starting it. Use when user says 'sprint review', 'review sprint', 'evaluar sprint', 'sprint planning review', or mentions checking sprint readiness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Walks through full ops-suite setup: asks about all infrastructure components and writes config.yaml. Use when setting up ops-suite for the first time or when config.yaml is missing.
Run database migrations against remote environments. Use when asked about "migrations", "pending schema changes", "apply migrations", "migration status", "update schema". SKIP: querying data (use db-query); service health (use service-status).
Execute read-only queries against databases in any environment. Use when asked about "SQL", "check data", "count records", "find rows", "query database", "how many X?", "look up Y". SKIP: running migrations (use db-migrate); service health (use service-status).
Deploy a merged PR or commit to an environment. TRIGGER when: chained by workflow-deploy or another skill; user explicitly invokes /deploy with a PR number, commit SHA, or ref. SKIP: interactive guided deployments (use workflow-deploy).
Show deployment status across environments — current deployed commit, author, timestamp, PR, and drift between envs. Use when asked about "deploy status", "what is deployed", "what version is in prod", "is prod up to date", "show deployments", "current commit per env", "deployment overview", "env diff", "qué hay desplegado", "estado de los deploys". TRIGGER when: user asks "what's deployed in X", "deploy status", "is staging behind prod", "show me deploys", "last deploy of [service]", "deployment diff between envs", "qué versión hay en prod". SKIP: deploying new versions (use deploy or workflow-deploy); pod health (use service-status); logs (use service-logs).
Establish local connections to cluster services like databases, brokers, and APIs. Use when asked about "port-forward", "connect to database", "local connection", "tunnel", "forward port", "access service locally". TRIGGER when: user asks "port-forward to X", "connect to database locally", "tunnel to service", "forward port", "access service locally", "open local connection to X". SKIP: checking service health (use service-status); running queries (use db-query).
| name | sprint-review |
| description | Use when evaluating a sprint before starting it. Use when user says 'sprint review', 'review sprint', 'evaluar sprint', 'sprint planning review', or mentions checking sprint readiness. |
| argument-hint | [BOARD-ID or TICKET-KEYS or empty] |
| allowed-tools | ["Agent","AskUserQuestion","ToolSearch"] |
Read ${CLAUDE_PLUGIN_ROOT}/config.yaml.
If it does not exist, tell the user to copy config.example.yaml to config.yaml and fill in their values. Stop here.
Extract:
issue_tracker — determines which adapter to loadsprint_review.oversized_threshold — story points above this are flaggedsprint_review.systemic_threshold — percentage (0-1) above which findings become systemicsprint_review.bug_alert_threshold — percentage of bugs that triggers a warningsprint_review.vague_terms_es — list of vague terms in Spanishsprint_review.vague_terms_en — list of vague terms in Englishcommunication — tool and channels for sending reportsIssue tracker-specific config (e.g., jira.story_points_field, jira.default_project).
Read the adapter file at ${CLAUDE_PLUGIN_ROOT}/skills/sprint-review/adapters/{issue_tracker}.md.
If the adapter does not exist, tell the user that {issue_tracker} is not yet supported and stop.
All tool-specific calls come from the adapter. Do not invent tool calls.
IMPORTANT: Instructions are in English, but all output MUST be in Spanish.
Determine the source of tickets:
Store all tickets as {tickets}.
Remove from the analysis:
Store the filtered list as {active_tickets}. Report how many were filtered and why.
For each ticket in {active_tickets}, run these 8 checks. Use Agent to parallelize when possible.
Compare all ticket summaries and descriptions. Flag pairs with >70% similarity in title or identical acceptance criteria.
For each ticket, evaluate:
Score: 0 (no definition) to 3 (fully defined).
For each ticket, check if story points are set (using the adapter's story points field).
Scan title, description, and AC for terms from {config.sprint_review.vague_terms_es} and {config.sprint_review.vague_terms_en}.
Report each match with the exact term and location.
Check for:
[A-Z]+-\d+)Calculate:
{config.sprint_review.bug_alert_threshold} → flagFlag tickets with story points > {config.sprint_review.oversized_threshold}.
Suggest splitting oversized tickets.
Flag tickets without an assignee.
For each check, calculate the percentage of tickets that failed:
fail_rate = failed_tickets / total_active_ticketsIf fail_rate > {config.sprint_review.systemic_threshold} for any check, classify it as a systemic issue that needs process-level attention, not just ticket-level fixes.
Read the output format at references/output-format.md.
Build the report using that format. All text in the report MUST be in Spanish.
Include:
Ask the user which action to take:
{config.communication.tool} is configured, offer to send a summary to the configured channel. Format the message using references/output-format-slack.md if sending to Slack.