菜单
Primary router for operations, deployment, incident, and lifecycle workflows. Analyzes intent and dispatches to deploy-checklist, incident-response, standup, status, revert. Use for pre-deploy verification, handling outages, daily summaries, progress checks, and safe rollbacks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Performs an exhaustive 14-dimension bug hunt across the codebase using Draft context (architecture, tech-stack, product) for false-positive elimination. Generates a severity-ranked report with code evidence, data flow traces, and suggested fixes. Optionally writes regression tests. Use when the user asks to find bugs, audit code for defects, scan for vulnerabilities, or says 'hunt bugs', 'find bugs', or 'code audit'.
Structured debugging session. Reproduce, isolate, diagnose, and fix bugs using systematic investigation. Invoked by /draft:new-track for bug tracks or directly for ad-hoc debugging.
Decompose project or track into modules with dependency mapping. Project scope updates architecture.md and derives .ai-context.md. Track scope generates hld.md (always) and lld.md (when --lld or High-complexity module triggers it) — design-mandated artifacts that drive implement, deploy-checklist, and upload sign-off.
Single-module production readiness audit (ACID, resilience, observability). Use to audit one service/module end-to-end — NOT for diff/PR review (use review / quick-review) or bug-finding sweeps (use bughunt).
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.
Lists Draft's canonical workflow commands, explains the Context-Driven Development flow (init, plan, implement, review), and recommends the appropriate next step. Use when the user asks about available Draft commands, needs help choosing a workflow step, or says 'what can Draft do', 'help', or 'show commands'.
| name | ops |
| description | Primary router for operations, deployment, incident, and lifecycle workflows. Analyzes intent and dispatches to deploy-checklist, incident-response, standup, status, revert. Use for pre-deploy verification, handling outages, daily summaries, progress checks, and safe rollbacks. |
/draft:ops groups all operational, deployment, and runtime lifecycle commands.
Intent keywords drive deterministic dispatch. Multi-intent requests are sequenced (e.g., status then incident).
| User Intent Keywords | Dispatches To | Purpose |
|---|---|---|
| deploy checklist, pre-deploy, release check, readiness | /draft:deploy-checklist | Pre-deployment verification with rollback triggers |
| incident, outage, sev, postmortem, triage | /draft:incident-response | Full incident lifecycle (triage → mitigate → postmortem) |
| standup, daily summary, what did I do, activity report | /draft:standup | Git activity standup summary (read-only) |
| status, progress, what's the state, track overview | /draft:status | Progress overview across tracks and git |
| revert, rollback, undo, git revert, restore | /draft:revert | Git-aware safe rollback of changes or tracks |
User: "run the deploy checklist for the auth track"
→ dispatches to /draft:deploy-checklist [track auth]
User: "we had an outage last night, start postmortem"
→ dispatches to /draft:incident-response postmortem
User: "give me today's standup"
→ dispatches to /draft:standup
User: "what's the current status of the project"
→ dispatches to /draft:status
User: "revert the last two commits on this branch safely"
→ dispatches to /draft:revert
Ops commands often read draft/tracks.md, draft/*/plan.md, and git metadata. They feed forward into documentation and jira flows when needed.
Direct invocation of the leaf skills continues to work for power users and scripts during the deprecation window.
