{
  "markdown": "# Development Crew\n\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)\n[![GitHub tag](https://img.shields.io/github/v/tag/marcelorodrigo/development-crew?label=version)](https://github.com/marcelorodrigo/development-crew/tags)\n\n_Four specialists that don't just write code: they think about it, challenge you, design it, build it, and hold it accountable._\n\nA **skills-first** development workflow — four specialist skills that coordinate structured software development from idea to reviewed code, on-demand and pipeline-native.\n\n## Quickstart\n\nGive your agent Development Crew: [Claude Code](#claude-code), [Codex CLI](#codex-cli), [Codex App](#codex-app), [OpenCode](#opencode), [Cursor](#cursor), [Gemini CLI](#gemini-cli), [GitHub Copilot CLI](#github-copilot-cli), [oh-my-pi](#oh-my-pi).\n\n## How it works\n\n**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.\n\nYou 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.\n\nEach 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.\n\n## Installation\n\nInstallation differs by harness. If you use more than one, install Development Crew separately for each one.\n\n### Claude Code\n\n- Add the marketplace:\n\n  ```bash\n  claude plugin marketplace add marcelorodrigo/development-crew\n  ```\n\n- Install the plugin:\n\n  ```bash\n  claude plugin install development-crew@development-crew-plugin\n  ```\n\n- Verify:\n\n  ```bash\n  /development-crew:rubber-duck\n  ```\n\n### Codex CLI\n\nAdd the repository as a plugin marketplace, then install Development Crew:\n\n```bash\ncodex plugin marketplace add marcelorodrigo/development-crew\ncodex plugin add development-crew@development-crew-plugin\n```\n\nStart a new Codex session, then verify the installation with `/skills` or invoke a skill directly:\n\n```text\n$rubber-duck\n```\n\n### Codex App\n\n- In the Codex app, click Plugins in the sidebar.\n- Search for \"Development Crew\" in the marketplace.\n- Click Install.\n\n### OpenCode\n\nInstall the latest release globally:\n\n```bash\nopencode plugin @marcelorodrigo/opencode-development-crew@latest --global\n```\n\nOr add the package to the `plugin` array in your global or project-level\n`opencode.json`:\n\n```json\n{\n  \"plugin\": [\"@marcelorodrigo/opencode-development-crew@latest\"]\n}\n```\n\nOpenCode installs the published npm package from this entry. Restart OpenCode\nafter adding or changing the plugin configuration.\n\nThe `@latest` tag resolves to the latest published release. The plugin also\nperforms a best-effort update check in the background. For an eligible floating\nnpm wrapper, it checks npm, installs and reifies the exact newer release, and\nthen shows a toast asking you to restart OpenCode. Before updating, the plugin\nsnapshots the skills outside the mutable package wrapper so OpenCode can still\ndiscover and read `SKILL.md` files safely.\n\nExact-pinned, local, and Git installs are not auto-updated. Restart OpenCode to\nactivate newly installed code. Update failures are non-fatal and do not prevent\nthe plugin from starting.\n\nIf an older destructive updater left a stale `@latest` wrapper, install the\nfixed release explicitly through OpenCode's plugin manager, using the same\nscope as the original entry, then restart OpenCode:\n\n```bash\nopencode plugin @marcelorodrigo/opencode-development-crew@<fixed-version> --global --force\n```\n\nReplace `<fixed-version>` with the first release containing this updater fix.\nFor a project-level entry, omit `--global` and run the command from that\nproject. This temporarily pins the plugin; change its config entry back to\n`@latest` afterward if you want future automatic updates. Do not remove\narbitrary cache or package paths manually.\n\nTo use the repository directly instead of npm:\n\n```json\n{\n  \"plugin\": [\"development-crew@git+https://github.com/marcelorodrigo/development-crew.git\"]\n}\n```\n\nOr fetch install instructions:\n\n```\nFetch and follow instructions from https://raw.githubusercontent.com/marcelorodrigo/development-crew/master/OPENCODE_INSTALL.md\n```\n\n### Cursor\n\nAdd to your `.cursor/plugins.json`:\n\n```json\n{\n  \"plugins\": [\"development-crew@git+https://github.com/marcelorodrigo/development-crew.git\"]\n}\n```\n\n### Gemini CLI\n\n```bash\ngemini extensions install https://github.com/marcelorodrigo/development-crew\n```\n\n### GitHub Copilot CLI\n\n- Add the marketplace:\n\n  ```bash\n  copilot plugin marketplace add marcelorodrigo/development-crew\n  ```\n\n- Install:\n\n  ```bash\n  copilot plugin install development-crew@development-crew-plugin\n  ```\n\n### oh-my-pi\n\n- Add the marketplace:\n\n  ```bash\n  omp plugin marketplace add marcelorodrigo/development-crew\n  ```\n\n- Install the plugin:\n\n  ```bash\n  omp plugin install development-crew@development-crew-plugin\n  ```\n\n- Verify:\n\n  ```bash\n  /skill:rubber-duck\n  ```\n\n## The Pipeline\n\nUse OpenCode's native `skill` tool. In current OpenCode versions, discovered\nskills are also exposed as slash entries when no existing command has the same\nname:\n\n```text\n/rubber-duck\n/architect\n/implementer\n/code-reviewer\n```\n\nThe slash entries come from OpenCode's skill discovery; this plugin does not\nregister custom commands. If a slash entry is unavailable, use the native\n`skill` tool:\n\n1. **rubber-duck** - Activates before writing code. Challenges assumptions, explores alternatives, asks the questions nobody else will. Produces a structured **Brainstorm Brief**.\n\n2. **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**.\n\n3. **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**.\n\n4. **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.\n\n**The agent checks for relevant skills before every task.** Mandatory workflows, not suggestions.\n\n## What's Inside\n\n### Core Skills\n\n- **rubber-duck** — Brainstorming sparring partner. Assumption-challenging, solution-space widening.\n- **architect** — Architecture formalizer. Component design, package structure, API contracts, error handling.\n- **implementer** — Builder. Production code, tests, build verification, convention matching.\n- **code-reviewer** — Code review specialist. Architecture compliance, bug detection, security, test quality.\n- **shared-principles** — Cross-cutting design principles followed by all technical specialists.\n\n### Bootstrap\n\n- **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.\n\n## Philosophy\n\n- **Pipeline over chaos** — Structured handoffs beat ad-hoc coding\n- **Design before code** — No implementation without a spec\n- **Review before merge** — No merge without review\n- **Precision over preference** — Name every component, every contract\n- **Evidence over claims** — Run the build, verify the tests\n\n## Contributing\n\n1. Fork the repository\n2. Switch to the `master` branch\n3. Create a branch for your work\n4. Run `pnpm install --frozen-lockfile`\n5. Run `pnpm run test` and `node scripts/validate-skills.mjs` to verify\n6. Submit a PR against `master`\n\n## Updating\n\n- **Claude Code:** `claude plugin update development-crew@development-crew-plugin`\n- **GitHub Copilot:** `copilot plugin update development-crew@development-crew-plugin`\n- **Gemini:** `gemini extensions update https://github.com/marcelorodrigo/development-crew`\n- **oh-my-pi:** `omp plugin upgrade development-crew@development-crew-plugin`\n\n- **OpenCode:** The `@latest` npm plugin entry checks npm in the background and\n  installs the exact newer release into the eligible floating wrapper. Skills\n  are snapshotted outside the mutable wrapper before the update. Restart\n  OpenCode after the notification to activate the new code. Exact-pinned,\n  local, and Git installs are not auto-updated, and update failures are\n  non-fatal.\n\n## License\n\nMIT — see [LICENSE](LICENSE) for details.\n\n## Community\n\nBuilt by [Marcelo Rodrigo](https://github.com/marcelorodrigo).\n\n- **Issues:** https://github.com/marcelorodrigo/development-crew/issues\n- **Release announcements:** Watch the repo on GitHub\n",
  "bytes": 9079,
  "sha": "26756bca7abc66e0f767b2d87eb63d483fd262ac7444c10b7d3845d8ac7c0f0b",
  "repo_slug": "marcelorodrigo/development-crew",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_marcelorodrigo_development_crew_c98bfd43/readme"
}