anycrew 0.1.0__tar.gz

anycrew-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+node_modules/
+.DS_Store
+*.log
+.env
+.env.*
+!.env.example
+/tmp/
+/examples/*/node_modules/

anycrew-0.1.0/CHANGELOG.md

@@ -0,0 +1,11 @@
+# Changelog
+
+## 0.1.0 — 2026-10-29
+
+- Wiki: 17 concept pages (`wiki/`) published to the GitHub wiki; logo and plugin icon; README in
+  open-source form with a concepts primer and FAQ.
+
+- First release: 16 agents, 22 `/crew-*` skills, 6 rules, 4 presets, docs skeleton, lint hook.
+- CLI: `init`, `sync`, `doctor`, `list`, `presets`; generators for Claude Code, Codex, Antigravity,
+  Cursor, OpenCode and GitHub Copilot.
+- Manifests for Claude Code plugins/marketplace and the Agent Plugins spec.

anycrew-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 anycrew contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

anycrew-0.1.0/PKG-INFO

@@ -0,0 +1,282 @@
+Metadata-Version: 2.5
+Name: anycrew
+Version: 0.1.0
+Summary: One crew of specialist AI agents for any coding assistant. Spec-driven, test-first, security-reviewed, model-tiered. Installs into Claude Code, OpenAI Codex, Google Antigravity, Cursor, OpenCode and GitHub Copilot.
+Project-URL: Homepage, https://github.com/fadlytanjung/anycrew
+Project-URL: Repository, https://github.com/fadlytanjung/anycrew
+Project-URL: Documentation, https://github.com/fadlytanjung/anycrew/wiki
+Project-URL: Changelog, https://github.com/fadlytanjung/anycrew/blob/main/CHANGELOG.md
+Author: anycrew contributors
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agent-skills,ai-agents,antigravity,claude-code,codex,copilot,cursor,mvp,opencode,spec-driven-development
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="assets/logo.svg" alt="anycrew" width="620">
+</p>
+
+<p align="center">
+  <strong>One crew of specialist AI agents for any coding assistant.</strong><br>
+  Spec-driven · test-first · security-reviewed · model-tiered
+</p>
+
+<p align="center">
+  <a href="https://github.com/fadlytanjung/anycrew/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/fadlytanjung/anycrew/ci.yml?branch=main&label=ci"></a>
+  <a href="https://www.npmjs.com/package/anycrew"><img alt="npm" src="https://img.shields.io/npm/v/anycrew?color=0284c7"></a>
+  <img alt="node" src="https://img.shields.io/badge/node-%E2%89%A518-339933?logo=node.js&logoColor=white">
+  <img alt="dependencies" src="https://img.shields.io/badge/dependencies-0-0284c7">
+  <a href="LICENSE"><img alt="MIT" src="https://img.shields.io/badge/license-MIT-blue"></a>
+  <br>
+  <img alt="Claude Code" src="https://img.shields.io/badge/Claude_Code-000?logo=anthropic&logoColor=white">
+  <img alt="Codex" src="https://img.shields.io/badge/OpenAI_Codex-412991?logo=openai&logoColor=white">
+  <img alt="Antigravity" src="https://img.shields.io/badge/Antigravity-4285F4?logo=google&logoColor=white">
+  <img alt="Cursor" src="https://img.shields.io/badge/Cursor-111827">
+  <img alt="OpenCode" src="https://img.shields.io/badge/OpenCode-1f2937">
+  <img alt="Copilot" src="https://img.shields.io/badge/GitHub_Copilot-24292e?logo=github&logoColor=white">
+</p>
+
+---
+
+anycrew installs a ready-made engineering team into the coding assistant you already use. 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 method from idea to a deployed MVP, and leave behind the documents a team can review: a
+constitution, a PRD, ADRs, specs with acceptance criteria, and a status page that says what is
+really built. Each agent declares how much model it needs, so cheap work runs on cheap models.
+
+```bash
+npx anycrew init                           # once published to npm
+npx github:fadlytanjung/anycrew init       # works today, straight from this repository
+```
+
+> **Status: 0.1.0, early.** Claude Code and Antigravity outputs are verified end to end; Codex,
+> Cursor, OpenCode and Copilot outputs follow their documentation and are being exercised next.
+> See the [tool matrix](docs/04-tool-matrix.md). Feedback and PRs welcome.
+
+## Contents
+
+- [Why anycrew](#why-anycrew)
+- [Concepts in two minutes](#concepts-in-two-minutes)
+- [What you get](#what-you-get)
+- [Quick start](#quick-start)
+- [Install the pack globally](#install-the-pack-globally)
+- [How it works](#how-it-works)
+- [The crew](#the-crew)
+- [Model tiers](#model-tiers)
+- [What `init` writes](#what-init-writes)
+- [Documentation and wiki](#documentation-and-wiki)
+- [FAQ](#faq)
+- [Roadmap](#roadmap)
+- [Contributing](#contributing)
+- [Acknowledgements](#acknowledgements)
+- [Licence](#licence)
+
+## Why anycrew
+
+Every new project with a coding assistant repeats the same setup: an agent guide, rules, a handful
+of slash commands, a constitution, a docs skeleton, a spec loop, quality gates, a status page. Each
+assistant wants those in a different folder with a different front matter. The packs that exist are
+tied to one assistant, or ship skills without a team, or ship a method without the security,
+testing, docs and release roles an MVP needs. None of them says which model each role needs.
+
+anycrew is the boilerplate for the **team**, not for the stack. A preset describes your stack's
+commands and conventions; anycrew never forces a framework, a cloud or a language.
+
+## Concepts in two minutes
+
+Every term has a page in the [wiki](wiki/Home.md). The short version:
+
+| Term | Means | In anycrew |
+|---|---|---|
+| **SDD** (spec-driven development) | write and approve the spec first, implement from it, change both together | the whole method; `rules/00-sdd-process.md` |
+| **Constitution** | the short list of principles every change is checked against | `docs/00-constitution.md`, created by `init` |
+| **PRD** (product requirements document) | who it is for, what they need, scope by priority, requirements with IDs | `docs/03`, written by `/crew-prd` |
+| **ADR** (architecture decision record) | one decision that is expensive to reverse: context, options, decision, consequences | `docs/adr/ADR-NNN-*.md`, written by `/crew-adr` |
+| **AC** (acceptance criterion) | one testable Given/When/Then statement, `AC-NNN-n` | in every spec; test names and commits cite them |
+| **Spec · plan · tasks** | what and why · how and which files · ordered test-first checklist | `docs/specs/NNN-name/`, the unit of work |
+| **Implementation status** | the only doc that says what is actually built, with the test that proves it | `docs/20`, kept true by `/crew-checkpoint` |
+| **Gate** | a point where a person decides before the next phase | decision, P0 scope, ADRs, spec Ready, production deploy |
+| **Agent** | a specialist with its own prompt, tools and model the assistant delegates to | 16 in `agents/` |
+| **Skill** | a procedure loaded on demand, typed as `/name` | 22 `/crew-*` in `skills/` |
+| **Rule** | always-on or path-scoped guidance | 6 in `rules/`, plus stack rules from your preset |
+| **Tier** | how much model an agent needs: `fast`, `balanced`, `strong` | mapped per assistant in `models.json` |
+| **Preset** | a JSON description of a stack: commands, layout, conventions | `presets/`, or your own file |
+| **Hook** | a command the assistant runs at an event, e.g. after a file edit | lint-after-edit, wired into each assistant |
+
+## What you get
+
+| | |
+|---|---|
+| **16 agents** | each with a job, inputs, outputs, a procedure, rules, stop conditions and a **model tier** |
+| **22 skills** (`/crew-*`) | the workflow as slash commands: status, brainstorm, research, prd, architecture, adr, design, spec, plan, tasks, implement, test, review, security, verify, debug, checkpoint, deploy-check, docs, llm, sync, init |
+| **6 rules** | spec-driven process, architecture boundaries, security and data, LLM features, testing, docs and status; plus backend and frontend rules generated from your preset |
+| **Docs skeleton** | constitution, brainstorm, research, PRD, traceability, architecture, data model, API, frontend, design system, conventions, security, testing, infra, observability, delivery plan, status, ADRs, specs |
+| **Presets** | `python-fastapi-react`, `node-typescript-next`, `go-service`, `generic`; write your own in one JSON file |
+| **Hook** | a tool-agnostic lint-after-edit hook wired into each assistant |
+| **One CLI** | `npx anycrew init` generates every assistant's native files from one source; `sync` keeps them current without touching your edits; zero dependencies |
+
+## Quick start
+
+```bash
+cd your-project
+npx anycrew init --preset python-fastapi-react --tools claude,codex,antigravity
+# or just:  npx anycrew init     (detects the assistants on your machine)
+# until the npm release lands, use the same commands with: npx github:fadlytanjung/anycrew
+
+npx anycrew doctor      # what each assistant will read
+npx anycrew list        # agents, tiers and the model each assistant will use
+```
+
+Then open your assistant in the folder and type `/crew-status`. For a new idea, `/crew-brainstorm`;
+for an existing codebase, `/crew-spec`.
+
+## Install the pack globally
+
+| Assistant | Command |
+|---|---|
+| Claude Code | `claude plugin marketplace add fadlytanjung/anycrew && claude plugin install anycrew@anycrew` |
+| Antigravity | `agy plugin install https://github.com/fadlytanjung/anycrew` |
+| Codex | `codex plugin marketplace add fadlytanjung/anycrew` then `/plugins` |
+| Copilot CLI | `copilot plugin install fadlytanjung/anycrew` |
+| Cursor | Customize → Install, point at the repository (Agent Plugins manifest) |
+| Skills only, any assistant | `npx skills add fadlytanjung/anycrew` |
+
+A global install gives you the agents and skills everywhere. `npx anycrew init` in a project adds
+the docs skeleton, the stack rules, the hooks and the per-project model overrides.
+
+## How it works
+
+```mermaid
+flowchart LR
+  idea["Idea"] --> b["/crew-brainstorm<br/>docs/01 decision"]
+  b --> p["/crew-prd<br/>docs/03 PRD, FR/NFR"]
+  p --> a["/crew-architecture<br/>docs/05, 09, 10, ADRs"]
+  a --> s["/crew-spec<br/>spec · plan · tasks"]
+  s --> i["/crew-implement<br/>TDD, one task, one commit"]
+  i --> r["/crew-review · /crew-security<br/>findings with evidence"]
+  r --> d["/crew-deploy-check<br/>checklist, rollback"]
+  d --> c["/crew-checkpoint · /crew-docs<br/>status that is true"]
+  i -. "/crew-debug · /crew-test" .-> i
+```
+
+Each skill delegates to one agent at its tier. The crew lead sequences the phases and keeps a
+person at every gate. Agents never approve their own work.
+
+## The crew
+
+| Agent | Tier | Does |
+|---|---|---|
+| crew-lead | strong | routes a request through the phases; never codes |
+| scout | fast | finds what exists, read-only, before anyone guesses |
+| brainstormer | strong | idea → problem scan → scored options → decision (`docs/01`) |
+| researcher | balanced | facts with sources and confidence (`docs/02`) |
+| product-manager | strong | personas, journeys, P0/P1/P2, FR/NFR (`docs/03`, `04`) |
+| architect | strong | containers, boundaries, data model, API contract, ADRs |
+| designer | balanced | screens, states, tokens, responsive and accessibility rules |
+| ai-engineer | strong | model/code boundary, prompts as files, schemas, grounding, evals |
+| spec-writer | strong | spec, plan, tasks with acceptance criteria |
+| implementer | balanced | one task, test first, smallest change, one commit |
+| tester | balanced | AC → test map, fixtures, boundary and property tests, evals |
+| debugger | strong | reproduce, isolate, root cause, regression test |
+| reviewer | strong | findings with file:line and a failure scenario; drift audit |
+| security-reviewer | strong | threat model, OWASP and LLM top-10 audit, test per fix |
+| release-engineer | balanced | build, pipeline, deploy, rollback, observability, cost guardrails |
+| doc-writer | fast | README, docs index, changelog, the status page |
+
+## Model tiers
+
+| Tier | Claude Code | Antigravity | Codex | OpenCode | Used by |
+|---|---|---|---|---|---|
+| fast | haiku, low effort | flash | low effort | claude-haiku | scout, doc-writer |
+| balanced | sonnet, medium | flash | medium | claude-sonnet | implementer, tester, researcher, designer, release-engineer |
+| strong | opus, high | pro | high | claude-opus | brainstormer, product-manager, architect, spec-writer, reviewer, security-reviewer, debugger, ai-engineer, crew-lead |
+
+Override any cell per project in `.anycrew/config.json` under `models`. Cursor and Copilot default
+to `inherit` until you set model IDs. Details: [docs/03-model-tiers.md](docs/03-model-tiers.md).
+
+## What `init` writes
+
+```
+your-project/
+├── AGENTS.md                   agent guide, read by every assistant (yours to edit)
+├── CLAUDE.md                   @AGENTS.md
+├── docs/                       constitution, status, specs index, ADR and spec templates (yours)
+├── .anycrew/config.json        preset, tools, model overrides
+├── .anycrew/hooks/             lint-after-edit.sh
+├── .agents/rules|skills|agents universal layer: Codex, Antigravity, Cursor, Copilot, OpenCode
+├── .claude/agents|skills|rules + settings.json hooks
+├── .codex/agents/*.toml
+├── .cursor/rules/*.mdc, agents/, hooks.json
+├── .opencode/agents/
+└── .github/copilot-instructions.md, instructions/, agents/, hooks/
+```
+
+Generated files carry an `anycrew:generated` marker; `sync` rewrites only those and reports the
+rest. `AGENTS.md` and everything under `docs/` are created once and then belong to you.
+
+## Documentation and wiki
+
+| Where | What |
+|---|---|
+| [wiki/](wiki/Home.md) | every term and concept, one page each: SDD, constitution, PRD, ACs, ADRs, spec loop, status, gates, agents vs skills vs rules, tiers, hooks, presets, standards, glossary, FAQ |
+| [docs/00-vision.md](docs/00-vision.md) | what anycrew is and is not |
+| [docs/01-method.md](docs/01-method.md) | the lifecycle, artifacts, gates, who does what |
+| [docs/02-agents.md](docs/02-agents.md) | the roster and how to customise it |
+| [docs/03-model-tiers.md](docs/03-model-tiers.md) | tiers and the mapping per assistant |
+| [docs/04-tool-matrix.md](docs/04-tool-matrix.md) | what each assistant reads, install, verification status |
+| [docs/05-landscape.md](docs/05-landscape.md) | comparison with BMAD, superpowers, spec-kit, wshobson/agents and others |
+| [docs/06-project-layout.md](docs/06-project-layout.md) | the docs skeleton and the spec loop in a project |
+| [docs/07-presets.md](docs/07-presets.md) | stack presets and writing your own |
+| [docs/08-roadmap.md](docs/08-roadmap.md) | what is next |
+| [docs/adr/](docs/adr/README.md) | decisions about anycrew itself |
+
+The `wiki/` folder is published to the GitHub wiki on every push to `main`.
+
+## FAQ
+
+**Is this a framework like CrewAI or LangGraph?** No. Those run agents inside your product. anycrew
+is a crew that helps you build your product inside your coding assistant.
+
+**Will it overwrite my CLAUDE.md, rules or agents?** No. `init` never touches `AGENTS.md`, `docs/`
+or any file without the `anycrew:generated` marker; it reports them instead.
+
+**Do I have to use the whole method?** No. Each skill works alone; the gates and IDs pay off most
+when the loop is used end to end.
+
+**Can I use cheaper models everywhere?** Yes: override the tier mapping per project.
+
+More in the [wiki FAQ](wiki/FAQ.md).
+
+## Roadmap
+
+0.2: exercise Codex, Cursor, OpenCode and Copilot outputs for real; eval cases per agent; a shared
+MCP server list; Gemini CLI extension. 0.3: Windsurf/Devin, Cline, Kiro, Amp, Augment; `upgrade`;
+an example project built end to end. Full list: [docs/08-roadmap.md](docs/08-roadmap.md).
+
+## Contributing
+
+`npm test` validates the pack (front matter, tier consistency, Agent Skills spec fields, size
+budgets) and runs the smoke test (init for every preset and tool, idempotent sync, protection of
+hand-written files). See [CONTRIBUTING.md](CONTRIBUTING.md), [SECURITY.md](SECURITY.md) and the
+[code of conduct](CODE_OF_CONDUCT.md).
+
+## Acknowledgements
+
+anycrew stands on the work of others: the spec loop and constitution from
+[spec-kit](https://github.com/github/spec-kit) and Kiro; brainstorm-first skills from
+[superpowers](https://github.com/obra/superpowers) and Compound Engineering; per-agent model
+selection from [wshobson/agents](https://github.com/wshobson/agents) and oh-my-claudecode; the
+open formats [AGENTS.md](https://agents.md), [Agent Skills](https://agentskills.io) and
+[Agent Plugins](https://agent-plugins.org); and the ADR format from Michael Nygard.
+
+## Licence
+
+[MIT](LICENSE).

anycrew-0.1.0/README.md

@@ -0,0 +1,261 @@
+<p align="center">
+  <img src="assets/logo.svg" alt="anycrew" width="620">
+</p>
+
+<p align="center">
+  <strong>One crew of specialist AI agents for any coding assistant.</strong><br>
+  Spec-driven · test-first · security-reviewed · model-tiered
+</p>
+
+<p align="center">
+  <a href="https://github.com/fadlytanjung/anycrew/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/fadlytanjung/anycrew/ci.yml?branch=main&label=ci"></a>
+  <a href="https://www.npmjs.com/package/anycrew"><img alt="npm" src="https://img.shields.io/npm/v/anycrew?color=0284c7"></a>
+  <img alt="node" src="https://img.shields.io/badge/node-%E2%89%A518-339933?logo=node.js&logoColor=white">
+  <img alt="dependencies" src="https://img.shields.io/badge/dependencies-0-0284c7">
+  <a href="LICENSE"><img alt="MIT" src="https://img.shields.io/badge/license-MIT-blue"></a>
+  <br>
+  <img alt="Claude Code" src="https://img.shields.io/badge/Claude_Code-000?logo=anthropic&logoColor=white">
+  <img alt="Codex" src="https://img.shields.io/badge/OpenAI_Codex-412991?logo=openai&logoColor=white">
+  <img alt="Antigravity" src="https://img.shields.io/badge/Antigravity-4285F4?logo=google&logoColor=white">
+  <img alt="Cursor" src="https://img.shields.io/badge/Cursor-111827">
+  <img alt="OpenCode" src="https://img.shields.io/badge/OpenCode-1f2937">
+  <img alt="Copilot" src="https://img.shields.io/badge/GitHub_Copilot-24292e?logo=github&logoColor=white">
+</p>
+
+---
+
+anycrew installs a ready-made engineering team into the coding assistant you already use. 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 method from idea to a deployed MVP, and leave behind the documents a team can review: a
+constitution, a PRD, ADRs, specs with acceptance criteria, and a status page that says what is
+really built. Each agent declares how much model it needs, so cheap work runs on cheap models.
+
+```bash
+npx anycrew init                           # once published to npm
+npx github:fadlytanjung/anycrew init       # works today, straight from this repository
+```
+
+> **Status: 0.1.0, early.** Claude Code and Antigravity outputs are verified end to end; Codex,
+> Cursor, OpenCode and Copilot outputs follow their documentation and are being exercised next.
+> See the [tool matrix](docs/04-tool-matrix.md). Feedback and PRs welcome.
+
+## Contents
+
+- [Why anycrew](#why-anycrew)
+- [Concepts in two minutes](#concepts-in-two-minutes)
+- [What you get](#what-you-get)
+- [Quick start](#quick-start)
+- [Install the pack globally](#install-the-pack-globally)
+- [How it works](#how-it-works)
+- [The crew](#the-crew)
+- [Model tiers](#model-tiers)
+- [What `init` writes](#what-init-writes)
+- [Documentation and wiki](#documentation-and-wiki)
+- [FAQ](#faq)
+- [Roadmap](#roadmap)
+- [Contributing](#contributing)
+- [Acknowledgements](#acknowledgements)
+- [Licence](#licence)
+
+## Why anycrew
+
+Every new project with a coding assistant repeats the same setup: an agent guide, rules, a handful
+of slash commands, a constitution, a docs skeleton, a spec loop, quality gates, a status page. Each
+assistant wants those in a different folder with a different front matter. The packs that exist are
+tied to one assistant, or ship skills without a team, or ship a method without the security,
+testing, docs and release roles an MVP needs. None of them says which model each role needs.
+
+anycrew is the boilerplate for the **team**, not for the stack. A preset describes your stack's
+commands and conventions; anycrew never forces a framework, a cloud or a language.
+
+## Concepts in two minutes
+
+Every term has a page in the [wiki](wiki/Home.md). The short version:
+
+| Term | Means | In anycrew |
+|---|---|---|
+| **SDD** (spec-driven development) | write and approve the spec first, implement from it, change both together | the whole method; `rules/00-sdd-process.md` |
+| **Constitution** | the short list of principles every change is checked against | `docs/00-constitution.md`, created by `init` |
+| **PRD** (product requirements document) | who it is for, what they need, scope by priority, requirements with IDs | `docs/03`, written by `/crew-prd` |
+| **ADR** (architecture decision record) | one decision that is expensive to reverse: context, options, decision, consequences | `docs/adr/ADR-NNN-*.md`, written by `/crew-adr` |
+| **AC** (acceptance criterion) | one testable Given/When/Then statement, `AC-NNN-n` | in every spec; test names and commits cite them |
+| **Spec · plan · tasks** | what and why · how and which files · ordered test-first checklist | `docs/specs/NNN-name/`, the unit of work |
+| **Implementation status** | the only doc that says what is actually built, with the test that proves it | `docs/20`, kept true by `/crew-checkpoint` |
+| **Gate** | a point where a person decides before the next phase | decision, P0 scope, ADRs, spec Ready, production deploy |
+| **Agent** | a specialist with its own prompt, tools and model the assistant delegates to | 16 in `agents/` |
+| **Skill** | a procedure loaded on demand, typed as `/name` | 22 `/crew-*` in `skills/` |
+| **Rule** | always-on or path-scoped guidance | 6 in `rules/`, plus stack rules from your preset |
+| **Tier** | how much model an agent needs: `fast`, `balanced`, `strong` | mapped per assistant in `models.json` |
+| **Preset** | a JSON description of a stack: commands, layout, conventions | `presets/`, or your own file |
+| **Hook** | a command the assistant runs at an event, e.g. after a file edit | lint-after-edit, wired into each assistant |
+
+## What you get
+
+| | |
+|---|---|
+| **16 agents** | each with a job, inputs, outputs, a procedure, rules, stop conditions and a **model tier** |
+| **22 skills** (`/crew-*`) | the workflow as slash commands: status, brainstorm, research, prd, architecture, adr, design, spec, plan, tasks, implement, test, review, security, verify, debug, checkpoint, deploy-check, docs, llm, sync, init |
+| **6 rules** | spec-driven process, architecture boundaries, security and data, LLM features, testing, docs and status; plus backend and frontend rules generated from your preset |
+| **Docs skeleton** | constitution, brainstorm, research, PRD, traceability, architecture, data model, API, frontend, design system, conventions, security, testing, infra, observability, delivery plan, status, ADRs, specs |
+| **Presets** | `python-fastapi-react`, `node-typescript-next`, `go-service`, `generic`; write your own in one JSON file |
+| **Hook** | a tool-agnostic lint-after-edit hook wired into each assistant |
+| **One CLI** | `npx anycrew init` generates every assistant's native files from one source; `sync` keeps them current without touching your edits; zero dependencies |
+
+## Quick start
+
+```bash
+cd your-project
+npx anycrew init --preset python-fastapi-react --tools claude,codex,antigravity
+# or just:  npx anycrew init     (detects the assistants on your machine)
+# until the npm release lands, use the same commands with: npx github:fadlytanjung/anycrew
+
+npx anycrew doctor      # what each assistant will read
+npx anycrew list        # agents, tiers and the model each assistant will use
+```
+
+Then open your assistant in the folder and type `/crew-status`. For a new idea, `/crew-brainstorm`;
+for an existing codebase, `/crew-spec`.
+
+## Install the pack globally
+
+| Assistant | Command |
+|---|---|
+| Claude Code | `claude plugin marketplace add fadlytanjung/anycrew && claude plugin install anycrew@anycrew` |
+| Antigravity | `agy plugin install https://github.com/fadlytanjung/anycrew` |
+| Codex | `codex plugin marketplace add fadlytanjung/anycrew` then `/plugins` |
+| Copilot CLI | `copilot plugin install fadlytanjung/anycrew` |
+| Cursor | Customize → Install, point at the repository (Agent Plugins manifest) |
+| Skills only, any assistant | `npx skills add fadlytanjung/anycrew` |
+
+A global install gives you the agents and skills everywhere. `npx anycrew init` in a project adds
+the docs skeleton, the stack rules, the hooks and the per-project model overrides.
+
+## How it works
+
+```mermaid
+flowchart LR
+  idea["Idea"] --> b["/crew-brainstorm<br/>docs/01 decision"]
+  b --> p["/crew-prd<br/>docs/03 PRD, FR/NFR"]
+  p --> a["/crew-architecture<br/>docs/05, 09, 10, ADRs"]
+  a --> s["/crew-spec<br/>spec · plan · tasks"]
+  s --> i["/crew-implement<br/>TDD, one task, one commit"]
+  i --> r["/crew-review · /crew-security<br/>findings with evidence"]
+  r --> d["/crew-deploy-check<br/>checklist, rollback"]
+  d --> c["/crew-checkpoint · /crew-docs<br/>status that is true"]
+  i -. "/crew-debug · /crew-test" .-> i
+```
+
+Each skill delegates to one agent at its tier. The crew lead sequences the phases and keeps a
+person at every gate. Agents never approve their own work.
+
+## The crew
+
+| Agent | Tier | Does |
+|---|---|---|
+| crew-lead | strong | routes a request through the phases; never codes |
+| scout | fast | finds what exists, read-only, before anyone guesses |
+| brainstormer | strong | idea → problem scan → scored options → decision (`docs/01`) |
+| researcher | balanced | facts with sources and confidence (`docs/02`) |
+| product-manager | strong | personas, journeys, P0/P1/P2, FR/NFR (`docs/03`, `04`) |
+| architect | strong | containers, boundaries, data model, API contract, ADRs |
+| designer | balanced | screens, states, tokens, responsive and accessibility rules |
+| ai-engineer | strong | model/code boundary, prompts as files, schemas, grounding, evals |
+| spec-writer | strong | spec, plan, tasks with acceptance criteria |
+| implementer | balanced | one task, test first, smallest change, one commit |
+| tester | balanced | AC → test map, fixtures, boundary and property tests, evals |
+| debugger | strong | reproduce, isolate, root cause, regression test |
+| reviewer | strong | findings with file:line and a failure scenario; drift audit |
+| security-reviewer | strong | threat model, OWASP and LLM top-10 audit, test per fix |
+| release-engineer | balanced | build, pipeline, deploy, rollback, observability, cost guardrails |
+| doc-writer | fast | README, docs index, changelog, the status page |
+
+## Model tiers
+
+| Tier | Claude Code | Antigravity | Codex | OpenCode | Used by |
+|---|---|---|---|---|---|
+| fast | haiku, low effort | flash | low effort | claude-haiku | scout, doc-writer |
+| balanced | sonnet, medium | flash | medium | claude-sonnet | implementer, tester, researcher, designer, release-engineer |
+| strong | opus, high | pro | high | claude-opus | brainstormer, product-manager, architect, spec-writer, reviewer, security-reviewer, debugger, ai-engineer, crew-lead |
+
+Override any cell per project in `.anycrew/config.json` under `models`. Cursor and Copilot default
+to `inherit` until you set model IDs. Details: [docs/03-model-tiers.md](docs/03-model-tiers.md).
+
+## What `init` writes
+
+```
+your-project/
+├── AGENTS.md                   agent guide, read by every assistant (yours to edit)
+├── CLAUDE.md                   @AGENTS.md
+├── docs/                       constitution, status, specs index, ADR and spec templates (yours)
+├── .anycrew/config.json        preset, tools, model overrides
+├── .anycrew/hooks/             lint-after-edit.sh
+├── .agents/rules|skills|agents universal layer: Codex, Antigravity, Cursor, Copilot, OpenCode
+├── .claude/agents|skills|rules + settings.json hooks
+├── .codex/agents/*.toml
+├── .cursor/rules/*.mdc, agents/, hooks.json
+├── .opencode/agents/
+└── .github/copilot-instructions.md, instructions/, agents/, hooks/
+```
+
+Generated files carry an `anycrew:generated` marker; `sync` rewrites only those and reports the
+rest. `AGENTS.md` and everything under `docs/` are created once and then belong to you.
+
+## Documentation and wiki
+
+| Where | What |
+|---|---|
+| [wiki/](wiki/Home.md) | every term and concept, one page each: SDD, constitution, PRD, ACs, ADRs, spec loop, status, gates, agents vs skills vs rules, tiers, hooks, presets, standards, glossary, FAQ |
+| [docs/00-vision.md](docs/00-vision.md) | what anycrew is and is not |
+| [docs/01-method.md](docs/01-method.md) | the lifecycle, artifacts, gates, who does what |
+| [docs/02-agents.md](docs/02-agents.md) | the roster and how to customise it |
+| [docs/03-model-tiers.md](docs/03-model-tiers.md) | tiers and the mapping per assistant |
+| [docs/04-tool-matrix.md](docs/04-tool-matrix.md) | what each assistant reads, install, verification status |
+| [docs/05-landscape.md](docs/05-landscape.md) | comparison with BMAD, superpowers, spec-kit, wshobson/agents and others |
+| [docs/06-project-layout.md](docs/06-project-layout.md) | the docs skeleton and the spec loop in a project |
+| [docs/07-presets.md](docs/07-presets.md) | stack presets and writing your own |
+| [docs/08-roadmap.md](docs/08-roadmap.md) | what is next |
+| [docs/adr/](docs/adr/README.md) | decisions about anycrew itself |
+
+The `wiki/` folder is published to the GitHub wiki on every push to `main`.
+
+## FAQ
+
+**Is this a framework like CrewAI or LangGraph?** No. Those run agents inside your product. anycrew
+is a crew that helps you build your product inside your coding assistant.
+
+**Will it overwrite my CLAUDE.md, rules or agents?** No. `init` never touches `AGENTS.md`, `docs/`
+or any file without the `anycrew:generated` marker; it reports them instead.
+
+**Do I have to use the whole method?** No. Each skill works alone; the gates and IDs pay off most
+when the loop is used end to end.
+
+**Can I use cheaper models everywhere?** Yes: override the tier mapping per project.
+
+More in the [wiki FAQ](wiki/FAQ.md).
+
+## Roadmap
+
+0.2: exercise Codex, Cursor, OpenCode and Copilot outputs for real; eval cases per agent; a shared
+MCP server list; Gemini CLI extension. 0.3: Windsurf/Devin, Cline, Kiro, Amp, Augment; `upgrade`;
+an example project built end to end. Full list: [docs/08-roadmap.md](docs/08-roadmap.md).
+
+## Contributing
+
+`npm test` validates the pack (front matter, tier consistency, Agent Skills spec fields, size
+budgets) and runs the smoke test (init for every preset and tool, idempotent sync, protection of
+hand-written files). See [CONTRIBUTING.md](CONTRIBUTING.md), [SECURITY.md](SECURITY.md) and the
+[code of conduct](CODE_OF_CONDUCT.md).
+
+## Acknowledgements
+
+anycrew stands on the work of others: the spec loop and constitution from
+[spec-kit](https://github.com/github/spec-kit) and Kiro; brainstorm-first skills from
+[superpowers](https://github.com/obra/superpowers) and Compound Engineering; per-agent model
+selection from [wshobson/agents](https://github.com/wshobson/agents) and oh-my-claudecode; the
+open formats [AGENTS.md](https://agents.md), [Agent Skills](https://agentskills.io) and
+[Agent Plugins](https://agent-plugins.org); and the ADR format from Michael Nygard.
+
+## Licence
+
+[MIT](LICENSE).

anycrew-0.1.0/agents/ai-engineer.md

@@ -0,0 +1,50 @@
+---
+name: ai-engineer
+description: "Designs and reviews the model-backed parts of the product (docs/06): which steps are a model call and which are code, prompts as versioned files with output schemas, grounding and citations, untrusted-content framing, model choice and cost per call, evals and tracing. Use when a feature calls an LLM, when building a multi-agent system, or when model output quality or cost is in question."
+tier: strong
+model: opus
+phase: design
+reads: [docs/05-architecture.md, docs/06-agent-design.md, docs/00-constitution.md, rules/50-llm-features.md]
+writes: [docs/06-agent-design.md, prompts, output schemas, evals]
+tools: Read, Grep, Glob, Write, Edit, Bash, WebSearch, WebFetch
+---
+
+# AI engineer
+
+You decide where a model belongs and where it does not, and you make model calls boring:
+versioned, schema-checked, grounded, measured and cheap enough.
+
+## Procedure
+
+1. **Draw the model/code boundary.** For each step of the feature: does it need judgement
+   (read, classify, map, explain, converse) or correctness (compute, match, decide, mutate)?
+   Judgement may be a model call; correctness is code. Write the table in `docs/06`.
+2. **Design each call.** Purpose, inputs (with the untrusted parts marked), output schema
+   (strict, validated before use), model tier (fast for classification and extraction, strong
+   for reasoning and prose), temperature, timeout, retry and fallback, cost per call and per
+   user action.
+3. **Prompts as files.** `prompts/<id>.md` with front matter `id`, `version`, `model`,
+   `output_schema`. No prompt text in code. Bump the version on every change and re-run the
+   evals and recordings that depend on it.
+4. **Untrusted content.** Documents, retrieved chunks, tool results and user text are data, never
+   instructions: framed as such, passed as separate parts, never allowed to change tool
+   permissions or policy. Tools exposed to a model are read-only and scoped unless an ADR says
+   otherwise.
+5. **Grounding.** Every number or claim a model writes for a user cites a source the code can
+   verify (an ID, a page, a chunk). Code decides whether a citation holds; the model never grades
+   itself.
+6. **Evals.** A dataset with expected outcomes, scorers (exact, schema, judge where needed), a
+   report checked into docs. Evals run on demand and are not a merge gate.
+7. **Observability.** One trace per run with a span per call; token and cost accounting; content
+   capture off by default and only on with synthetic data.
+8. **Multi-agent systems.** Each agent has one job, a schema for its result, an idempotency key
+   and a small return value; large data stays in storage. Orchestration is code (a graph or a
+   workflow), not a conversation.
+
+## Rules
+
+- Models never compute money, totals, matches, risk levels or state changes.
+- The cheapest model that passes the eval wins; record the comparison.
+- Model IDs and regions are configuration, never literals.
+- A prompt that sees content includes the untrusted-content framing, always.
+- Anything a model proposes about the user's own data is a suggestion until a person accepts it.