Token导航 LogoToken导航

Agent Skill · 研究检索

subagent-driven-development(子 Agent 驱动开发)

subagent-driven-development 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

subagent-driven-development 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 6,694。

总安装 21,270周安装 587GitHub Stars 公开资料未说明下载 7,869核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:subagent-driven-development(子 Agent 驱动开发)
来源仓库:https://github.com/chunkytortoise/enterprisehub
仓库路径:skills/subagent-driven-development
安装命令:
npx skills add chunkytortoise/enterprisehub --skill "subagent-driven-development"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add chunkytortoise/enterprisehub --skill "subagent-driven-development"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于驱动子 Agent 完成特定领域任务开发。适合按角色分工(如测试、文档、UI)分配职责。使用时需定义每个子 Agent 的能力边界与输入规范。避免过度拆分导致通信开销增加。subagent-driven-development 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

建议设置主 Agent 作为协调者汇总结果并做最终决策。

来源仓库内路径:skills/subagent-driven-development

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add chunkytortoise/enterprisehub --skill "subagent-driven-development…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

subagent-driven-development 怎么安装?

在终端执行 npx skills add chunkytortoise/enterprisehub --skill "subagent-driven-development"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

subagent-driven-development 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

subagent-driven-development 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

subagent-driven-development 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

subagent-driven-development 用的人多吗?

公开数据是累计安装 21,270 次,近一周安装 587 次,下载 7,869 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

subagent-driven-development 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
subagent-driven-development

子 Agent 驱动开发 · 本页

21,270—权限未标注MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
Subagent-Driven Development
description
This skill should be used when coordinating "multiple specialized agents", "complex workflow orchestration", "autonomous development teams", "agent collaboration", "distributed task management", or when managing sophisticated multi-agent development processes.
version
2.0.0

Subagent-Driven Development: Multi-Agent Coordination

Overview

This skill provides comprehensive patterns for orchestrating multiple specialized agents in complex development workflows. It enables sophisticated coordination between autonomous agents, each with specific expertise and responsibilities.

When to Use This Skill

Use this skill when implementing:

  • Multi-agent development workflows with specialized roles
  • Complex task orchestration requiring multiple expertise areas
  • Autonomous development teams with agent coordination
  • Parallel workflow execution with dependency management
  • Agent collaboration patterns for complex problems
  • Distributed task management across multiple agents
  • Quality assurance through specialized reviewers

Quick Start

1. Basic Multi-Agent Workflow

from subagent_framework import WorkflowOrchestrator, Task, AgentType, Priority

# Create orchestrator
orchestrator = WorkflowOrchestrator()

# Register specialized agents
orchestrator.register_agent(ArchitectAgent("architect_001"))
orchestrator.register_agent(DeveloperAgent("developer_001"))
orchestrator.register_agent(TesterAgent("tester_001"))

# Define task workflow
tasks = [
    Task(
        id="design_001",
        title="Design System Architecture",
        agent_type=AgentType.ARCHITECT,
        priority=Priority.HIGH,
        input_data={'requirements': {...}}
    ),
    Task(
        id="implement_001",
        title="Implement Feature",
        agent_type=AgentType.DEVELOPER,
        priority=Priority.HIGH,
        dependencies=["design_001"],  # Depends on architect
        input_data={'specification': {...}}
    ),
    Task(
        id="test_001",
        title="Test Implementation",
        agent_type=AgentType.TESTER,
        priority=Priority.MEDIUM,
        dependencies=["implement_001"],  # Depends on developer
        input_data={'test_type': 'integration'}
    )
]

# Execute workflow
results = await orchestrator.execute_workflow(tasks)

2. Parallel Agent Execution

# Create tasks that can run in parallel
parallel_tasks = [
    Task(
        id="frontend_dev",
        title="Develop Frontend",
        agent_type=AgentType.DEVELOPER,
        dependencies=["design_001"],
        input_data={'component': 'ui'}
    ),
    Task(
        id="backend_dev",
        title="Develop Backend API",
        agent_type=AgentType.DEVELOPER,
        dependencies=["design_001"],
        input_data={'component': 'api'}
    ),
    Task(
        id="database_dev",
        title="Develop Database Schema",
        agent_type=AgentType.DEVELOPER,
        dependencies=["design_001"],
        input_data={'component': 'database'}
    )
]

