Design a Grok Bot role and create its setup prompt. Use only when the user explicitly invokes /new-grok-bot.

Launch a new bb worker thread with the right project, model, worktree, and task brief. Use for nagent, launching a bb session, or a standalone bb agent. Covers thread creation; use bb-cli for managing existing threads.

Operate and coordinate AI agents in Herdr workspaces in Ghostty. Use when the user mentions Herdr or asks to inspect, message, wait for, or coordinate its agents. Excludes cmux and ordinary terminal sessions.

Launch an independent GPT code review and return it verbatim. Use only when the user explicitly invokes /gpt-review.

Use Git worktrees to isolate parallel coding tasks. Use when setting up a task checkout, working in a shared repo, or managing existing worktrees.

Launch an independent Fable code review and return it verbatim. Use only when the user explicitly invokes /fable-review.

Use this when controlling bb. The bb CLI inspects and manages threads, environments, projects, machines, providers, skills, plugins, settings, terminals, and other BB services.

Bulk-triage unresolved Jira bugs with AI-driven recommendations and an interactive HTML report. Scan also loads recently resolved bugs for regression matching in analyze. Use when triaging a project backlog, prioritizing bug fixes, identifying candidates for automated fixing, or reviewing stale issues. For one bug in depth (no artifacts), use /assess. Activated by commands: /run, /start, /scan, /analyze, /report, and /assess.

Pre-cycle Feature sizing workflow that assesses Features from Jira using T-shirt sizes (XS–XXL), produces per-team effort breakdowns (DEV, QE, UX, UI, DOCS), and writes results back to Jira. Accepts a single Feature or all Features in a Fix Version for batch sizing. Use when sizing Features for cycle planning, prioritizing a release backlog, or evaluating whether a Feature fits in a cycle. Activated by commands: /ingest, /assess, /apply.

Requirements-to-PRD workflow that ingests requirements from Jira, clarifies ambiguities through iterative Q&A, drafts a Product Requirements Document, and manages review via GitHub PRs. Use when creating PRDs, analyzing requirements, or preparing feature specifications for review. Activated by commands: /ingest, /clarify, /draft, /revise, /publish, /respond.

KCS article workflow that gathers bug context from Jira and user input, drafts a KCS Solution article in markdown, validates it against the KCS Content Standard, and produces a handoff message for the support engineer. Use when writing KCS articles for known issues with workarounds. Activated by commands: /gather, /draft, /validate, /handoff.

Story-to-code workflow that takes a Jira Story, plans the implementation, writes contract-based tests and production code via TDD, validates against the project's CI expectations, and manages review via GitHub PRs. Use when implementing Jira stories produced by the design workflow. Activated by commands: /ingest, /plan, /revise, /code, /validate, /publish, /respond.

Story-to-e2e-test workflow that takes a Jira [QE] Story, discovers the project's e2e testing infrastructure, plans test scenarios, writes e2e tests matching project conventions, validates them, and manages review via GitHub PRs. Use when implementing [QE] stories produced by the design workflow. Activated by commands: /ingest, /plan, /revise, /code, /validate, /publish, /respond.

Design-and-decompose workflow that takes a PRD, researches the problem space, drafts a technical design document with a requirement-anchored testplan, decomposes work into Jira-ready epics and stories, and manages review via GitHub PRs. Use when creating design documents, researching external integrations or standards, breaking features into epics/stories, or syncing task breakdowns to Jira. Activated by commands: /ingest, /research, /draft, /decompose, /revise, /publish, /respond, /sync.

Automated CVE remediation that reads vulnerability details from Jira vulnerability tickets, applies multi-strategy dependency fixes, validates results, and creates pull requests with full justification. Language-agnostic: supports Go, Node.js, Python, Java, Rust, Ruby. Use when patching CVEs, updating vulnerable dependencies, or responding to Jira vulnerability tickets. Activated by commands: /start, /scan, /patch, /validate, /pr, /backport, /close, /report.

AI-driven code review workflow that reviews uncommitted changes using a discoverable reviewer profile, presents findings for human decision, and iterates until approved. Supports --unattended for automated iteration. Use when reviewing code before commit or PR. Activated by commands: /start, /continue, /clean.

Deploy code to CreateOS through the NodeOps MPP Gateway. Use when a user wants to ship an application, inspect a CreateOS payment quote, pay with USDC through native MPP or x402, or check a deployment created by the gateway.

Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals, readability, clear CTAs, mobile usability, and what causes pogo-sticking back to Google. Use when the user has decent rankings but poor CTR or poor on-page conversion, wants better dwell time / engagement, less bounce, or a page experience aligned with search intent. Trigger on: "SXO", "search experience optimization", "good rankings but low CTR", "high bounce rate from search", "pogo-sticking", "improve dwell time", "SEO and conversion", "ranking but not converting", "engagement signals", "make this page convert search traffic". For pure landing-page conversion in ads use /google-ads-landing; for content quality use /seo-page.

Single-page SEO audit: content quality under Google's E-E-A-T framework and Helpful Content guidelines, on-page factors, search intent, technical signals and readability. Pulls GSC data for the page, crawls the live HTML, checks metadata, schema, internal linking and depth, and produces a scored report with fixes. Use whenever the user wants to analyze a specific page or URL, not the whole site. Trigger on: "analyze this page", "audit this URL", "how is this page doing", "evaluate my blog post", "check this landing page", "page SEO", "content quality check", "is this page good enough", "review this page's SEO", "what's wrong with this page", "how can I improve this page", "page analysis", "single page audit", "content audit for [URL]", or any request naming a specific URL/page for SEO evaluation. If the user provides a specific URL (not just a domain), this is likely the right skill; use /seo-analysis for full-site audits instead.

Full SEO audit combining Google Search Console, URL Inspection API, PageSpeed Insights, a technical crawl, keyword research, and metadata, schema, search intent and Core Web Vitals checks. Surfaces quick wins, diagnoses traffic drops and content gaps, and produces an actionable 30-day plan. Use whenever the user asks about SEO, search rankings, organic traffic, Google Search Console, keyword performance, search visibility, technical SEO, URL indexing, or LCP, INP, CLS or Lighthouse scores. Also trigger on: "why is my traffic down", "what keywords am I ranking for", "improve my rankings", "check my search console", "SEO audit", "analyze my SEO", "technical SEO", "meta tags", "indexing issues", "crawl errors", "content strategy", "keyword cannibalization", "search intent", "schema markup", "structured data", "URL inspection", "page speed", "performance score", "core web vitals", "lighthouse", or any organic search question. If in doubt, trigger.