feature-dev

A guided workflow for developing a feature with specialist agents working as a coordinated team. It separates codebase exploration, architecture design, implementation, review, testing, and cleanup, with approval points between stages.

In plain words
What is it for?
Use it for feature work that needs architectural investigation and quality checks. The workflow can explore the codebase, propose designs, implement the selected approach, review it, run tests, and apply fixes or simplification.
Why use it?
It provides several focused reviews of the same feature and makes the design and implementation decisions visible before code is changed.

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/skill-snapshot
Any agent
npx skills add zircote-plugins/refactor --skill skill-snapshot
Clone the repo
git clone --depth 1 https://github.com/zircote-plugins/refactor

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,773 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.00027 $0.04773
Opus 5 $0.00014 $0.02387
Sonnet 5 $0.00005 $0.00955
Haiku 4.5 $0.00003 $0.00477

Measured 2d ago against content hash fcac35384465, 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 2d ago.

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.

feature-dev-workspace/skill-snapshot/SKILL.md · 512 lines

How it starts

The opening of the file, as written. The whole thing — 512 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 · 512 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. 2d ago First seen · 512 lines · 27 tokens per session scan A fcac35384465

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 27 tokens to every session and 4,773 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

self-improving-agent

Log learnings, errors, and corrections to .learnings/ for continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects the agent, (3) A knowledge gap is identified, (4) A better approach is found. Captures corrections, insights, errors, and feature requests; promotes broadly…

mick-gsk/drift · 85 tokens

drift-agent-prompt-authoring

Drift-spezifischer Workflow zum Erstellen und Verbessern von Agent-Prompts unter .github/prompts/. Verwenden bei neuen .prompt.md-Dateien, bei der Schärfung von Evaluierungs-Prompts, bei der Trennung zwischen internem Prompt und Field-Test-Prompt sowie bei der Ausrichtung auf Drift-Policy und Shared Partials.…

mick-gsk/drift · 115 tokens

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality).

mick-gsk/drift · 37 tokens

detect-stack

Analyze a codebase to detect its language, framework, conventions, and CI gates. Run this on first use in a project to generate stack context that all coding principle skills reference. Use when the user says "detect stack," "analyze this project," or "what's this codebase using.".

JordanCoin/codingskills · 63 tokens

re0-loop

Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.

LilMGenius/paperthin · 60 tokens

new-skill

Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…

hyhmrright/brooks-lint · 145 tokens