Claude Code Workflows plugin for Grok Build

Name: Claude Code Workflows
Author: shinpr

Community Claude Code plugin, installs in GrokPluginAutomation

Development workflows for Claude Code that keep broad exploration focused on the outcome you approved.

How to install Claude Code Workflows in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add shinpr/claude-code-workflows

2. Install the plugin:

grok plugin install dev-workflows@shinpr/claude-code-workflows --trust

✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

This repo's marketplace has 4 plugins; we checked dev-workflows, dev-workflows-frontend, dev-workflows-fullstack. Install another the same way: grok plugin install <name>@shinpr/claude-code-workflows --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add shinpr/claude-code-workflows, then select dev-workflows and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 69 skills, 3 subagents. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (40)

ai-development-guide — Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
coding-principles — Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
documentation-criteria — Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
external-resource-context — Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the
implementation-approach — Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
integration-e2e-testing — Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
llm-friendly-context — Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or gene
recipe-add-integration-tests — Add integration/E2E tests to existing codebase using Design Docs
recipe-build — Execute materialized task files in autonomous execution mode
recipe-design — Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
recipe-diagnose — Investigate problem, verify findings, and derive solutions
recipe-implement — Orchestrate the complete implementation lifecycle from requirements to deployment
recipe-plan — Create work plan from design document and obtain plan approval
recipe-quality-profile — Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.
recipe-reverse-engineer — Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
recipe-review — Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.
recipe-update-doc — Update existing design documents (Design Doc / PRD / ADR) with review
requirement-convergence — Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
subagents-orchestration-guide — Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
testing-principles — Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with frontend and browser E2E implementation references. Use when writing tests, deciding test scope, or reviewing test quality
ai-development-guide — Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
coding-principles — Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
documentation-criteria — Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
external-resource-context — Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the
frontend-ai-guide — Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
implementation-approach — Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
integration-e2e-testing — Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.
llm-friendly-context — Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or gene
recipe-diagnose — Investigate problem, verify findings, and derive solutions
recipe-front-adjust — Adjust an already-implemented UI in-session with verification against the design source
recipe-front-build — Execute materialized frontend task files in autonomous execution mode
recipe-front-design — Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
recipe-front-plan — Create frontend work plan from design document and obtain plan approval
recipe-front-review — Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-quality-profile — Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.
recipe-update-doc — Update existing design documents (Design Doc / PRD / ADR) with review
requirement-convergence — Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
subagents-orchestration-guide — Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
testing-principles — Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with frontend and browser E2E implementation references. Use when writing tests, deciding test scope, or reviewing test quality
typescript-rules — React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

Subagents (20)

dev-workflows:acceptance-test-generator — Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skele
dev-workflows:code-reviewer — Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/
dev-workflows:code-verifier — Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
dev-workflows:codebase-analyzer — Collects compact repository evidence for scope confirmation, technical option selection, complete design, and verification. Use before Design Doc creation when repository facts can change scope, reuse
dev-workflows:design-sync — Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detec
dev-workflows:document-reviewer — Reviews one document or one ADR batch against governing requirements, repository evidence, and the needs of its next consumer. Use before user approval or when document consistency and completeness ne
dev-workflows:integration-test-reviewer — Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns
dev-workflows:investigator — Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidenc
dev-workflows:prd-creator — Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metri
dev-workflows:quality-fixer — Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness,
dev-workflows:requirement-analyzer — Collects compact repository scope and cost evidence for requirement confirmation while the user retains product requirements and exclusions and the orchestrator owns comparison, Structural Scale, and
dev-workflows:scope-discoverer — Discovers functional scope from existing codebase for reverse documentation. Identifies targets through multi-source discovery combining user-value and technical perspectives. Use when "reverse engine
dev-workflows:security-reviewer — Reviews completed implementation against governing security requirements and the reachable trust model. Use after implementation or when security review/security check/vulnerability check is requested
dev-workflows:solver — Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solution
dev-workflows:task-decomposer — Converts each approved Work Plan task into one executable implementation task file. Use when work plans are approved and task materialization is needed.
dev-workflows-frontend:acceptance-test-generator — Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skele
dev-workflows-frontend:code-reviewer — Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/
dev-workflows-frontend:code-verifier — Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
dev-workflows-frontend:codebase-analyzer — Collects compact repository evidence for scope confirmation, technical option selection, complete design, and verification. Use before Design Doc creation when repository facts can change scope, reuse
dev-workflows-frontend:design-sync — Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detec

