One crew of specialist AI agents for any coding assistant. Spec-driven · test-first · security-reviewed · model-tiered
anycrew installs a ready-made engineering team into the coding assistant you already use:
Claude Code, OpenAI Codex, Google Antigravity, Cursor, OpenCode or GitHub Copilot. Sixteen agents
(brainstormer, product manager, architect, designer, spec writer, implementer, tester, reviewer,
security reviewer, debugger, AI engineer, release engineer, doc writer, scout, crew lead) follow one
spec-driven method from idea to a deployed MVP, and each declares how much model it needs so cheap
work runs on cheap models.
This package is the Python CLI. It has no dependencies and needs Python 3.9 or newer.
Install and run
uvx anycrew init # run without installing (uv)
pipx run anycrew init # run without installing (pipx)
pip install anycrew # or install the `anycrew` command
uv tool install anycrew
Quick start
cd your-project
anycrew init --preset python-fastapi-react --tools claude,codex,antigravity
# or just: anycrew init (detects the assistants on your machine)
anycrew doctor # what each assistant will read
anycrew list # agents, tiers and the model each assistant will use
anycrew sync # regenerate after editing .anycrew/config.json or upgrading
Then open your assistant in the folder and type /crew-status. For a new idea, /crew-brainstorm;
for an existing codebase, /crew-spec.
What init writes
your-project/
├── AGENTS.md agent guide, read by every assistant (yours to edit)
├── docs/ constitution, status, specs index, ADR and spec templates (yours)
├── .anycrew/config.json preset, tools, model overrides
├── .agents/rules|skills|agents universal layer: Codex, Antigravity, Cursor, Copilot, OpenCode
├── .claude/ .codex/ .cursor/ .opencode/ .github/ native files per assistant
└── .anycrew/hooks/ lint-after-edit hook
Generated files carry an anycrew:generated marker; sync rewrites only those. AGENTS.md and
everything under docs/ are created once and then belong to you.
Presets
python-fastapi-react, node-typescript-next, go-service, generic, or your own JSON file:
anycrew init --preset ./my-stack.json. A preset carries commands and conventions, never code.
Model tiers
| Tier | Claude Code | Antigravity | Codex | Used by |
|---|---|---|---|---|
| fast | haiku, low effort | flash | low effort | scout, doc-writer |
| balanced | sonnet, medium | flash | medium | implementer, tester, researcher, designer, release-engineer |
| strong | opus, high | pro | high | brainstormer, product-manager, architect, spec-writer, reviewer, security-reviewer, debugger, ai-engineer, crew-lead |
Override per project in .anycrew/config.json under models.
Documentation
- Repository and full README: https://github.com/fadlytanjung/anycrew
- Wiki (every concept explained: SDD, ADR, PRD, acceptance criteria, gates, tiers): https://github.com/fadlytanjung/anycrew/wiki
- Changelog: https://github.com/fadlytanjung/anycrew/blob/main/CHANGELOG.md
A Node build of the same CLI exists on npm for teams without Python; both generate byte-identical projects.
Licence
MIT.
Metadata
Release files for anycrew 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| anycrew-0.3.0.tar.gz | 119.6 kB | With provenance | Details for anycrew-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anycrew-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for anycrew-0.3.0-py3-none-any.whl |
Total release size: 231.4 kB
Release files / anycrew-0.3.0.tar.gz
| Download URL | anycrew-0.3.0.tar.gz |
|---|---|
| Size | 119.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfa84bfcb8eabd4e6f41a2c854595f8f77a8700df5952a2c5ae4ae8c60146497
|
|
BLAKE2b-256 checksum How to use checksums |
7ed298428c27b11e8bd2167d3f395793b3515cc6a471806880d851faef69e8d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / anycrew-0.3.0-py3-none-any.whl
| Download URL | anycrew-0.3.0-py3-none-any.whl |
|---|---|
| Size | 111.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92ddac95e51d8d0827d39b2bedb2d63c0c804a1dff6655fc75cbf3c13eb11f10
|
|
BLAKE2b-256 checksum How to use checksums |
c9b40394d1958f3782ed2f76fe784f800f45f87d3d6c99af1b33df8946fe79bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logSecurity for anycrew 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for anycrew-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.