ops-feature-dev
GitHub作为 feature-dev 插件的薄路由器，支持在代理团队模式下并行处理功能开发阶段。用于引导探索、架构和实现流程，协调多代理协作并管理任务分发。
Trigger Scenarios
Install
npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -y
SKILL.md
Frontmatter
{
"name": "ops-feature-dev",
"effort": "medium",
"maxTurns": 40,
"description": "OPS on-demand: This skill should be used when the user asks to \"guided feature\", \"feature-dev\", or…",
"allowed-tools": [
"Skill",
"Agent",
"AskUserQuestion",
"TodoWrite",
"Read",
"TeamCreate",
"SendMessage"
],
"argument-hint": "[feature description]"
}
Agent Teams support
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when
feature-dev phases fan out in parallel (e.g. explore + architect, or implement +
review). This enables:
- Phase agents share findings mid-flight (explore surfaces a constraint → architect adjusts before implementation starts)
- You can steer priorities in real time ("finish API contract first, then UI")
- Agents report progress as each phase completes
Team setup (only when the flag is enabled, and only for genuinely parallel phases):
TeamCreate("feature-dev-lifecycle")
Agent(team_name="feature-dev-lifecycle", name="phase-explore", ...)
Agent(team_name="feature-dev-lifecycle", name="phase-architect", ...)
Steer with SendMessage / broadcast; share work via TaskCreate/TaskUpdate.
If the flag is NOT set, fall back to standard fire-and-forget subagents (the
default), or invoke /feature-dev inline via the Skill tool.
OPS ► FEATURE DEV
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
Thin router into the feature-dev companion plugin. Do not re-implement its phases here.
When to use
- Ad-hoc repos (no
.planning/): optional structured alternative to jumping straight into/flow build. - Project repos (
.planning/present): run beforegsd-execute-phasewhen you want exploration + architecture + clarifying questions; execution still canonical via GSD. - Review: gstack
/reviewandgsd-code-reviewstay canonical; feature-dev Phase 6 is available via explicit/feature-devor auto-swap tofeature-dev:code-reviewer.
Routing
If $ARGUMENTS is empty, invoke /feature-dev with no args (discovery phase).
Otherwise invoke /feature-dev $ARGUMENTS via the Skill tool.
Integration notes
- Requires the feature-dev plugin installed (
/ops:setupStep 2c or/plugin install feature-dev). - Specialist auto-swap (
feature-dev:code-*) is handled bybin/ops-suggest-specialized-agentwhen the plugin is present. - Does not replace
/flow build,/review, orgsd-execute-phase— it overlays them.
Version History
-
6f1e3e0
Current 2026-08-27 09:31
优化专家发现上下文延迟加载，修复文件竞态条件及缺失能力索引时的错误处理，恢复市场发布标识并清理路由自引用。
- 64bad13 2026-08-12 09:00