Plugins in this marketplace (4)

dev-workflows — Skills + Subagents for backend development - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents
dev-workflows-frontend — Skills + Subagents for React/TypeScript - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents
dev-workflows-fullstack — Skills + Subagents for fullstack development (backend + React/TypeScript) - Use skills for coding guidance, or run recipe workflows for full orchestrated agentic coding with specialized agents
dev-skills — Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents

About this listing

Claude Code Workflows is a community plugin on GitHub by shinpr, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 40 skills, 20 subagents, 4 plugins in this marketplaces. Its license is MIT. We checked commit 910f9dd2a912. It's one of 82 listings in the Automation category on GrokStacks.

Claude Code Workflows FAQ

How do I install Claude Code Workflows in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add shinpr/claude-code-workflows, then run grok plugin install dev-workflows@shinpr/claude-code-workflows --trust. This repo's marketplace has 4 plugins; we checked dev-workflows, dev-workflows-frontend, dev-workflows-fullstack. Install another the same way: grok plugin install <name>@shinpr/claude-code-workflows --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is Claude Code Workflows an official Grok Build plugin?

No. Claude Code Workflows is a community plugin on GitHub by shinpr, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does Claude Code Workflows include?

According to what Grok loaded in our install check, Claude Code Workflows includes 40 skills, 20 subagents, 4 plugins in this marketplaces: ai-development-guide, coding-principles, documentation-criteria, external-resource-context, implementation-approach, integration-e2e-testing….

Details

Type: Plugin
Category: Automation
Source: Community Claude Code plugin, installs in Grok
License: MIT
Author: shinpr
Keywords: agent-skills, agentic-ai, agentic-coding, ai-agents, anthropic, claude-code, claude-code-plugin, claude-code-skill, code-quality, code-review, developer-tools, development-workflow
Source repo: https://github.com/shinpr/claude-code-workflows
Checked commit: 910f9dd2a912
Checked by GrokStacks: Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain Claude Code Workflows? Add the badge; it links to this page.

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/claude-code-workflows/)

HTML

<a href="https://grokstacks.com/p/claude-code-workflows/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

Claude Code WorkflowsCommunity plugin for Grok Build · 40 skills, 20 subagents, 4 plugins in this marketplacesDevelopment workflows for Claude Code that keep broad exploration focused on the outcome you approved.View on GrokStacks →

<a href="https://grokstacks.com/p/claude-code-workflows/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Claude Code Workflows</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 40 skills, 20 subagents, 4 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Development workflows for Claude Code that keep broad exploration focused on the outcome you approved.</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Claude Code Workflows on GrokStacks](https://grokstacks.com/p/claude-code-workflows/)**: Community plugin for Grok Build with 40 skills, 20 subagents, 4 plugins in this marketplaces. Install: `grok plugin install dev-workflows@shinpr/claude-code-workflows --trust` (after `grok plugin marketplace add shinpr/claude-code-workflows`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Automation

Agent Sop

Natural language workflows that enable AI agents to perform complex, multi-step tasks with consistency and reliability.

Community Claude Code plugin, installs in GrokPluginAutomation

Agentic Creator Os

Agentic Creator OS (ACOS), by GenCreator: reusable orchestration, skills, commands, agents and local safety tooling for creator workflows.

Community plugin, built for Grok BuildPluginAutomation

Agentlas OS

Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.

Community Claude Code plugin, installs in GrokPluginAutomationMCP: manual setup

Agentrq

AgentRQ: Human-in-loop realtime conversational task manager for AI Agents. Self-hosted! Control your own agents from wherever you want Mobile, Web, Desktop. Designed to work well with your own Claude subscriptions and any harness with ACP support.

Community Claude Code plugin, installs in GrokPluginAutomationNeeds sign-in