feature-development

feature-development is a skill for Claude Code, Codex from protect-my-hair/nucleus-marketplace. It costs 32 tokens per session (2,622 once invoked), scanned A, original, MIT.

A feature-development workflow for the Nucleus V2 project. It guides work from requirements and design through implementation, testing, reviews, and completion evidence.

In plain words
What is it for?
Use it when developing one or more Nucleus V2 features, especially features involving user interfaces or formal project specifications.
Why use it?
It prevents coding from starting without the required plans, specifications, design sources, task tracking, and review checks.

Skill for Claude CodeCodex

Written for Claude Code and Codex: SessionStart hook event, but also agents/openai.yaml present. Also seen: mentions subagents; names the TodoWrite tool; mentions Claude Code.

Part of the nucleus plugin — 27 skills, 1 agent, 1 hook shipped together

Good fit Use it when developing one or more Nucleus V2 features, especially features involving user interfaces or formal project specifications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/protect-my-hair/nucleus-marketplace/feature-development
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.

Any agent
npx skills add protect-my-hair/nucleus-marketplace --skill feature-development
Clone the repo
git clone --depth 1 https://github.com/protect-my-hair/nucleus-marketplace

Made for: Claude Code, Codex.

Or install nucleus, the plugin that ships this one along with the rest of its 27 skills, 1 agent, 1 hook.

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.

agentmods badge for feature-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/feature-development/github.svg)](https://agentmods.dev/skills/protect-my-hair/nucleus-marketplace/feature-development)
Your own site
<a href="https://agentmods.dev/skills/protect-my-hair/nucleus-marketplace/feature-development"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/feature-development/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.

agentmods 80×15 button for feature-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/protect-my-hair/nucleus-marketplace/feature-development"><img src="https://agentmods.dev/badge/skills/protect-my-hair/nucleus-marketplace/feature-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,622 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.02622
Opus 5 $0.00016 $0.01311
Sonnet 5 $0.00006 $0.00524
Haiku 4.5 $0.00003 $0.00262

Measured 13d ago against content hash 468f11d845ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

feature-development 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 13d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/feature_development.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/nucleus/skills/feature-development/SKILL.md · 112 lines

How it starts

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

特性开发

前置:使用本 Skill 前,先按 using-nucleus 完成 Nucleus 入口识别(Claude Code 会话由插件 SessionStart hook 自动注入该纪律)。

核心原则

特性开发是按特性分组的 task / todo 编排,不是脚本循环,也不是一个大开发任务。

当前特性涉及 UI,且 docs/ui-design/**、Pencil 文件、ui-prototype.md 或用户明确设计稿存在时,未把相关 UI 设计源纳入实施计划、实现任务和完成评审证据前,不得写 UI 源码或把当前特性标记完成;仅发现仓库候选设计源时,未完成人工相关性确认前不得写 UI 源码。

当前特性实施计划缺少 developmentSpecs,或目标仓库 docs/specs/** 规范缺失但没有 setup gap 处理结论时,不得写源码、测试或把当前特性标记完成。

当前特性实施计划缺少 specAnchor,或上下文压缩 / 会话恢复 / 阶段切换后没有从磁盘重读 .nucleus/runs/<workflowRunId>/spec-anchor.json 及其 sourceEvidencePaths 时,不得写源码、测试、样式或请求完成评审。

未创建宿主 todo/task 任务包,不得执行 feature-doc-designfeature-development-preparefeature-implementationmulti-review 或进入下一个特性。

每个特性设计评审、实施计划确认和特性完成评审请求发给人之前,必须先按 _shared/references/subagent-precheck-protocol.md 调度独立 reviewer 完成 subagentPreReview;未取得“材料可提交人工审查”结论时,不得请求人工评审通过。

Checklist

启动本 Skill 后,必须先为以下每一项创建宿主 todo/task,并按顺序执行;Codex 使用计划 / 任务工具,Claude Code 使用 TodoWrite 或等价宿主 todo。每完成、阻塞或等待一项,都必须逐项更新状态。.nucleus/runs/<workflowRunId>/feature-development/tasks.jsontasks.md 只是这些宿主任务包的镜像证据,不能替代宿主任务、设计评审、计划确认、review、整改复核或 PMS 状态。

  1. 读取需求设计产物:读取需求实现方案、拆解结果和 .nucleus/context/<workflowRunId>.json;不把上游评审是否文件化作为本阶段 input 阻塞。
  2. 读取特性拆解输入:读取 requirement-decomposition 输出的特性路径、优先级、依赖和 feature-doc-design 输入。
  3. 确认需求分支:调用或执行 requirement-branch;缺分支授权时 ALERT_AND_BLOCK
  4. 读取现有特性树:读取目标仓库 docs/features/** 既有结构,避免跨特性误写。
  5. 创建宿主特性任务包:为每个特性创建独立 task 包;当前特性未完成前不得开始下一个特性。
  6. 执行当前特性设计:调用 feature-doc-design 直接写入 docs/features/** 待评审特性文档,先按 _shared/references/subagent-precheck-protocol.md 完成 subagentPreReview;通过后按 _shared/references/interaction-format.md 的确认型格式呈现给人评审,未通过时修订设计。
  7. 生成并确认实施计划:设计评审通过后生成实施计划,先按 _shared/references/subagent-precheck-protocol.md 完成 subagentPreReview;通过后按 _shared/references/interaction-format.md 的确认型格式请求确认,未确认时不得写源码或测试。计划必须包含 specAnchordevelopmentSpecs,列出 docs/specs/** 规范证据、适用 rules、缺失状态、facts manifest hash、reload policy 和 setup gap 处理要求。当前特性存在相关 UI 设计源时,计划必须包含 UI 设计源发现证据、Pencil frame / UI 状态映射、公共组件 / 公共样式契约和视觉证据路径;仅发现候选设计源时,计划必须要求人工确认相关性。
  8. 按计划实现并验证:每个 task 写源码、测试或样式前,先重读 specAnchor.sourceEvidencePaths 指向的 specs、UI 设计证据和实施计划,再补测试或测试资产,再实现当前特性覆盖内容,并运行计划声明的验证命令。若计划 uiDesign.applicability=required,必须先导出或读取设计 frame,按 frame / 状态映射实现,并采集浏览器截图、人工视觉证据或等价 UI 对照证据。
  9. 完成多维评审:调用 multi-review 做 code-review、方案一致性评审和计划满足度评审。
  10. 整改并复核:整改评审意见或写明不采纳理由,再完成复核。
  11. 收口当前特性证据:确认当前特性证据完整且无越界改动后,才允许解锁下一个特性。

Read the full file on GitHub · 112 lines

Files

What ships with it

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

  1. 13d ago First seen · 112 lines · 32 tokens per session scan A 468f11d845ba

Subscribe to this mod's changes

feature-development is a skill published in the GitHub repository protect-my-hair/nucleus-marketplace (162 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,622 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens