Development Crew
Four specialists that don't just write code: they think about it, challenge you, design it, build it, and hold it accountable.
A skills-first development workflow — four specialist skills that coordinate structured software development from idea to reviewed code, on-demand and pipeline-native.
Quickstart
Give your agent Development Crew: Claude Code, Codex CLI, Codex App, OpenCode, Cursor, Gemini CLI, GitHub Copilot CLI.
How it works
Development Crew is a pipeline-first workflow: four specialist skills hand off to each other like a relay race, each one knowing exactly what to expect from the previous and what to produce for the next.
You start with a rough idea. The Rubber Duck challenges your assumptions and helps you shape it into a clear problem statement. The Architect formalizes the design into a precise, buildable spec. The Implementer writes production code and tests against that spec. The Code Reviewer inspects everything for bugs, edge cases, and architectural compliance before anything ships.
Each skill can be loaded independently — jump in at any point. But when you run the full pipeline, you get a structured, reviewable path from vague idea to verified code.
Installation
Installation differs by harness. If you use more than one, install Development Crew separately for each one.
Claude Code
Codex CLI
codex plugin install https://github.com/marcelorodrigo/development-crew
Codex App
- In the Codex app, click Plugins in the sidebar.
- Search for "Development Crew" in the marketplace.
- Click Install.
OpenCode
Add to your opencode.json (global or project-level):
{
"plugin": ["development-crew@git+https://github.com/marcelorodrigo/development-crew.git"]
}
Or fetch install instructions:
Fetch and follow instructions from https://raw.githubusercontent.com/marcelorodrigo/development-crew/master/.opencode/INSTALL.md
Cursor
Add to your .cursor/plugins.json:
{
"plugins": ["development-crew@git+https://github.com/marcelorodrigo/development-crew.git"]
}
Gemini CLI
gemini extensions install https://github.com/marcelorodrigo/development-crew
GitHub Copilot CLI
The Pipeline
Use OpenCode's native skill tool (or skill: name in any harness):
-
rubber-duck - Activates before writing code. Challenges assumptions, explores alternatives, asks the questions nobody else will. Produces a structured Brainstorm Brief.
-
architect - Activates with a clear direction or Brainstorm Brief. Applies the style appropriate to your tech stack. Names every class, places every file, defines every boundary. Produces a precise Architecture Spec.
-
implementer - Activates with an Architecture Spec. Writes production code and tests that match the project's conventions. Does not add features that weren't asked for. Runs the build until it passes. Produces an Implementation Summary.
-
code-reviewer - Activates with implemented code. Diffs against the default branch. Validates against the spec, project conventions, and loaded skills. Finds bugs, edge cases, architectural violations. Produces a Code Review with categorized findings and a verdict.
The agent checks for relevant skills before every task. Mandatory workflows, not suggestions.
What's Inside
Core Skills
- rubber-duck — Brainstorming sparring partner. Assumption-challenging, solution-space widening.
- architect — Architecture formalizer. Component design, package structure, API contracts, error handling.
- implementer — Builder. Production code, tests, build verification, convention matching.
- code-reviewer — Code review specialist. Architecture compliance, bug detection, security, test quality.
- shared-principles — Cross-cutting design principles followed by all technical specialists.
Bootstrap
- using-development-crew — Orientation skill injected into every new session. Tells the agent about the pipeline, when to invoke each specialist, and how skills coordinate.
Philosophy
