agentCLAWHUBUnverified

Virtual Intelligent Dev Team

Route complex software work with bounded, evidence-backed loops. Skill: Virtual Intelligent Dev Team Owner: fxbin Summary: Route complex software work with bounded, evidence-backed loops. Tags: latest:0.1.2 Version history: v0.1.2 | 2026-08-08T07:46:04.117Z | auto Version 0.1.2 of virtual-intelligent-dev-team - No functional or documentation changes detected; SKILL.md remains unchanged. - This release consolidates the current architecture and workflows without introducing new feat

OpenClaw

Rank

62

Safety

84

Downloads

1.4k

Updated

Oct 10, 2026

Version

0.1.2

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor
Clawhubvendor · observed Oct 10, 2026
Protocol compatibility
OpenClawcompatibility · observed Oct 10, 2026
Adoption signal
1.4K downloadsadoption · observed Oct 10, 2026
Latest release
0.1.2release · observed Aug 8, 2026
Handshake status
UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s177x7bk3bp1n32y264k0ewmhs8859wb:virtual-intelligent-dev-team
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-fxbin-virtual-intelligent-dev-team/snapshot"

Documentation

CLAWHUB

152,260 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: virtual-intelligent-dev-team
archetype: router
description: Bounded work-loop router for complex software tasks. Routes to the smallest defensible workflow with one semantic lead from 8 specialists (Java Virtuoso, Sentinel Architect, Technical Trinity, Code Audit Council, Git Workflow Guardian, World-Class Product Architect, Data Pipeline Guardian, API Contract Sentinel), attaches copilots only when useful, asks intent-confirmation for fuzzy ideas, and closes with verifiable evidence.
---

# Virtual Intelligent Dev Team

Route complex software work into the smallest defensible delivery workflow, keep one semantic lead, and close the task with verifiable evidence and a resume anchor.

## Positioning

This skill is a bounded work-loop router for complex tasks. Routing is one of its closures; the full set is six closure layers, one delivery subgraph, and one optional stage-council overlay:

1. `Planning closure`
   - Large rewrites, migrations, and project-wide transformations get a lightweight analysis / plan / progress pack before implementation.
2. `Routing closure`
   - Work is routed across lead, assistant, governance, and process tracks based on task shape, risk, stack, and workflow signals.
3. `Delivery closure`
   - Narrow feature and bug-fix slices use a quick slice brief, durable project context, delivery status, targeted verification, and self-review.
4. `Iteration closure`
   - Optimization loops preserve baseline, round memory, self-feedback, `keep / retry / rollback / stop`, `pivot`, and `resume`.
5. `Release closure`
   - Release readiness uses a formal `ship` / `hold` gate and bootstraps the next remediation loop when needed.
6. `Drill closure`
   - Offline drills verify rollback, resume, and release-gate bootstrap paths.
Delivery subgraph:

- `Team Engine Lite`(Delivery closure 内子图,非独立层)
   - Code-facing delivery uses Worker / Verifier separation, max-cycle retry, remediation patch, controlled real subagent runtime eligibility, external-agent soft orchestration fallback, and a DeliveryCycleReport before Lead acceptance.
   - Verifier 独立性由"禁止上游预判下游"硬约束(P0-3)保证,而非独立成层。详见 `references/team-engine-lite-protocol.md` 和 `references/verifier-extraction-guide.md`。
Optional overlay:

- `Stage council overlay`
  - Product discovery and prototype design can expand into phase-level councils under `World-Class Product Architect` without replacing the top-level lead, workflow bundle, or Team Engine Lite verification.

Runtime rule:

- When routing alone is not enough, return the smallest matching workflow bundle and resume anchor instead of inventing a new ceremony.

## Routing goal

Route complex software requests into the smallest defensible workflow bundle, keep one semantic lead, and attach only assistants, governance, and artifacts that materially improve delivery fidelity.

## Trigger cues

- multi-domain software delivery
- fuzzy ideas where product opportunity, prototype exploration, technical feasibility, architecture risk, or de

docs/README.md

# Virtual Intelligent Dev Team Docs

`docs/` 同时承担公开站点和维护者文档,但两者职责不同:

- 五个 HTML 页面面向浏览者,构成 GitHub Pages 静态站。
- Markdown 文档面向使用者与维护者,解释操作方式、设计理念和版本变化。
- 运行时规则仍以 `../SKILL.md` 和 `../references/` 为真源。

## 公开站点

| 页面 | 主要内容 |
| --- | --- |
| [index.html](index.html) | 定位、核心闭环、最短上手路径 |
| [architecture.html](architecture.html) | 六层 Closure、Team Engine Lite、runtime 与 12 个 Workflow Bundles |
| [engineering.html](engineering.html) | Harness、标准交接对象、反熵治理与完成证据 |
| [agents.html](agents.html) | 8 个专家角色、路由边界与两个 Stage Council |
| [matrix.html](matrix.html) | 14 维能力对比、适用边界与取舍 |

