Claude Code Workflows 🚀

End-to-end development workflows for Claude Code - Specialized agents handle requirements, design, implementation, and quality checks so you get reviewable code, not just generated code.

⚡ Quick Start

This marketplace includes the following plugins:

Core plugins:

• dev-workflows - Backend and general-purpose development
• dev-workflows-frontend - React/TypeScript specialized workflows

Optional add-ons (enhance core plugins):

• claude-code-discover - Turns feature ideas into evidence-backed PRDs
• metronome - Detects shortcut-taking behavior and nudges Claude to proceed step by step
• linear-prism - Turns requirements into structured Linear tasks — validates before decomposing, so downstream design starts clean

Skills only (for users with existing workflows):

• dev-skills - Coding best practices, testing principles, and design guidelines — no workflow recipes

These plugins provide end-to-end workflows for AI-assisted development. Choose what fits your project:

Backend or General Development

# 1. Start Claude Code
claude

# 2. Install the marketplace
/plugin marketplace add shinpr/claude-code-workflows

# 3. Install backend plugin
/plugin install dev-workflows@claude-code-workflows

# 4. Reload plugins
/reload-plugins

# 5. Start building
/recipe-implement <your feature>

Frontend Development (React/TypeScript)

# 1-2. Same as above (start Claude Code and add marketplace)

# 3. Install frontend plugin
/plugin install dev-workflows-frontend@claude-code-workflows

# 4-5. Same as above (reload plugins and start building)

# Use frontend-specific commands
/recipe-front-design <your feature>

Full-Stack Development

Install both plugins to get the complete toolkit for backend and frontend work.

# Use fullstack commands for cross-layer features
/recipe-fullstack-implement "Add user authentication with JWT + login form"

# Or execute from existing fullstack work plan
/recipe-fullstack-build

The fullstack recipes create separate Design Docs per layer (backend + frontend), verify cross-layer consistency via design-sync, and route tasks to the appropriate executor based on filename patterns. See Fullstack Workflow for details.

External Plugins

# Install discover (product discovery before implementation)
/plugin install discover@claude-code-workflows

# Install metronome (prevents shortcut-taking behavior)
/plugin install metronome@claude-code-workflows

# Install linear-prism (requirements → Linear tasks with quality gates)
/plugin install linear-prism@claude-code-workflows

Skills Only (For Users with Existing Workflows)

If you already have your own orchestration (custom prompts, scripts, CI-driven loops) and just want the best-practice guides, use dev-skills. If you want Claude to plan, execute, and verify end-to-end, install dev-workflows instead.

• Minimal context footprint — no agents or recipe skills loaded
• Drop-in best practices without changing your workflow
• Works as a ruleset layer for your own orchestrator

Do not install alongside dev-workflows or dev-workflows-frontend — duplicate skills will be silently ignored. See details below.

# Install skills-only plugin
/plugin install dev-skills@claude-code-workflows

Skills auto-load when relevant — coding-principles activates during implementation, testing-principles during test writing, etc.

Switching between plugins:

# dev-skills → dev-workflows
/plugin uninstall dev-skills@claude-code-workflows
/plugin install dev-workflows@claude-code-workflows

# dev-workflows → dev-skills
/plugin uninstall dev-workflows@claude-code-workflows
/plugin install dev-skills@claude-code-workflows

Warning: dev-skills and dev-workflows / dev-workflows-frontend share the same skills. Installing both causes skill descriptions to appear twice in the system context. Claude Code limits skill descriptions to ~2% of the context window — exceeding this limit causes skills to be silently ignored.

🔧 How It Works

The Workflow

graph TB
    A[👤 User Request] --> B[🔍 requirement-analyzer]

    B --> |"📦 Large (6+ files)"| C[📄 prd-creator]
    B --> |"📦 Medium (3-5 files)"| CA[🔬 codebase-analyzer]
    B --> |"📦 Small (1-2 files)"| E[⚡ Direct Implementation]

    C --> CA
    CA --> D[📐 technical-designer]
    D --> CV[✅ code-verifier]
    CV --> DR[📋 document-reviewer]
    DR --> DS[🔄 design-sync]
    DS --> F[🧪 acceptance-test-generator]
    F --> G[📋 work-planner]
    G --> H[✂️ task-decomposer]

    H --> I[🔨 task-executor]
    E --> I

    I --> J[✅ quality-fixer]
    J --> K[🎉 Ready to Commit]

