克劳德代码工作流

1. requirement-analyzer determines scale

1. requirement-analyzer determines scale

Common setup

```bash

Install and start building

```bash

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:**

fixes lint and build errors, and commits per task.

```

Why UI Spec exists. Prototypes capture the visual surface, but rarely the loading, error, empty, and partial states that appear during integration.

For example, two components might each handle their own loading state cleanly while the dashboard that combines them has no defined behavior when one is still loading and the other has errored. UI Spec captures these state-x-display matrices and traces them into the Design Doc and test skeletons, so integration breakage is caught early.

⚡ Quick Start

Optional add-ons

These optional plugins cover adjacent stages in the workflow:

• 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.
• pr-review: reviews GitHub PRs with Claude Code or Codex reviewers on deterministic PR snapshots, repo-specific quality criteria, and severity-gated posting with approval.

/plugin install discover@claude-code-workflows
/plugin install metronome@claude-code-workflows
/plugin install linear-prism@claude-code-workflows
/plugin install pr-review@claude-code-workflows

4. Optional prototype code is placed under docs/ui-spec/assets/

3. UI Spec captures the screen structure (with optional prototype)

Fullstack option: generates both backend and frontend Design Docs per feature unit

```

If you're working with undocumented legacy code, these commands generate PRD and design docs to make it AI-friendly. For a quick walkthrough, see: How I Made Legacy Code AI-Friendly with Auto-Generated Docs

---

Claude Code Workflows 🚀

End-to-end development workflows for Claude Code that produce code aligned with design docs and tests. Specialized agents handle requirements, design, implementation, and quality checks, so what you get is code that actually passes its tests and matches its design docs.

---

Which plugin should I start with?

Fullstack (single plugin)

/plugin install dev-workflows-fullstack@claude-code-workflows /reload-plugins /recipe-fullstack-implement "Add user authentication with JWT + login form"

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 ```

<a id="warning-duplicate-skills"></a>

Warning: dev-skills and dev-workflows / dev-workflows-frontend / dev-workflows-fullstack share the same skills. Installing more than one of them makes skill descriptions appear multiple times in the system context. Claude Code limits skill descriptions to ~2% of the context window. Exceeding this limit causes skills to be silently ignored. For fullstack work, install only dev-workflows-fullstack (do not install it alongside dev-workflows or dev-workflows-frontend).

---

The Workflow

This figure shows how a request is routed by size (small / medium / large). Larger work goes through PRD, codebase analysis, and design before reaching implementation. Smaller work skips ahead.

The Diagnosis Workflow

The diagnosis flow loops between investigator and verifier until path coverage is sufficient, then hands off to solver for tradeoff analysis.

The Reverse Engineering Workflow

Reverse engineering runs in two phases. PRDs come first (one per discovered feature), then Design Docs reuse the scope without re-discovering it.

⚡ 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)

For fullstack recipes, install dev-workflows-fullstack and use /recipe-fullstack-implement or /recipe-fullstack-build.

Frontend Development (dev-workflows-frontend)

The frontend plugin adds React-specific agents (component architecture, Testing Library, TypeScript-first quality checks) and UI Spec generation from optional prototype code.

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.

---

Shared Agents (Available in Both Plugins)

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

Backend-Specific Agents (dev-workflows)

Frontend-Specific Agents (dev-workflows-frontend)

---

🎯 Typical Workflows

5. UI Spec captures screen structure, components, and interactions

Implements components with Testing Library, handles TypeScript types,

Fullstack Workflow

```bash /recipe-fullstack-implement "Add user authentication with JWT + React login form"

9. Vertical slices commit early so integration is verified per phase

```

Install dev-workflows-fullstack for fullstack recipes. Tasks are routed based on filename patterns (*-backend-task-*, *-frontend-task-*). For reverse engineering existing fullstack codebases, use /recipe-reverse-engineer with the fullstack option.

UI Adjustment (Frontend Plugin)

```bash /recipe-front-adjust "Tighten Card spacing and align action buttons with the design source"

Quick Fixes (Both Plugins)

```bash /recipe-task "Fix validation error message"

Direct implementation with quality checks. Works the same in both plugins.

```

Problem Diagnosis (Both Plugins)

```bash /recipe-diagnose "API returns 500 error on user login"

🔌 Contributing External Plugins

This marketplace supports the full lifecycle of building products with AI: product quality, discovery, implementation control, and verification. If your plugin helps developers build better products with AI coding agents, we'd like to hear from you.

See CONTRIBUTING.md for submission guidelines and acceptance criteria.

---

🤔 FAQ

Q: Do I need to learn special commands?

A: Not really. For backend, just use /recipe-implement. For frontend, use /recipe-front-design. The plugins handle everything else automatically.

Q: What if there are errors?

A: The quality-fixer agents (one in each plugin) automatically fix most issues like test failures, type errors, and lint problems. If something cannot be auto-fixed, you'll get clear guidance on what needs attention.

Q: Is there a version for OpenAI Codex CLI?

A: Yes. codex-workflows provides the same end-to-end development workflows for Codex CLI. Same concept (specialized subagents for requirements, design, implementation, and quality checks), adapted for the Codex CLI environment.

Q: Should I commit the work plan and task files in docs/plans/?

A: No. Recipes treat docs/plans/ as ephemeral working state. Work plans, task files, prep tasks, review-fix tasks, and intermediate analysis files all live there during a recipe run and are cleaned up at the end. Add the following line to your project's .gitignore so working state stays out of git:

docs/plans/

PRDs, ADRs, UI Specs, and Design Docs live in their own directories (docs/prd/, docs/adr/, docs/ui-spec/, docs/design/) and are intended to be committed.

---