Agent Skills › Lifecycle-Innovations-Limited/claude-ops › ops-feature-dev

ops-feature-dev

GitHub

作为 feature-dev 插件的轻量级路由入口，引导功能开发流程。支持探索、架构、实现及审查等阶段，可结合 Agent Teams 实现并行协作与实时协调，适用于临时仓库或项目规划前的准备工作。

claude-ops/skills/ops-feature-dev/SKILL.md Lifecycle-Innovations-Limited/claude-ops

Trigger Scenarios

需要结构化功能开发流程时执行 gsd-execute-phase 前需探索或架构设计时启用 Agent Teams 进行并行阶段协作时

Install

npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -y

More Options

Non-standard path

npx skills add https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev -g -y

Use without installing

npx skills use Lifecycle-Innovations-Limited/claude-ops@ops-feature-dev

指定 Agent (Claude Code)

npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a claude-code -g -y

安装 repo 全部 skill

npx skills add Lifecycle-Innovations-Limited/claude-ops --all -g -y

预览 repo 内 skill

npx skills add Lifecycle-Innovations-Limited/claude-ops --list

SKILL.md

Frontmatter

{
    "name": "ops-feature-dev",
    "effort": "medium",
    "maxTurns": 40,
    "description": "Guided feature development — delegates to the feature-dev plugin's 7-phase workflow (explore, architect, implement, review). Use before ad-hoc builds or as pre-work before gsd-execute-phase.",
    "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

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 before gsd-execute-phase when you want exploration + architecture + clarifying questions; execution still canonical via GSD.
Review: gstack /review and gsd-code-review stay canonical; feature-dev Phase 6 is available via explicit /feature-dev or auto-swap to feature-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:setup Step 2c or /plugin install feature-dev).
Specialist auto-swap (feature-dev:code-*) is handled by bin/ops-suggest-specialized-agent when the plugin is present.
Does not replace /flow build, /review, or gsd-execute-phase — it overlays them.