A workflow for planning and building software features in either an existing codebase or a new project. It covers understanding the work, research and design where needed, approval, implementation, and review.

Use it to scope a feature, design its implementation, create a plan, obtain approval, and route simple or complex work to the appropriate coding and review process.

It gives feature work a defined path from unclear request to reviewed code, while adjusting the process to the size and complexity of the change.

How DeL-TaiseiOzaki/claude-code-orchestra configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/feature/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestra

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/feature/github.svg)](https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/feature)

Your own site

<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/feature"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/feature"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 147 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 9,043 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00147	$0.09043
Opus 5.5	$0.00059	$0.03617
Sonnet 5.5	$0.00029	$0.01809
Haiku 4.5	$0.00015	$0.00904

Measured 1mo ago against content hash e3fc7e2fc558, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature 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 1mo 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.

.claude/skills/feature/SKILL.md · 892 lines

How it starts

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

Feature

One entry point for feature work, two modes:

MODE=existing (old /add-feature path): the feature goes into an established codebase whose conventions are already known. No external research needed → Codex-direct scope → design → plan.
MODE=greenfield (old /start-feature path): a large or new feature that needs external research and parallel design → Agent Teams (Researcher + Architect) with bidirectional communication.

Both modes converge on a shared Phase 3: user approval + complexity-routed implementation.

Preflight: ensure codex CLI is current (see codex-system skill).

/feature <feature description>
    | MODE determination (AskUserQuestion when ambiguous)
    ├─ MODE=existing   : Phase 1E SCOPE  -> Phase 2E DESIGN (Codex direct)
    └─ MODE=greenfield : Phase 1G UNDERSTAND -> Phase 2G RESEARCH & DESIGN (Agent Teams)
    | Phase 3 (shared): PLAN, APPROVE & IMPLEMENT
    SIMPLE   (1-3 files, <50 LOC) -> Codex danger-full-access direct
    MODERATE (3-5 files)          -> Codex danger-full-access + /team-execute --review-only
    COMPLEX  (5+ files)           -> /team-execute (implement + review)

Mode Determination (always first)

Decide the MODE before anything else. Signals:

Signal	MODE=existing	MODE=greenfield
Codebase state	Established, conventions known	New area, or conventions absent
External research needed	No — Codex reasons about existing patterns directly	Yes — libraries/tools/reference architectures must be researched
Feature size	Localized addition	Large, multi-module, or project kickoff
Design source	Codex (read-only consults)	Agent Teams (Researcher + Architect)

If the signals are mixed or unclear, ask via AskUserQuestion — do NOT guess:

question: "Which feature mode applies?"
multiSelect: false
options:
  - label: "existing"
    description: "Add to an established codebase; conventions known; no external research (old /add-feature)."
  - label: "greenfield"
    description: "Large/new feature; needs external research and parallel design via Agent Teams (old /start-feature)."

Read the full file on GitHub · 892 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

1mo ago Changed e3fc7e2fc558
2mo ago Changed 252ed9f2e8c2
2mo ago First seen · 892 lines · 147 tokens per session scan A f8b29fda0265

Subscribe to this mod's changes

feature is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (198 stars, last pushed 5d ago), licensed MIT. It adds 147 tokens to every session and 9,043 once invoked, about $0.0006 per session on Opus 5.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-30.

Planning Project management

feature next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
featureDeL-TaiseiOzaki/claude-code-orchestra	Skill	198	5d ago	MIT	A	147	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

claude-code-orchestra: Skill for Claude Code