Knowledge Ops
affaan-m/ECC
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).
Agent skill
Ops Feature Dev
by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or…
MITAuto-check passed
Install Ops Feature Dev
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .claude/skills/ops-feature-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .claude/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .agents/skills/ops-feature-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .agents/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .cursor/skills/ops-feature-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .cursor/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-feature-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .gemini/skills/ops-feature-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .gemini/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .github/skills/ops-feature-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .github/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-feature-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-feature-dev .opencode/skills/ops-feature-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ops-feature-dev" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-feature-dev into .opencode/skills/ops-feature-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-feature-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ops-feature-dev- GitHub stars
- 540
- Token cost
- ~661 tokens
- SKILL.md length
- 263 words
- Files
- 1
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or…
- Asks to guided feature
- SKILL.md covers Agent Teams support, When to use, Routing and Integration notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ops Feature Dev is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or…
Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.
When your agent uses it
- Asks to guided feature
Example prompts
- “guided feature”
- “feature-dev”
- “/ops-feature-dev”
Requirements
- Pre-approved tools (allowed-tools): Skill, Agent, AskUserQuestion, TodoWrite, Read, TeamCreate, SendMessage
What it can do on your machine
Read from SKILL.md and the folder at commit 6a4340b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
SkillAgentAskUserQuestionTodoWriteReadTeamCreateSendMessage
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ops Feature Dev loads about 661 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 263 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Lifecycle-Innovations-Limited/claude-ops at commit 6a4340b, republished under its MIT licence (© Lifecycle-Innovations-Limited). 263 words, ~661 tokens.
Download SKILL.mdSave it as
.claude/skills/ops-feature-dev/SKILL.md (or your agent's skills folder).- name
- ops-feature-dev
- 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]
- effort
- medium
- maxTurns
- 40
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.
© Lifecycle-Innovations-Limited, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in claude-ops/skills/ops-feature-dev of Lifecycle-Innovations-Limited/claude-ops.
Open the folder on GitHubat commit 6a4340b
Compare with similar skills
Ops Feature Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ops Feature Dev this skillLifecycle-Innovations-Limited/claude-ops | 540 | — | ~661 | Automated safety check: Pass | MIT | |
| Knowledge Opsaffaan-m/ECC | 275k | 2 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Research Opsaffaan-m/ECC | 275k | 2 repos | ~902 | Automated safety check: Pass | MIT | |
| Terminal Opsaffaan-m/ECC | 275k | 2 repos | ~750 | Automated safety check: Pass | MIT | |
| Messages Opsaffaan-m/ECC | 275k | 1 repos | ~724 | Automated safety check: Pass | MIT | |
| Email Opsaffaan-m/ECC | 275k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Research Ops
affaan-m/ECC
Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.
Terminal Ops
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
GitHub Ops
affaan-m/ECC
GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC.
More from Lifecycle-Innovations-Limited/claude-ops
All 67 skills in this repoOps Dash
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "ops dashboard", "pixel HQ", or…
Ops Gtm
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "go to market", "GTM plan", or…
Ops Marketing
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "klaviyo", "ads spend", or…
Ops Socials
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "tweet", "post to linkedin", or…
Ops Yolo
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "yolo mode", "run the business today"…
Ops Monitor
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "datadog", "APM alerts", or…
Questions about Ops Feature Dev
What does Ops Feature Dev do?
OPS on-demand: This skill should be used when the user asks to "guided feature", "feature-dev", or…. Ops Feature Dev is an agent skill from Lifecycle-Innovations-Limited/claude-ops.
When should I use Ops Feature Dev?
Ops Feature Dev fits situations like: asks to guided feature.
How do I install Ops Feature Dev in Claude Code?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-feature-dev in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-feature-dev in your project. Claude Code loads it when a task matches its description.
How do I install Ops Feature Dev in Codex?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a codex`. Or copy the skill folder (claude-ops/skills/ops-feature-dev in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-feature-dev in your project. Codex loads it when a task matches its description.
Can I use Ops Feature Dev in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-feature-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-feature-dev, .gemini/skills/ops-feature-dev, .github/skills/ops-feature-dev and .opencode/skills/ops-feature-dev in your project.
What does Ops Feature Dev need to run?
SKILL.md names no scripts, command-line tools or credentials: Ops Feature Dev is instructions for the agent only. Its frontmatter pre-approves these tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, TeamCreate, SendMessage.
Does Ops Feature Dev access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ops Feature Dev safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ops Feature Dev use?
Ops Feature Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ops Feature Dev use?
About 661 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ops Feature Dev?
Skills that share tags, products or a category with Ops Feature Dev: Knowledge Ops (affaan-m/ECC, 275k stars), Research Ops (affaan-m/ECC, 275k stars), Terminal Ops (affaan-m/ECC, 275k stars) and Messages Ops (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ops Feature Dev?
Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 540 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 7, 2026.
Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.