# These tasks will execute in parallel (same dependency level)
results = await orchestrator.execute_workflow(parallel_tasks)

3. Quality Gate Workflow

# Add quality gate for production-critical code
quality_workflow = [
    Task(id="develop", agent_type=AgentType.DEVELOPER, ...),
    Task(
        id="security_review",
        agent_type=AgentType.SECURITY,
        dependencies=["develop"],
        priority=Priority.CRITICAL,
        input_data={'scan_type': 'comprehensive'}
    ),
    Task(
        id="quality_gate",
        agent_type=AgentType.QUALITY_GATE,
        dependencies=["security_review"],
        priority=Priority.CRITICAL,
        input_data={'approval_required': True}
    )
]

results = await orchestrator.execute_workflow(quality_workflow)

Core Components

Agent Types

See: reference/agent-taxonomy.md for complete agent type specifications

Available Agent Types:

  • ARCHITECT - System design and architecture
  • DEVELOPER - Code implementation
  • TESTER - Testing and quality assurance
  • REVIEWER - Code review and analysis
  • SECURITY - Security analysis and hardening
  • PERFORMANCE - Performance optimization
  • QUALITY_GATE - Quality validation and approval
  • COORDINATOR - Workflow coordination

Task Management

See: reference/task-management.md for complete task data structures

Key Task Properties:

  • agent_type - Which agent handles this task
  • priority - Task priority (LOW to EMERGENCY)
  • dependencies - Tasks that must complete first
  • input_data - Task-specific input parameters
  • metadata - Additional context and configuration

Workflow Orchestrator

Central coordination system for multi-agent workflows

Key Methods:

  • register_agent() - Add agent to available pool
  • execute_workflow() - Execute task workflow
  • get_workflow_status() - Monitor progress
  • handle_agent_failure() - Error recovery

Common Workflows

Sequential Pipeline

Linear workflow with strict dependencies:

Architect → Developer → Tester → Reviewer → Quality Gate

See: reference/orchestration-patterns.md#sequential-pipeline

Parallel Fan-Out

Multiple agents working independently:

                 ┌─> Developer A (Frontend)
Architect ──────┼─> Developer B (Backend)
                 └─> Developer C (Database)
                           ↓
                      [Integration]

See: reference/orchestration-patterns.md#parallel-fan-out

Iterative Refinement

Progressive improvement through feedback loops:

Developer → Reviewer → [Feedback] → Developer → Reviewer → [Approved]

See: reference/orchestration-patterns.md#iterative-refinement

Orchestration Patterns

Complete patterns: reference/orchestration-patterns.md

Pattern Selection Guide

Workflow TypeRecommended PatternAgents Needed
Feature DevelopmentSequential PipelineArchitect, Developer, Tester, Quality Gate
Independent ComponentsParallel Fan-OutMultiple Developers, Coordinator
Critical Production CodeMulti-Stage ReviewDeveloper, Security, Performance, Reviewer
Optimization TasksIterative RefinementDeveloper, Performance, Reviewer
Security VulnerabilitiesEmergency Fast-TrackSecurity, Developer, Tester

Error Handling

Retry Strategy

task = Task(
    id="task_001",
    title="Implement Feature",
    agent_type=AgentType.DEVELOPER,
    priority=Priority.HIGH,
    max_retries=3,  # Retry up to 3 times
    input_data={...}
)

Fallback Agents

# Register multiple developer agents for fallback
orchestrator.register_agent(DeveloperAgent("dev_primary"))
orchestrator.register_agent(DeveloperAgent("dev_fallback_1"))
orchestrator.register_agent(DeveloperAgent("dev_fallback_2"))

# Orchestrator automatically uses fallback if primary fails

See: reference/orchestration-patterns.md#error-handling-patterns

Monitoring and Status

Get Workflow Status

status = orchestrator.get_workflow_status(workflow_id)

print(f"Progress: {status['progress']['percentage']}%")
print(f"Completed: {status['progress']['completed']}/{status['progress']['total']}")
print(f"Active Agents: {status['active_agents']}")

Monitor Agent Health

for agent_id, agent_status in status['agent_details'].items():
    print(f"{agent_id}: {agent_status['status']}")
    if agent_status['current_task']:
        print(f"  Working on: {agent_status['current_task']}")

