Ops Feature Dev logo

Ops Feature Dev

Organization
Lifecycle-Innovations-Limited
ops-feature-dev

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

Overview

PublisherLifecycle-Innovations-Limited
Repositoryclaude-ops
Skill nameops-feature-dev
Stars
543
Forks
64
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Lifecycle-Innovations-Limited on GitHub. Read the source before you install it.

Installation

Install the Ops Feature Dev AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git /tmp/claude-ops
mkdir -p .claude/skills
cp -r /tmp/claude-ops/claude-ops/skills/ops-feature-dev .claude/skills/ops-feature-dev
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ops Feature Dev in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ops Feature Dev on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ops Feature Dev is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  • 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

What does the Ops Feature Dev AI skill do?

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

Why use Ops Feature Dev on TypingMind?

Because you install it once and use it with any model. Ops Feature Dev is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ops Feature Dev in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ops Feature Dev?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ops Feature Dev?

As many as you like. As long as a model supports skills, you can use Ops Feature Dev with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ops Feature Dev AI skill free?

Yes. It is published on GitHub by Lifecycle-Innovations-Limited under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