Menu
Canonical integrations parent command. Handles external system exports and syncs. Routes intent to jira-preview or jira-create based on context.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | integrations |
| description | Canonical integrations parent command. Handles external system exports and syncs. Routes intent to jira-preview or jira-create based on context. |
/draft:integrations is the canonical integrations parent command.
It handles connectors and exports to external systems like Jira.
Specialist integration workflows remain available as named modes:
/draft:integrations jira-preview (formerly /draft:jira-preview)/draft:integrations jira-create (formerly /draft:jira-create)Examine the user's input and route to the correct integrations workflow.
If the user explicitly invokes a specialist mode, route directly:
/draft:integrations jira-preview → follow /draft:jira-preview/draft:integrations jira-create → follow /draft:jira-createIf no explicit mode is specified, infer the intent from the user's prompt:
| Intent | Action | Route |
|---|---|---|
| "Export to Jira", "Preview Jira issues", "Show me what you'll create in Jira" | Jira Preview | /draft:jira-preview |
| "Create Jira issues", "Sync to Jira", "Make tickets" | Jira Create | /draft:jira-create |
If the user runs a bare /draft:integrations without clear intent, present a small integrations menu with a recommended default path:
Draft Integrations Menu:
1. /draft:integrations jira-preview (Generate Jira export file for review)
2. /draft:integrations jira-create (Create Jira issues from export)
What integration action do you want to perform?
Do not automatically launch a specialist workflow without explicit or clear inferred intent.
The legacy specialist commands remain supported during the migration period, but /draft:integrations is the canonical parent for integration tasks.