HarnessCommunity★ 1k

Claude Code Workflows

Updated Jul 7, 2026

Production Claude Code workflows by shinpr organized as three marketplace plugins: dev-workflows (backend/general), dev-workflows-frontend (React/TypeScript), and dev-workflows-fullstack (both layers with design-sync). A requirement-analyzer routes tasks by complexity (small/medium/large); each phase runs in a fresh agent context. Includes diagnosis, reverse-engineering, and PR-review optional add-ons.

View on GitHub

What it does

/recipe-implement
End-to-end backend feature development: routes by complexity, generates PRD/Design Doc, implements with TDD, reviews against design doc.
/recipe-front-design
Creates a UI Spec capturing all screen states (loading/error/empty) and a frontend Design Doc with React component architecture.
/recipe-fullstack-implement
Full-stack feature in one command: separate Design Docs per layer, design-sync for cross-layer consistency, layer-aware task routing.
/recipe-diagnose
Diagnosis loop: investigator maps failure points, verifier checks path coverage, re-investigates if insufficient, solver produces solutions with tradeoff analysis.
/recipe-reverse-engineer
Generates PRD and Design Docs from existing code; fullstack option covers both backend and frontend in a single workflow.
/recipe-task
Executes a single scoped task (bug fix, small change) with quality checks and type verification — available in all three plugins.

Files (1)

OVERVIEW.mdprimary · markdown · 2.2 KB

## What it does

Production-grade Claude Code workflows organized as three marketplace plugins: dev-workflows (backend/general), dev-workflows-frontend (React/TypeScript), and dev-workflows-fullstack (both layers with design-sync between them). Each phase — requirements, design, implementation, QA — runs in a fresh agent context to prevent cross-phase context contamination.

The requirement-analyzer classifies task size: small (1-2 files) → direct implementation; medium (3-5 files) → codebase-analyzer + technical-designer; large (6+ files) → prd-creator + codebase-analyzer + technical-designer. Larger work generates PRDs, Architecture Decision Records, Design Docs, and acceptance test scaffolds before any code is written.

Specialist agents per plugin:

Backend (dev-workflows): prd-creator, technical-designer, codebase-analyzer, acceptance-test-generator, task-executor (TDD), quality-fixer, code-reviewer, code-verifier, scope-discoverer (for reverse engineering), investigator/verifier/solver (diagnosis loop).

Frontend (dev-workflows-frontend): ui-spec-designer (captures loading/error/empty state matrices), ui-analyzer (reads external design sources via MCP), technical-designer-frontend, task-executor-frontend (Testing Library), quality-fixer-frontend.

Shared: requirement-analyzer, work-planner, task-decomposer, document-reviewer, design-sync (cross-doc consistency), security-reviewer, rule-advisor.

All entry points use the recipe- prefix. Use tab completion (/recipe-) to see available recipes.

## Install

    claude
    /plugin marketplace add shinpr/claude-code-workflows
    /plugin install dev-workflows@claude-code-workflows   # backend
    /reload-plugins

## When to use

Use /recipe-implement for a new backend feature; /recipe-front-design then /recipe-front-build for React components; /recipe-fullstack-implement when the feature spans both layers. Use /recipe-diagnose for root cause analysis (loops between investigator and verifier until path coverage is sufficient). Use /recipe-reverse-engineer on undocumented legacy code to generate PRD and Design Docs before an AI can safely modify it. docs/plans/ is ephemeral — add it to .gitignore; docs/prd/, docs/design/, and docs/ui-spec/ should be committed.