所有页面共享:

- `assets/site.css`:视觉 tokens、布局、组件、响应式与可访问性样式
- `assets/site.js`:移动端导航、复制按钮和轻量页面状态

站点不使用构建工具、CDN、远程字体或前端框架。`deck.html` 及其专用资源已经退役;演示内容已归并进五个正式页面,不保留兼容入口。

## GitHub Pages 部署

本 skill 会通过仓库级发布 workflow 以 subtree 形式发布到独立仓库
`fxbin/virtual-intelligent-dev-team`。subtree 发布后,
`.github/workflows/pages.yml` 位于目标仓库根目录,并把 `./docs` 上传为 Pages artifact。
该流程不执行 Jekyll 构建,因此不需要 `.nojekyll`。

预期公开地址:

- <https://fxbin.github.io/virtual-intelligent-dev-team/>

注意:GitHub 的 `blob/.../docs/index.html` 页面只显示 HTML 源码,不会渲染站点;必须访问 Pages 地址。第一次启用时,目标仓库的 **Settings → Pages → Source** 需要允许 **GitHub Actions**。workflow 成功运行前,不应宣称线上站点已部署。

## 本地预览

从独立 skill 仓库根目录运行:

```bash
python -m http.server 8000
```

访问 <http://localhost:8000/docs/>。

从 `skill-hub` 仓库根目录运行同一命令时,访问:

<http://localhost:8000/virtual-intelligent-dev-team/docs/>

不要直接用 `file://` 作为最终验收方式;本地 HTTP 能更接近 Pages 的路径与资源加载行为。

## 推荐阅读顺序

第一次使用:

1. [../README.md](../README.md)
2. [usage-guide.md](usage-guide.md)
3. [index.html](index.html)

理解设计与维护:

1. [design-philosophy.md](design-philosophy.md)
2. [architecture.html](architecture.html)
3. [engineering.html](engineering.html)
4. [../SKILL.md](../SKILL.md)

版本变化:

- [release-notes.md](release-notes.md)

## 文档更新规则

- 行为、路由或协议变化先改真源,再同步公开 HTML 和回归覆盖。
- 五个页面的公共视觉或交互只在 `assets/site.css` / `assets/site.js` 修改。
- 删除或重命名公开页面时,同步发布脚本、站内导航、README 与测试。
- 不把 `SKILL.md` 扩写成手册;详细解释留在 `references/` 或 `docs/`。
- 每次修改本 skill 都必须更新 `VERSION` 并通过 `quick_validate`。

## 运行时真源

- `../SKILL.md`
- `../references/playbook-index.md`
- `../references/agent-catalog.md`
- `../references/workflow-bundles.md`
- `../references/team-engine-lite-protocol.md`
- `../references/*.schema.json`

公开站点负责解释和导航,不替代上述运行时契约。

README.md

# Virtual Intelligent Dev Team

