# Ops Feature Dev

OPS on-demand: This skill should be used when the user asks to \"guided feature\"...

- Repository: https://github.com/Lifecycle-Innovations-Limited/claude-ops (547 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -a claude-code -y`
Codex: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -a codex -y`
Cursor: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -a cursor -y`
Gemini CLI: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops`

## Description

OPS on-demand: This skill should be used when the user asks to \"guided feature\", \"feature-dev\", or…

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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):

```bash
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 **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

The rest: https://github.com/Lifecycle-Innovations-Limited/claude-ops/blob/HEAD/claude-ops/skills/ops-feature-dev/SKILL.md