Claude Code Development Workflows plugin
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
- 705 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Agents write code, run checks and commit
- They work with project files
Install
- Works in
Manual install
/plugin marketplace add shinpr/claude-code-workflows
/plugin install dev-workflows@claude-code-workflowsUse dev-workflows-frontend or dev-workflows-fullstack instead of dev-workflows if they fit better.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Agents write code, run checks and commit
- They work with project files
This is third-party code. Review the repository files before installing.
What it does
A set of three plugins for backend, React and TypeScript frontend, and full-stack work. A recipe first fixes the expected outcome and exclusions, then checks the design against the repository, splits the work into tasks and for each one implements, verifies, runs quality checks and commits. On larger changes a separate agent reviews the finished implementation for fit with the agreement, unnecessary changes and security problems. There are also recipes for diagnosing problems, reverse-documenting a system from its code, adding integration tests and setting repository quality rules.
Who it is for. For developers whose agent drifts into side findings on larger tasks and loses the original goal.
Good fit when
- A change involves several decisions and needs design
- You need a reliable handoff between contexts
- You want independent verification before merge
Not a fit when
- A throwaway experiment or prototype
- The outcome and change boundary are already obvious
Example request
/recipe-implement "Add rate limiting to the public API"Limitations
Works only in Claude Code with plugin marketplace support. Install only one of the three plugins; full-stack already includes the others. Recipes add agent calls and artifacts, so they use more tokens than working directly.
How to disable. Uninstall with /plugin uninstall dev-workflows@claude-code-workflows (or the variant you installed).
FAQ
Which plugin should I pick?
dev-workflows for backend and general work, dev-workflows-frontend for React, dev-workflows-fullstack for changes on both sides.
Can a team share the setup?
Yes, install the marketplace and plugin with --scope project and commit .claude/settings.json.
Discussion
No questions or reviews yet.
Related
PluginsMadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend
A Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
Nick Tune's plugin marketplace for Claude Code: checks before a task is handed in, code review and TDD personas
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
README in short
The README describes the problem: on non-trivial work the agent finds a real but side issue and drifts from the requested behavior. A table shows which recipe and plugin to start with for different tasks, with install commands for individuals and teams. A diagram shows the route from outcome agreement to independent review and how the number of decisions sets the path. MIT licensed.