「triage」の検索結果

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.

日本語の概要は準備中です。原文の説明を表示しています。

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Triages an incoming non-disclosure agreement against the organisation's written standard NDA positions and returns a DRAFT triage pack: a clause-by-clause deviations table with a severity band, a suggested response per clause quoted from the positions document, open questions and a governing-law flag, all for counsel to decide. Never gives legal advice or an acceptability call. Use when the user asks to "triage this NDA against our standard positions", "screen this confidentiality agreement before it goes to legal", "red-flag this mutual NDA", "first-pass the counterparty's NDA" or "is this NDA standard or does it need counsel". Do not use for a full review of an MSA, SOW, licence or any whole contract, use contract-review-pack instead; for one clause lined up across several documents, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate HITL triage of review findings using parallel agents. Use when the user says 'triage these findings' or 'run findings triage' or has a batch of review findings to process.

日本語の概要は準備中です。原文の説明を表示しています。

窓口が人間から「承認スコープの輪郭」を受けて、その内側で triage → worker 派遣 → iteration → verify → push → PR 作成 → CI 監視 を完了駆動で自走し、PR ごとに merge gate で必ず停止するベルトコンベア。/work-discovery + /org-delegate + verify + /org-pull-request + /org-escalation を呼ぶ薄い orchestrator。 発動条件: 人間が「この範囲は自走してよい」というスコープ承認を明示し、複数候補を 完了駆動で順次流したいとき（例「triage 上位の S 級バグ修正を空き pane 分まで自走、 merge は都度わたしが判断」）。起動主体は窓口に限定。スコープ外候補・判断境界・退出条件に 触れたら必ず halt する。merge 自動化はしない。

open Issue を triage して「次の仕事候補（N 件 + 推奨 1 件）」を窓口が人間へ提示する。 候補はオペレーターが書いたゴール台帳（registry/goals/）の条項に当たるものだけで、条項順に並ぶ。 tools/work_discovery_scan.py を 1 回実行し、その候補 JSON を 設計書 §5.2 / §12 の人間可読フォーマットでレンダリングするところで停止する（propose-only）。 起動主体は窓口に限定。手動 / イベント起動のみ（常駐 /loop なし）。 「次の仕事候補出して」「triage して」「次なにやる？」や PR マージ後の proactive next-dispatch で窓口が手動起動する。

直近N日（デフォルト1日）に更新された `cc-triage-scope` / `cc-pr-created` ラベル付きGitHub Issueのdescriptionとコメントを横断し、繰り返し現れる仕様判断・要件決定のロジックを再利用可能なルールとして抽出して `.claude/requirements/` 配下のタイプ別マークダウンへ集約・統合・圧縮したうえで、commit-push + create-prでPRを作成する（`cc-triage-scope`ラベル + 自分自身をAssignee）。作成したルールは create-issue / create-issue-from-issue-number / answer-issue-questions が仕様作成・判断の材料として読み込む。

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).

日本語の概要は準備中です。原文の説明を表示しています。

Triage WorldMonitor Sentry issues — classify unresolved events as noise, already-fixed, product bugs, or needs-human; optionally ship a tested fix. Use when the user says triage Sentry, pastes a WORLDMONITOR-* ID or sentry.io URL, or asks to investigate production errors.

日本語の概要は準備中です。原文の説明を表示しています。

PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.

日本語の概要は準備中です。原文の説明を表示しています。

Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to triage the open PR queue before a release. Classifies every open PR into must-merge, candidate, superseded, or deferred; writes a working triage doc; and runs the merge loop end-to-end. Designed for the pre-release "PR speedrun" pass where a solo maintainer wants to clear the inbound backlog in a single session.

日本語の概要は準備中です。原文の説明を表示しています。

Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.

日本語の概要は準備中です。原文の説明を表示しています。

Score and route an inbound lead, or rank a backlog of leads, against your ICP and qualification framework, then recommend a priority and next action. Use when the user asks "triage this lead", "triage my leads", "rank my lead backlog", "is [company] a good lead", "qualify [lead]", or pastes or uploads lead info.

日本語の概要は準備中です。原文の説明を表示しています。

Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.

日本語の概要は準備中です。原文の説明を表示しています。

Triage an incoming verdaccio/verdaccio GitHub issue against the codebase, the affected release line, and related issues, then choose the labels from the repository's existing taxonomy. Use whenever the user asks to triage, classify, assess, reproduce, prioritize, or label an issue, especially when an issue URL or number is supplied.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels, milestone, and assignee. Use when the user asks to triage an issue, sort the backlog, deal with new issues, check whether a bug is already reported, or says "what should we do with this issue".

日本語の概要は準備中です。原文の説明を表示しています。

Triage supplied or imported security findings against a repository using its security policy and static code evidence. Accepts scanner reports, advisories, GitHub findings, and Jira or Linear tickets. Do not use for discovery, duplicate triage, runtime validation, or fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a Sandcastle GitHub issue and try to reproduce it with Docker. Use when given an issue number to triage or verify.

日本語の概要は準備中です。原文の説明を表示しています。

Triage supplied or imported security findings against a repository using its security policy and static code evidence. Accepts scanner reports, advisories, GitHub findings, and Jira or Linear tickets. Do not use for discovery, duplicate triage, runtime validation, or fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to triage ONE microsoft/apm issue already selected by autopilot-issue-triage-scheduler. Return one advisory recommendation and a proposed scope brief, never human approval. Do not implement the issue, manage the backlog, or list the queue.

日本語の概要は準備中です。原文の説明を表示しています。