Skip to content
Skills Library
Programming · Building & coding

ops-feature-dev

/ops-feature-dev

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

Repository
claude-ops ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Triggers from the description

guided feature\feature-dev\

Arguments

/ops-feature-dev [feature description]
Original author description

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

How it works

  1. Agent Teams support
  2. When to use
  3. Routing
  4. Integration notes
Original SKILL.md headings · 49 lines, 298 words
SKILL.md preview
---
name: ops-feature-dev
description: "OPS on-demand: This skill should be used when the user asks to \"guided feature\", \"feature-dev\", or…"
argument-hint: '[feature description]'
allowed-tools:
  - Skill
  - Agent
  - AskUserQuestion
  - TodoWrite
  - Read
  - TeamCreate
  - SendMessage
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):

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

Versions

The database has no other skills named ops-feature-dev.

Database snapshot: 13.11.2026 · package version 1a87dd778760 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flow
    OPS on-demand: This skill should be used when the user asks to \"/ops:flow\", \"dev lifecycle\", or \"where…
  • 100ops-settings
    OPS on-demand: This skill should be used when the user asks to \"update credentials\", \"ops settings\", or…
  • 100feature-dev
    Guided feature development — explore codebase → clarify requirements → design architecture → implement → review. Use when implementing new features affecting multiple modules.
  • 100feature-dev
    Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
  • 95feature-dev
    Feature development workflow with exploration, architecture, implementation, and review phases. Use for implementing new features or significant changes.
  • 95feature-dev
    Feature development workflow with exploration, architecture, implementation, and review phases. Use for implementing new features or significant changes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.