[![Version](https://img.shields.io/badge/version-v6.0.19-8b5cf6?style=flat-square)](./VERSION)
[![License](https://img.shields.io/badge/license-MIT-10b981?style=flat-square)](./LICENSE)
[![Status](https://img.shields.io/badge/status-production--ready-f59e0b?style=flat-square)]()
[![Archetype](https://img.shields.io/badge/archetype-router-06b6d4?style=flat-square)](./SKILL.md)
[![Agents](https://img.shields.io/badge/specialist_agents-8-3b82f6?style=flat-square)](./references/agent-catalog.md)
[![Closures](https://img.shields.io/badge/closure_layers-6-a78bfa?style=flat-square)](https://fxbin.github.io/virtual-intelligent-dev-team/architecture.html)
[![Languages](https://img.shields.io/badge/language_profiles-13-10b981?style=flat-square)](./references/language-profiles.yaml)
[![Python](https://img.shields.io/badge/python-3.8+-3776ab?style=flat-square&logo=python&logoColor=white)]()

> **面向复杂软件工作的闭环协调层**:用六层闭环承接专家路由 · 计划 · 执行 · 迭代 · Beta · Release · Feedback,并在 Delivery closure 内嵌 Team Engine Lite 对抗式验收,以工程约束门禁 · 反熵治理 · 自优化循环保障交付质量。
> 适合接手"单个专家已经不够、单轮回答也不够"的复杂软件任务。

---

## 在线站点

> 文档站使用纯静态 HTML/CSS/JS,可由独立仓库的 GitHub Actions 直接部署到 GitHub Pages。

| 入口 | 说明 | 链接 |
| --- | --- | --- |
| 落地页 | 项目总览:定位 / 痛点 / 六层闭环 / Team Engine Lite / 8 Agent / Quick Start | [fxbin.github.io/virtual-intelligent-dev-team](https://fxbin.github.io/virtual-intelligent-dev-team) |
| 闭环架构 | 六层 Closure、Delivery 子图与 Stage Council overlay | [Architecture](https://fxbin.github.io/virtual-intelligent-dev-team/architecture.html) |
| 工程化四支柱 | Harness 门禁 · Team Engine Lite · 反熵治理 · 自优化循环 | [Engineering](https://fxbin.github.io/virtual-intelligent-dev-team/engineering.html) |
| 8 Agent 角色图谱 | 8 个专家的职责、领域与证据要求 | [Agents](https://fxbin.github.io/virtual-intelligent-dev-team/agents.html) |
| 能力矩阵对比 | 14 个维度对比本项目与普通多专家提示词 | [Matrix](https://fxbin.github.io/virtual-intelligent-dev-team/matrix.html) |

> 独立仓库本地预览:运行 `python -m http.server 8000` 后访问 `http://localhost:8000/docs/`。在 `skill-hub` 根目录启动时,访问 `/virtual-intelligent-dev-team/docs/`。

---

## 项目定位

`virtual-intelligent-dev-team` 是一个面向复杂软件工作的智能协作项目。

它不只是"专家角色路由器",而是把研发、产品、分轮内测、技术治理、发布门禁、显式 `/auto` 自动运行,以及状态驱动恢复,收拢成一个可持续迭代的闭环工作流。

一句话说:

它适合接手"单个专家已经不够、单轮回答也不够"的复杂软件任务。

---

## 🚀 5 分钟快速上手

### 0. 运行维护脚本前安装依赖

直接调用 skill 不需要额外安装;如果要运行路由、schema、遥测或回归脚本,先执行:

```bash
python -m pip install -r requirements.txt
```

`requirements.txt` 统一声明 `jsonschema` 与 `PyYAML`,避免不同维护环境依赖隐式存在。

### 1. 最简单的使用场景(小切片交付)

```bash
# 场景:实现一个小功能或修复一个 bug
/virtual-intelligent-dev-team 实现用户登录功能的邮箱验证
```

**会发生什么:**
- 自动路由到 `Technical Trinity`(通用后端工程专家)
- 生成 Quick Slice Brief(包含目标、范围、验收条件)
- 实现代码并保留 delivery status 和完成证据
- 给出下一步建议(测试、提交、发布门禁等)

### 2. 模糊想法确认(意图确认)

```bash
# 场景:有一个想法,不确定该从产品、原型、技术还是架构入手
/virtual-intelligent-dev-team 我想做一个用户画像功能
```

**会发生什么:**
- 先给出 5 个确认方向选项:
  - `product-opportunity`:产品机会验证
  - `prototype-exploration`:原型探索
  - `technical-feasibility`:技术可行性评估
  - `architecture-risk`:架构风险分析
  - `delivery-plan`:交付拆解
- 用

_meta.json

{
  "ownerId": "kn73qh82zhjckby6wqrhe3ax2n80ckax",
  "slug": "virtual-intelligent-dev-team",
  "version": "0.1.2",
  "publishedAt": 1786175164117
}

references/agent-catalog.md

# Agent Catalog

Source of truth for each team member's scope, trigger patterns, and anti-patterns.

## 1. Java Virtuoso

- Core strengths: Java 21, Spring Boot 3.2+, JVM performance, concurrency strategy, migration from legacy Java APIs.
- Best triggers: `java`, `spring`, `jvm`, `gc`, `virtual threads`, `java upgrade`, `spring boot`.
- Typical tasks: backend implementation, performance tuning, Java refactors, Spring architecture, concurrency reviews.
- Avoid using as lead for: pure business strategy, pure UI design, generic Git-only tasks.
- Output bias: concrete Java decisions, production-ready implementation guidance, test strategy, migration notes.
- Constraints: 禁止建议 `java.util.Date`,统一使用 `java.time`;`Stream.parallel()` 改动必须附性能基准;公共 API 变更必须同时更新 OpenAPI 契约与回归测试;JVM 调优建议必须标注 GC 算法与目标停顿时间。
- Evidence requirements: 改动必须附 JVM 启动参数与运行时版本、受影响模块的回归测试结果;涉及启动耗时或吞吐时附 Spring Boot 启动基准。

## 2. Sentinel Architect (NB)

- Core strengths: high-risk change governance, staged execution, research-first delivery, safety rails for critical work.
- Best triggers: `high risk`, `critical`, `production-impacting`, `research first`, `migration with rollback`, `sensitive refactor`.
- Typical tasks: risky refactors, hotfix governance, phased modernization, conflict-heavy coordination.
- Avoid using as lead for: low-risk one-off fixes or straightforward single-step answers.
- Output bias: execution mode, risk gates, rollback thinking, decision checkpoints, auditability.
- Constraints: 不得跳过风险评估直接进入执行;不得在没有回滚方案的情况下推进生产高风险变更;不得在反复失败场景下继续猜测,必须转入根因排查;重大变更必须保留人工 sign-off 节点。
- Evidence requirements: 高风险变更需提供风险矩阵(影响面 / 回滚成本 / 监控信号)、分阶段执行计划与决策检查点、回滚策略与触发条件、上线前 checklist 与责任分工。

## 3. Technical Trinity

- Core strengths: general backend engineering, system design, implementation tradeoffs, reliability, DevSecOps-aware delivery.
- Best triggers: `system design`, `backend`, `api`, `service`, `python`, `go`, `node`, `rust`, `architecture`, `reliability`.
- Typical tasks: service design, module refactors, platform engineering, implementation planning, technical landing.
- Avoid using as lead for: pure market strategy, pricing, financing, or purely visual frontend redesign.
- Output bias: architecture choices, implementation slices, risk tradeoffs, operational concerns.
- Constraints: 架构变更必须给出模块/接口/边界影响范围;多语言实现建议必须落到 `language-profiles.yaml` 已注册的 profile;迁移与重构必须保留行为对等的回归证据;禁止把业务战略 / 融资 / 定价类请求路由到本 Agent。
- Evidence requirements: 通用工程任务需提供目标语言对应的 lint / test / build 命令(来自 `language-profiles.yaml`)、接口契约与现有调用方清单、回归测试结果或可运行验证脚本;架构改造场景额外需要模块地图或调用链证据。

## 4. Code Audit Council

- Core strengths: review, audit, security assessment, maintainability analysis, refactor prioritization.
- Best triggers: `review`, `audit`, `security review`, `pr review`, `code review`, `vulnerability`, `refactor assessment`.
- Typical tasks: bug/risk finding, PR review, hardening advice, quality grading, remediation prioritization.
- Avoid using as lead for: requests without code context or pure strategy discuss
Github ReposUpdated 19h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW
Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW
Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW
Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular

OPENCLAW

Machine-readable data

The same record, as JSON, for agents and crawlers.

{
  "facts": [
    {
      "factKey": "vendor",
      "category": "vendor",
      "label": "Vendor",
      "value": "Clawhub",
      "href": "https://clawhub.ai/fxbin/skills/virtual-intelligent-dev-team",
      "sourceUrl": "https://clawhub.ai/fxbin/skills/virtual-intelligent-dev-team",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-10T12:15:51.819Z",
      "isPublic": true
    },
    {
      "factKey": "protocols",
      "category": "compatibility",
      "label": "Protocol compatibility",
      "value": "OpenClaw",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-fxbin-virtual-intelligent-dev-team/contract",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-fxbin-virtual-intelligent-dev-team/contract",
      "sourceType": "contract",
      "confidence": "medium",
      "observedAt": "2026-10-10T12:15:51.819Z",
      "isPublic": true
    },
    {
      "factKey": "traction",
      "category": "adoption",
      "label": "Adoption signal",
      "value": "1.4K downloads",
      "href": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceUrl": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-10T12:15:51.819Z",
      "isPublic": true
    },
    {
      "factKey": "latest_release",
      "category": "release",
      "label": "Latest release",
      "value": "0.1.2",
      "href": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceUrl": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-08-08T07:46:04.117Z",
      "isPublic": true
    },
    {
      "factKey": "handshake_status",
      "category": "security",
      "label": "Handshake status",
      "value": "UNKNOWN",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-fxbin-virtual-intelligent-dev-team/trust",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-fxbin-virtual-intelligent-dev-team/trust",
      "sourceType": "trust",
      "confidence": "medium",
      "observedAt": null,
      "isPublic": true
    }
  ],
  "events": [
    {
      "eventType": "release",
      "title": "Release 0.1.2",
      "description": "Version 0.1.2 of virtual-intelligent-dev-team - No functional or documentation changes detected; SKILL.md remains unchanged. - This release consolidates the current architecture and workflows without introducing new features or fixes. - All existing routing, closure, and workflow mechanisms are preserved as previously documented.",
      "href": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceUrl": "https://clawhub.ai/fxbin/virtual-intelligent-dev-team",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-08-08T07:46:04.117Z",
      "isPublic": true
    }
  ]
}

Record generated Oct 10, 2026.

Sponsored

Ads related to Virtual Intelligent Dev Team and adjacent AI workflows.