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]