360 Secure SkillHub
360 安全技能中心

Lobster Subagent Dev

该 Skill 描述一套子智能体驱动的开发流程:先读取实施计划并拆解任务,再为每个任务分派全新子智能体完成实现、测试、提交与自检,随后依次通过规格审查和代码质量审查,全部任务完成后做最终整体审查并运行完整测试。还给出按任务复杂度选择模型以及处理子智能体状态(完成、带疑虑完成、缺上下文、受阻)的建议。

wangxiaofei860208-source
wangxiaofei860208-source
热度 39.89
最近更新 2026-05-11 17:40:03
分类:开发依赖:内部调用大模型应用场景:代码生成 / 代码审查 / 任务管理 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add lobster-subagent-dev
Metadata
name
lobster-subagent-dev
version
1.0.0
description
Subagent-driven development. Dispatch fresh subagent per task with 2-stage review (spec + quality). Cost-aware model routing. From Superpowers by Jesse Vincent.
author
Super Lobster 🦞
tags
["subagent","development","tdd","review","parallel"]
license
MIT

Lobster Subagent-Driven Development 🦞

Fresh subagent per task. Two-stage review. Ship with confidence.

Inspired by Superpowers by Jesse Vincent.

Core Principle

Fresh subagent per task + 2-stage review = high quality, fast iteration

Subagents never inherit session context. You construct exactly what they need. This preserves your own context for coordination work.

The Process

1. Read Plan → Extract Tasks

  • Read implementation plan once
  • Extract ALL tasks with full text
  • Create TodoWrite tracking

2. Per Task: Implementer → Spec Review → Quality Review

[Dispatch Implementer]
  ↓ (if questions → answer → re-dispatch)
[Implementer: implement + test + commit + self-review]
  ↓
[Dispatch Spec Reviewer]
  ↓ ❌ → Fix → Re-review
  ↓ ✅
[Dispatch Code Quality Reviewer]
  ↓ ❌ → Fix → Re-review
  ↓ ✅
[Mark task complete]
  ↓
[Next task...]

3. Final Review

After all tasks complete:

  • Dispatch final code reviewer for entire implementation
  • Verify all requirements met
  • Run full test suite

Model Selection

Task Type Model Why
1-2 files, complete spec Cheapest Mechanical
Multi-file integration Standard Needs judgment
Architecture/review Strongest Needs expertise

Agent Status Handling

Status Action
DONE Proceed to spec review
DONE_WITH_CONCERNS Read concerns, then decide
NEEDS_CONTEXT Provide context, re-dispatch
BLOCKED Change model / split task / escalate

Never

  • Skip reviews (spec OR quality)
  • Start quality review before spec passes
  • Let implementer self-review replace actual review
  • Move to next task while review has open issues
  • Dispatch multiple implementers in parallel (conflicts)