How do I install the Ops Feature Dev skill?

Run npx skillmds@latest add lifecycle-innovations-limited/ops-feature-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ops Feature Dev skill do?

OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or… It is listed under Coding & Dev Tools on SkillMD.

Is Ops Feature Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ops Feature Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ops Feature Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ops Feature Dev?

Lifecycle-Innovations-Limited (@lifecycle-innovations-limited) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ops Feature Dev by lifecycle-innovations-limited

Name: Ops Feature Dev
Rating: 4.2 (5 reviews)
Author: Lifecycle-Innovations-Limited

File contents

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 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.

---name: ops-feature-devdescription: OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or…---## Agent Teams supportIf `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is set, use **Agent Teams** whenfeature-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):```bashTeamCreate("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 (thedefault), or invoke `/feature-dev` inline via the Skill tool.# OPS ► FEATURE DEVLoad `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`.## RoutingIf `$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.

Frequently asked questions

Ops Feature Dev