メニュー
Issue classification, prioritization, and management patterns for GitHub integration.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Demo pipeline state machine — 7-phase autonomous sequence with delegation context templates, phase transition logic, BLOCKED recovery strategies, and demo-state.json schema. Used exclusively by demo-conductor.
Cinematic narration style guide for demo-conductor — ANSI-coloured banner formats, live pipeline scoreboard, audience-facing language, phase summaries, and error narration patterns. Keeps the demo presentation-quality throughout.
Standardized completion and escalation protocol for subagent responses. Ensures the conductor can machine-parse every subagent return. Use when reporting completion status back to the orchestrator.
Cross-session learnings lifecycle — schema, storage, retrieval, and pruning of lessons learned during orchestrator sessions. Use when managing learnings via the /learn command.
Agent Teams assembly and task injection — selects appropriate team, validates prerequisites, estimates cost, injects tasks into the shared task list, and manages team lifecycle.
Token and cost tracking with model tier enforcement
| name | issue-triage |
| description | Issue classification, prioritization, and management patterns for GitHub integration. |
| Priority | Response Time | Criteria |
|---|---|---|
| P0 — Critical | < 1 hour | Data loss, security breach, complete outage |
| P1 — High | < 4 hours | Major feature broken, no workaround |
| P2 — Medium | < 1 week | Feature degraded, workaround available |
| P3 — Low | Backlog | Cosmetic, enhancement, nice-to-have |
bug — Something isn't workingenhancement — New feature or improvementdocumentation — Documentation update neededquestion — Clarification neededtech-debt — Code quality improvementneeds-triage — Not yet classifiedneeds-info — Waiting for reporterconfirmed — Reproduced and acceptedwont-fix — Intentional behavior or out of scopeApply area labels matching the affected component: area/api, area/ui, area/auth, area/data, etc.
Before creating new issues:
stale labelneeds-info after 14 days without responseP3 to milestone "Backlog" after triage