Grok Workflows

grok-workflows

Run [claude-code-workflows](https://github.com/shinpr/claude-code-workflows) (CCW) design, implementation, diagnosis, and review recipes on Grok without maintaining a Grok-specific fork.

This marketplace provides upstream CCW workflow packs together with `claude-to-grok`, a small adapter for Grok's tool and agent names. CCW continues to own the recipes, approval gates, review loops, and quality checks.

Quick start

Install the adapter and one workflow pack. `dev-workflows-fullstack` is the usual choice when a repository contains both backend and frontend code.

grok plugin marketplace add shinpr/grok-workflows
grok plugin install claude-to-grok --trust
grok plugin install dev-workflows-fullstack --trust

Confirm the installation, then open a new Grok session so its slash commands refresh:

grok plugin list
grok inspect

Start a workflow:

/recipe-implement "Add rate limiting to the public API"

`marketplace add` registers the catalog; the two `plugin install` commands install the adapter and workflow pack.

Choose a workflow pack

Install `claude-to-grok` plus one of these packs:

Workflow pack	Use it for	Example entry point
dev-workflows-fullstack	Backend and React/TypeScript work in the same repository	/recipe-fullstack-implement
dev-workflows	Backend, API, CLI, and general development	/recipe-implement
dev-workflows-frontend	React and TypeScript frontend work	/recipe-front-design

The packs also include focused workflows such as `/recipe-diagnose`, `/recipe-review`, and `/recipe-reverse-engineer` where applicable.

How it works

The external plugin entries in [`.grok-plugin/marketplace.json`](.grok-plugin/marketplace.json) track the default branch of the upstream CCW repository. Workflow source and release versions remain owned by CCW.

When a recipe runs, `claude-to-grok` maps the Claude Code runtime na