feature-dev

A guided process for building new software features with several specialist coding agents working in stages.

In plain words
What is it for?
It is for investigating where a feature belongs, designing its structure, writing the code, reviewing quality, and running tests.
Why use it?
It reduces unclear scope and design mistakes by exploring the codebase, comparing architecture options, implementing the chosen approach, and reviewing the result with approval points.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/zircote-plugins/refactor/feature-dev
Any agent
npx skills add zircote-plugins/refactor --skill feature-dev
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/refactor

Made for: Claude Code, Codex.

Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00101 $0.05457
Opus 5 $0.00051 $0.02729
Sonnet 5 $0.00020 $0.01091
Haiku 4.5 $0.00010 $0.00546

Measured yesterday against content hash 40d0c4442b39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-dev scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/feature-dev/SKILL.md · 532 lines

How it starts

The opening of the file, as written. The whole thing — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Development Skill (Swarm Orchestration)

You are the team lead orchestrating a guided feature development process using a swarm of specialist agents with interactive approval gates.

Overview

This skill implements a comprehensive feature development workflow using specialist agents from the refactor plugin, coordinated as a swarm team:

  • code-explorer — Deep codebase exploration: traces patterns, maps architecture, identifies integration points (runs as N parallel instances)
  • architect — Designs feature architecture with implementation blueprints (runs as N parallel instances)
  • code-reviewer — Focus-area quality review: simplicity/DRY, bugs/correctness, conventions/abstractions (runs as N parallel instances)
  • feature-code — Implements the chosen architecture following codebase conventions
  • refactor-code — Available for fix-up tasks if needed
  • refactor-test — Runs tests to verify implementation correctness
  • simplifier — Available for post-implementation polish if needed

The workflow uses interactive approval gates at key decision points and parallel multi-instance agent spawning for exploration, architecture, and review phases.

Arguments

$ARGUMENTS: Feature description or requirement to implement.

Parse $ARGUMENTS as the initial feature description. This will be refined through the elicitation protocol in Phase 1.

Phase 0.0: Configuration Check

Step 0.0.1: Load or Create Configuration

  1. Attempt to read .claude/refactor.config.json from the project root
  2. If file exists: Parse the JSON silently. Merge with defaults (any missing fields use defaults). Store as config. Proceed to Phase 0.1.
  3. If file does NOT exist: Create with defaults and proceed.

Config schema v3.1 — feature-dev uses the featureDev section:

{
  "version": "3.1",
  "iterations": 3,
  "postRefactor": { "..." },
  "featureDev": {
    "explorerCount": 3,
    "architectCount": 3,
    "reviewerCount": 3,
    "commitStrategy": "single-final",
    "createPR": false,
    "prDraft": true
  }
}

Read the full file on GitHub · 532 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 532 lines · 101 tokens per session scan A 40d0c4442b39

Subscribe to this mod's changes

feature-dev is a skill published in the GitHub repository zircote-plugins/refactor (2 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 5,457 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.