{"id":50589724,"url":"https://github.com/fxbin/virtual-intelligent-dev-team","last_synced_at":"2026-06-05T09:30:35.482Z","repository":{"id":350243732,"uuid":"1205864384","full_name":"fxbin/virtual-intelligent-dev-team","owner":"fxbin","description":null,"archived":false,"fork":false,"pushed_at":"2026-05-29T11:33:39.000Z","size":831,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-05-29T13:14:39.253Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/fxbin.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-04-09T11:00:02.000Z","updated_at":"2026-05-29T11:33:43.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/fxbin/virtual-intelligent-dev-team","commit_stats":null,"previous_names":["fxbin/virtual-intelligent-dev-team"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/fxbin/virtual-intelligent-dev-team","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fxbin%2Fvirtual-intelligent-dev-team","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fxbin%2Fvirtual-intelligent-dev-team/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fxbin%2Fvirtual-intelligent-dev-team/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fxbin%2Fvirtual-intelligent-dev-team/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/fxbin","download_url":"https://codeload.github.com/fxbin/virtual-intelligent-dev-team/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fxbin%2Fvirtual-intelligent-dev-team/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33939226,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-05T02:00:06.157Z","response_time":120,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-06-05T09:30:34.865Z","updated_at":"2026-06-05T09:30:35.475Z","avatar_url":"https://github.com/fxbin.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Virtual Intelligent Dev Team\n\n`virtual-intelligent-dev-team` 是一个面向复杂软件工作的智能协作项目。\n\n它不只是“专家角色路由器”，而是把研发、产品、分轮内测、技术治理、发布门禁、显式 `/auto` 自动运行，以及状态驱动恢复，收拢成一个可持续迭代的闭环工作流。\n\n一句话说：\n\n它适合接手“单个专家已经不够、单轮回答也不够”的复杂软件任务。\n\n## 项目定位\n\n这个项目最适合三类问题：\n\n- 复杂研发交付\n  - 例如小切片实现、大重构、迁移、跨模块联动、技术治理\n- 产品与研发协同\n  - 例如需求澄清、验收标准、前后端协作、分轮 beta\n- 版本与闭环治理\n  - 例如多轮优化、release gate、post-release feedback loop、resume\n\n## 为什么不是普通多专家提示词\n\n很多“虚拟团队”方案，主要解决的是“换几个角色来回答”。\n\n这个项目想解决得更深一层：\n\n- 不只换角色\n  - 还要判断谁主负责、谁协同、是否需要治理\n- 不只给建议\n  - 还要给出执行路径、恢复锚点和下一步\n- 不只做开发前\n  - 还覆盖 beta、release、post-release feedback\n- 不只做单轮问答\n  - 还支持有边界的多轮优化和状态恢复\n\n所以它更像一个“复杂软件工作的闭环协调层”，而不是一个“多身份回答器”。\n\n## 适合解决什么问题\n\n- 复杂研发任务的 lead agent 路由与协同\n- 大型重构、迁移、拆分、技术治理\n- 多轮优化、benchmark、回滚、resume\n- 产品定义、验收标准、分轮 beta 内测\n- release gate 与 post-release feedback loop\n- trigger health 与 workflow quality baseline，避免该触发不触发、误触发、过度流程化或 completion claim 证据不足\n- goal framing：对宽目标、重复失败、release、beta、multi-agent 等任务先锁定 success evidence、stop condition 和 non-goals\n- anti-entropy governance：对 fallback growth、duplicate owner、adapter / guard 膨胀、delete vs compat 和 source-of-truth 删除边界做治理\n- 显式 `/auto` 自动运行与状态优先恢复\n- Team Engine Lite 的 Worker / Verifier 分离、RemediationPatch 和 DeliveryCycleReport\n- 受控真实 Subagent runtime eligibility：显式 multi-agent/subagent 请求或合格 `/auto` 工作流可生成 `SubagentRuntimePlan`，但只有宿主提供 spawn / wait / merge 证据时才声明真实 runtime\n\n## 核心能力\n\n- `默认手动模式`\n  - 默认是人工驱动模式，不会擅自进入自动运行。\n- `显式 /auto`\n  - 只有显式输入 `/auto` 才会进入自动运行分支。\n- `setup -\u003e go`\n  - 自动运行保持两阶段协议，先建状态，再执行。\n- `safe / background / resume`\n  - 自动子协议支持安全预演、后台执行、状态恢复。\n- `状态优先恢复`\n  - 恢复优先读取机器可读的 automation state，而不是靠对话猜测上下文。\n- `小切片交付`\n  - 小型功能或 bugfix 默认保留 quick slice brief、project context、delivery status 和验证证据。\n- `目标边界`\n  - 对容易漂移的任务先形成 goal frame，明确 success evidence、stop condition、non-goals 和当前 stop state。\n- `工作流质量基线`\n  - 用 trigger accuracy、fast-path cheapness、output compactness、evidence freshness、artifact laziness 和 authority boundary 约束 skill 迭代。\n- `反熵治理`\n  - 遇到 duplicate owner、fallback、adapter、guard 或兼容路径增长时，先判断旧路径该删除、保留兼容，还是需要用户确认。\n- `Team Engine Lite`\n  - code-facing、release-facing、Git-facing 与 remediation 路线默认保留 Worker / Verifier 分离、max-cycle retry、RemediationPatch 和 DeliveryCycleReport。\n- `受控真实 Subagent runtime eligibility`\n  - 显式 multi-agent / subagent / parallel agent 请求会生成受控计划、角色边界、spawn policy、merge policy 和 fallback；没有宿主 runtime evidence 时仍保持 `soft_orchestration_only`。\n- `外部 Agent 后端软编排`\n  - 可以把 Codex / Claude Code / OpenCode 当作角色后端，但默认只声明 `soft_orchestration_only`，不虚假声称真实异步多进程 runtime。\n- `有边界的迭代优化`\n  - 优化循环是有边界、有证据、有回滚点的，不做无限自转。\n- `发布与反馈闭环`\n  - 不只做发布前 gate，也覆盖发布后的反馈回写与下一轮修复入口。\n\n## 能力矩阵\n\n| 维度 | 本项目提供什么 | 普通多专家提示词常见缺口 |\n| --- | --- | --- |\n| 任务路由 | 选择主负责人、协同者、治理轨道 | 往往只是平铺多个角色视角 |\n| 日常交付 | 小切片 brief、项目上下文、状态锚点 | 容易直接跳到实现，缺少可恢复上下文 |\n| 执行模式 | 支持手动模式与显式 `/auto` | 通常没有明确模式切换 |\n| 恢复能力 | 状态优先恢复、resume、恢复锚点 | 容易依赖上下文记忆 |\n| 迭代能力 | 有边界的多轮优化、基线、回滚决策 | 常见问题是无限\"再来一轮\" |\n| 发布治理 | release gate、hold 后续修复入口 | 常停留在\"建议发/不发\" |\n| 上线后闭环 | post-release feedback loop | 很少覆盖上线后的反馈回写 |\n| 产品协同 | 支持产品、研发、技术治理联动 | 容易偏单一研发视角 |\n| Beta 验证 | 分轮内测、模拟用户、cohort ramp、反馈门禁 | 通常只有静态测试计划，没有结构化分轮验证 |\n| 工作流质量 | 触发健康、快路径廉价、证据新鲜度、artifact 懒创建、authority boundary | 容易越改越重，或把方法建议误说成最终权威 |\n| 反熵治理 | delete-first / compat-exception / confirmation-first 路径选择 | 常见做法是不断加 fallback 或 guard |\n| Subagent runtime | 显式请求时输出受控计划，真实执行必须有宿主 spawn / wait / merge 证据 | 容易把角色扮演误称为真实多 Agent runtime |\n| 离线验证 | offline loop drill 验证回滚与恢复路径 | 很少验证关键闭环路径是否真的跑通 |\n\n## 快速开始\n\n如果你第一次使用，建议从这三种方式开始：\n\n```text\n$virtual-intelligent-dev-team 帮我接管这次重构，并给出可执行分工。\n$virtual-intelligent-dev-team /auto setup 这个项目级迁移。\n$virtual-intelligent-dev-team 判断当前版本是否可以 release。\n```\n\n对应的理解方式是：\n\n- 不带 `/auto`\n  - 走手动模式，适合高风险任务和需要逐轮确认的场景\n- 带 `/auto setup`\n  - 先建立自动化状态和恢复锚点\n- 再执行 `/auto go`\n  - 进入自动执行阶段\n\n## 适合与不适合\n\n更适合：\n\n- 复杂研发任务\n- 跨产品与研发的交付协同\n- 需要多轮优化、恢复和发布治理的工作\n\n不太适合：\n\n- 纯商业战略\n- 融资、定价、泛咨询\n- 非软件交付型的轻量一次性问题\n\n## 目录结构\n\n```text\nvirtual-intelligent-dev-team/\n├── SKILL.md\n├── README.md\n├── VERSION\n├── LICENSE\n├── agents/\n├── assets/\n├── docs/\n├── evals/\n├── references/\n├── scripts/\n└── tests/\n```\n\n目录职责分层：\n\n- `SKILL.md`\n  - 运行时契约、触发边界、主流程\n- `docs/`\n  - 面向维护者与开源使用者的说明文档\n- `references/`\n  - 路由规则、playbook、schema、真源细则\n- `assets/`\n  - 模板、样例、卡片\n- `scripts/`\n  - 校验、导出、自动运行、恢复、发布辅助脚本\n- `tests/`\n  - 语义回归与契约测试\n\n## 快速入口\n\n- 使用说明：\n  - [docs/usage-guide.md](docs/usage-guide.md)\n- 设计理念：\n  - [docs/design-philosophy.md](docs/design-philosophy.md)\n- 文档索引：\n  - [docs/README.md](docs/README.md)\n\n如果你想先上手：\n\n- 读 `README.md`\n- 再读 `docs/usage-guide.md`\n\n如果你想先理解设计：\n\n- 读 `docs/design-philosophy.md`\n- 再读 `SKILL.md`\n\n## 运行流程图\n\n```mermaid\nflowchart TD\n    A[收到复杂软件任务] --\u003e B{是否显式输入 /auto}\n    B --\u003e|否| C[手动模式]\n    B --\u003e|是| D[\"/auto setup\"]\n    D --\u003e E[建立 automation state]\n    E --\u003e F[\"/auto go 或 resume\"]\n    F --\u003e G[自动执行入口]\n\n    C --\u003e H[识别任务类型 / 风险 / 技术栈 / Git 与 process 信号]\n    G --\u003e H\n\n    H --\u003e I{是否大型改造 / 迁移 / 先规划}\n    I --\u003e|是| J[\"plan-first-build 前置规划和 progress anchor\"]\n    J --\u003e H\n    I --\u003e|否| K{是否窄实现或 bugfix}\n    K --\u003e|是| L[quick-slice-deliver]\n    K --\u003e|否| M[选择一个 lead agent]\n\n    M --\u003e N{是否需要 assistant / governance / Git guardrail}\n    N --\u003e|是| O[加载协同治理或 Git 轨道]\n    N --\u003e|否| P[保持轻量路由]\n    O --\u003e Q{选择最小 workflow bundle}\n    P --\u003e Q\n    L --\u003e Q\n\n    Q --\u003e|产品定义到交付| R[product-spec-deliver]\n    Q --\u003e|多轮优化或候选比较| S[bounded iteration]\n    Q --\u003e|反复失败或根因排查| T[root-cause-remediate]\n    Q --\u003e|分轮内测或用户递增| U[beta-feedback-ramp]\n    Q --\u003e|发版提交或正式验收| V[ship-hold-remediate]\n    Q --\u003e|已发布反馈回流| W[post-release-close-loop]\n    Q --\u003e|审计后修复| X[audit-fix-deliver]\n    Q --\u003e|发布安全回滚分支策略| Y[govern-change-safely]\n    Q --\u003e|AGENTS 或项目知识沉淀| Z[capture-project-knowledge]\n    Q --\u003e|常规复杂任务| AA[统一执行与验证]\n\n    R --\u003e AB{是否面向 code release Git remediation}\n    S --\u003e AB\n    T --\u003e AB\n    U --\u003e AB\n    V --\u003e AC{release gate 结论}\n    W --\u003e AB\n    X --\u003e AB\n    Y --\u003e AB\n    AA --\u003e AB\n    Z --\u003e AK[统一输出 + evidence + next step + resume anchor]\n\n    AC --\u003e|ship| W\n    AC --\u003e|hold| AD[生成 remediation brief 或 next iteration brief]\n    AD --\u003e AB\n\n    AB --\u003e|是| AE[Harness constraint gate]\n    AE --\u003e AF[Team Engine Lite]\n    AF --\u003e AG[DeliveryCycleReport]\n    AG --\u003e AH{Verifier verdict}\n    AH --\u003e|pass| AK\n    AH --\u003e|fail| AI[RemediationPatch 加有界重试]\n    AI --\u003e AF\n    AH --\u003e|hold| AJ[升级给 Lead 或 Human 决策]\n    AJ --\u003e AK\n\n    AB --\u003e|否| AK\n```\n\n## 如何调用\n\n最常见的调用方式：\n\n```text\n$virtual-intelligent-dev-team 帮我接管这次重构，并给出可执行分工。\n$virtual-intelligent-dev-team /auto setup 这个项目级迁移。\n$virtual-intelligent-dev-team 判断当前版本是否可以 release。\n```\n\n如果你主要关心运行时规则，优先读：\n\n- `SKILL.md`\n- `references/runtime-routing-index.md`\n- `references/tooling-command-index.md`\n\n如果你主要关心维护和扩展，优先读：\n\n- `README.md`\n- `docs/README.md`\n\n## 校验命令\n\n项目级：\n\n```bash\npython3 validate.py --changed\n```\n\nskill 级：\n\n```bash\npython3 ../scripts/sync_virtual_intelligent_dev_team_version.py --check\npython3 ../scripts/sync_virtual_intelligent_dev_team_version.py\npython3 skill-forge/scripts/quick_validate.py ./virtual-intelligent-dev-team\npython3 -m unittest virtual-intelligent-dev-team.tests.test_routing_and_guardrails\npython3 virtual-intelligent-dev-team/scripts/validate_virtual_team.py --pretty\n```\n\n## 版本\n\n当前版本见 [VERSION](VERSION)。\n\n## 致谢与参考来源\n\n本项目的迭代优化模式部分参考了 [agency-agents](https://github.com/msitarzewski/agency-agents) 的设计思路，并在其基础上适配了本 skill 的闭环工作流、状态恢复与发布治理等能力。\n\n相关的模式提炼见 [references/bounded-iteration-patterns.md](references/bounded-iteration-patterns.md)。\n\n## License\n\n本项目使用 [MIT License](LICENSE)。\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffxbin%2Fvirtual-intelligent-dev-team","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ffxbin%2Fvirtual-intelligent-dev-team","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ffxbin%2Fvirtual-intelligent-dev-team/lists"}