The Diagnosis Workflow

graph LR
    P[🐛 Problem] --> INV[🔍 investigator]
    INV --> |Failure Points| VER[⚖️ verifier]
    VER --> |Coverage Check| COV{Sufficient?}
    COV --> |Yes| SOL[💡 solver]
    COV --> |No| INV
    SOL --> |Solutions + Steps| R[📋 Report]

The Reverse Engineering Workflow

graph TB
    subgraph Phase1[Phase 1: PRD Generation]
        CMD[📜 /recipe-reverse-engineer] --> SD[🔍 scope-discoverer unified]
        SD --> PRD[📄 prd-creator]
        PRD --> CV1[✅ code-verifier]
        CV1 --> DR1[📋 document-reviewer]
    end

    subgraph Phase2[Phase 2: Design Doc Generation]
        TD[📐 technical-designer] --> CV2[✅ code-verifier]
        CV2 --> DR2[📋 document-reviewer]
        DR2 --> DONE[📚 Complete]
    end

    DR1 --> |"All PRDs Approved (reuse scope)"| TD

What Happens Behind the Scenes

1. Analysis - Figures out how complex your task is
2. Codebase Understanding - Analyzes existing code to inform design decisions
3. Planning - Creates the right docs (PRD, UI Spec, Design Doc, work plan) based on complexity
4. Execution - Specialized agents handle implementation autonomously
5. Quality - Runs tests, checks types, fixes errors automatically
6. Review - Makes sure everything matches the design
7. Done - Reviewed, tested, ready to commit

⚡ Workflow Recipes

All workflow entry points use the recipe- prefix to distinguish them from knowledge skills. Type /recipe- and use tab completion to see all available recipes.

Backend & General Development (dev-workflows)

| Recipe | Purpose | When to Use | |--------|---------|-------------| | /recipe-implement | End-to-end feature development | New features, complete workflows | | /recipe-fullstack-implement | End-to-end fullstack development | Cross-layer features (requires both plugins) | | /recipe-task | Execute single task with precision | Bug fixes, small changes | | /recipe-design | Create design documentation | Architecture planning | | /recipe-plan | Generate work plan from design | Planning phase | | /recipe-build | Execute from existing task plan | Resume implementation | | /recipe-fullstack-build | Execute fullstack task plan | Resume cross-layer implementation (requires both plugins) | | /recipe-review | Verify code against design docs | Post-implementation check | | /recipe-diagnose | Investigate problems and derive solutions | Bug investigation, root cause analysis | | /recipe-reverse-engineer | Generate PRD/Design Docs from existing code | Legacy system documentation, codebase understanding | | /recipe-add-integration-tests | Add integration/E2E tests to existing code | Test coverage for existing implementations | | /recipe-update-doc | Update existing design documents with review | Spec changes, review feedback, document maintenance |

Frontend Development (dev-workflows-frontend)

| Recipe | Purpose | When to Use | |--------|---------|-------------| | /recipe-front-design | Create UI Spec + frontend Design Doc | React component architecture, UI Spec | | /recipe-front-plan | Generate frontend work plan | Component breakdown planning | | /recipe-front-build | Execute frontend task plan | Resume React implementation | | /recipe-front-review | Verify code against design docs | Post-implementation check | | /recipe-task | Execute single task with precision | Component fixes, small updates | | /recipe-diagnose | Investigate problems and derive solutions | Bug investigation, root cause analysis | | /recipe-update-doc | Update existing design documents with review | Spec changes, review feedback, document maintenance |

Tip: Both plugins share /recipe-task, /recipe-diagnose, and /recipe-update-doc. /recipe-update-doc auto-detects the document's layer. If your project has frontend Design Docs, the frontend plugin is needed to update them. For reverse engineering, use /recipe-reverse-engineer with the fullstack option to generate both backend and frontend Design Docs in a single workflow.

📦 Specialized Agents

The workflow uses specialized agents for each stage of the development lifecycle.

Shared Agents (Available in Both Plugins)

These agents work the same way whether you're building a REST API or a React app:

| Agent | What It Does | |-------|--------------| | requirement-analyzer | Figures out how complex your task is and picks the right workflow | | codebase-analyzer | Analyzes existing codebase before design