Milvus Integration Workflow

Use this for Python open-source projects where the goal is an upstream Milvus or Zilliz Cloud integration PR.

1. Evaluate before coding

1. Read project guidance first: AGENTS.md, CLAUDE.md, CONTRIBUTING.md, README.md, pyproject.toml, and relevant docs/.
2. Check existing Milvus work before editing:

   gh pr list --repo <owner>/<repo> --state all --search "milvus"
   gh issue list --repo <owner>/<repo> --state all --search "milvus"
   

3. If an open or recently closed Milvus PR exists, pause and report status, conflicts, and whether it should be replaced, rescued, or abandoned.
4. Classify the project architecture:
   • Existing backend/provider abstraction: add a Milvus provider.
   • Hardcoded backend but clear boundary: propose abstraction plus Milvus provider.
   • Scattered or coupled storage logic: pause and ask whether to proceed.
5. Report the plan before implementation: abstraction entry point, dependency strategy, tests, docs, risks, and PR value.