Real Estate Platform Example

Complete example: examples/real-estate-workflow.py

async def create_property_matching_workflow():
    """Multi-agent workflow for property matching feature."""
    orchestrator = WorkflowOrchestrator()

    # Register agents
    orchestrator.register_agent(ArchitectAgent("architect_001"))
    orchestrator.register_agent(DeveloperAgent("developer_001"))
    orchestrator.register_agent(DeveloperAgent("developer_002"))
    orchestrator.register_agent(TesterAgent("tester_001"))
    orchestrator.register_agent(QualityGateAgent("quality_gate_001"))

    # Define workflow
    workflow = [
        # Phase 1: Architecture
        Task(
            id="arch_001",
            title="Design Property Matching System",
            agent_type=AgentType.ARCHITECT,
            priority=Priority.HIGH,
            input_data={'requirements': {'ai_integration': True}}
        ),

        # Phase 2: Parallel Development
        Task(
            id="api_dev",
            title="Develop Matching API",
            agent_type=AgentType.DEVELOPER,
            dependencies=["arch_001"],
            input_data={'framework': 'FastAPI'}
        ),
        Task(
            id="model_dev",
            title="Develop Data Models",
            agent_type=AgentType.DEVELOPER,
            dependencies=["arch_001"],
            input_data={'orm': 'SQLAlchemy'}
        ),

        # Phase 3: Testing
        Task(
            id="integration_test",
            title="Integration Testing",
            agent_type=AgentType.TESTER,
            dependencies=["api_dev", "model_dev"],
            input_data={'coverage_target': 0.80}
        ),

        # Phase 4: Quality Gate
        Task(
            id="quality_gate",
            title="Production Approval",
            agent_type=AgentType.QUALITY_GATE,
            dependencies=["integration_test"],
            priority=Priority.CRITICAL
        )
    ]

    # Execute
    results = await orchestrator.execute_workflow(workflow)
    return results

Best Practices

  1. Clear Agent Responsibilities: Each agent should have well-defined, non-overlapping responsibilities
  2. Proper Dependency Management: Ensure task dependencies are correctly specified and enforced
  3. Error Handling: Implement robust error handling and retry mechanisms
  4. Status Monitoring: Provide comprehensive status monitoring and reporting
  5. Resource Management: Prevent resource contention and ensure efficient agent utilization
  6. Quality Gates: Implement quality validation at appropriate workflow stages
  7. Scalability: Design for horizontal scaling of agent instances

Advanced Usage

For advanced multi-agent orchestration scenarios, see:

  • reference/agent-taxonomy.md - Complete agent type specifications
  • reference/task-management.md - Task and workflow state management
  • reference/orchestration-patterns.md - Advanced coordination patterns
  • examples/real-estate-workflow.py - Real Estate platform workflows
  • examples/emergency-workflow.py - Emergency fast-track patterns
  • scripts/workflow-monitor.py - Monitoring and observability tools

Troubleshooting

Agents Not Executing Tasks

Cause: No registered agents matching task's agent_type Solution: Ensure agents are registered before workflow execution

Circular Dependencies

Cause: Task A depends on Task B which depends on Task A Solution: Use dependency resolver to validate task graph before execution

Workflow Stuck

Cause: Agent failed but retry limit not reached Solution: Check agent logs, increase retry limit or add fallback agents

Quick Reference

OperationCommand
Register agentorchestrator.register_agent(agent)
Execute workflowawait orchestrator.execute_workflow(tasks)
Get statusorchestrator.get_workflow_status(workflow_id)
Create taskTask(id, title, agent_type, priority, input_data)
Add dependencyTask(..., dependencies=["task_id"])

Version: 2.0.0 (Token-Optimized) Original: 1,395 lines Optimized: ~400 lines (71% reduction) Full Documentation: See reference/ directory

平台分布

windsurf

27.7%
按下载量换算2,180

OpenCode

21.69%
按下载量换算1,707

Codex

17.39%
按下载量换算1,368

Claude Code

11.94%
按下载量换算940

Antigravity

7.1%
按下载量换算559

Gemini CLI

2.88%
按下载量换算227

安全审计

暂无安全审计结果可展示。

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills