feature-development

feature-development is a skill for Claude Code, Codex from u9401066/rootcause-mcp. It costs 0 tokens per session (1,335 once invoked), scanned A, a copy of feature-development, Apache-2.0.

A complete workflow for developing a software feature from planning through deployment. It coordinates architecture design, test generation, code review, project notes, and pre-commit checks.

In plain words
What is it for?
Use it to plan a new feature, identify affected parts of a codebase, implement it, generate tests, review the changes, update project notes, and run pre-commit checks.
Why use it?
It organizes the work needed for a feature and helps keep planning, implementation, tests, review, and project memory aligned.

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/u9401066/rootcause-mcp/feature-development
Any agent
npx skills add u9401066/rootcause-mcp --skill feature-development
Clone the repo
git clone --depth 1 https://github.com/u9401066/rootcause-mcp

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00000 $0.01335
Opus 5 $0.00000 $0.00668
Sonnet 5 $0.00000 $0.00267
Haiku 4.5 $0.00000 $0.00134

Measured 2d ago against content hash e227f1dd4e3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

Origin

This is a copy

100% identical to feature-development — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/feature-development/SKILL.md · 160 lines

How it starts

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


name: feature-development description: Complete feature development workflow orchestrating multiple skills from planning to deployment. Triggers: FD, 新功能, 開發功能, feature, implement, 實作, 實現, 建立功能, create feature, develop, 開發新, add feature, 加功能, 功能開發. version: 1.0.0 category: workflow compatibility:

  • claude-code
  • github-copilot
  • vscode
  • codex-cli orchestrates:
  • ddd-architect
  • test-generator
  • code-reviewer
  • memory-updater
  • git-precommit allowed-tools:
  • read_file
  • write_file
  • create_file
  • create_directory
  • list_dir
  • grep_search
  • semantic_search
  • run_in_terminal
  • get_changed_files

功能開發工作流

描述

完整的功能開發流程,從規劃到部署,編排多個 Skills 協同工作。

觸發條件

  • 「新功能開發」「implement feature」「建立新功能」
  • 「FD: [功能名稱]」

📋 工作流程

┌─────────────────────────────────────────────────────────────┐
│              Feature Development Workflow                    │
├─────────────────────────────────────────────────────────────┤
│  Phase 1: 📐 規劃 (Planning)                                 │
│  ├─ 需求分析與確認                                           │
│  ├─ 識別影響範圍                                             │
│  └─ 更新 Memory Bank (activeContext)                        │
├─────────────────────────────────────────────────────────────┤
│  Phase 2: 🏗️ 架構 (Architecture)                            │
│  ├─ [ddd-architect] 生成 DDD 結構                           │
│  ├─ 建立介面定義                                             │
│  └─ 更新架構文檔                                             │
├─────────────────────────────────────────────────────────────┤
│  Phase 3: 🧪 測試先行 (TDD)                                  │
│  ├─ [test-generator] 生成測試框架                            │
│  ├─ 撰寫失敗的測試案例                                       │
│  └─ 定義驗收標準                                             │
├─────────────────────────────────────────────────────────────┤
│  Phase 4: 💻 實作 (Implementation)                          │
│  ├─ 實作 Domain 層                                          │
│  ├─ 實作 Application 層                                     │
│  ├─ 實作 Infrastructure 層                                  │
│  └─ 實作 Presentation 層                                    │
├─────────────────────────────────────────────────────────────┤
│  Phase 5: ✅ 驗證 (Verification)                            │
│  ├─ 執行測試套件                                             │
│  ├─ [code-reviewer] 程式碼審查                              │
│  ├─ [security-reviewer] 安全檢查                            │
│  └─ 靜態分析 (mypy, ruff, vulture)                          │
├─────────────────────────────────────────────────────────────┤
│  Phase 6: 📦 提交 (Commit)                                  │
│  ├─ [memory-updater] 更新 Memory Bank                       │
│  ├─ [git-precommit] 執行提交前檢查                          │
│  └─ 提交變更                                                │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 160 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 · 160 lines · 0 tokens per session scan A e227f1dd4e3a

Subscribe to this mod's changes

feature-development is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,335 tokens. A static security scan graded it A with 0 findings. It is 100% identical to feature-development, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

coding-icd10

Suggests candidate ICD-10-CM diagnosis codes (and ICD-10-PCS procedure codes) for diagnoses and procedures extracted by OpenMed, with rationale and a human-coder caveat. Use when the user wants to code a problem list, map a diagnosis span to a billable ICD-10-CM code, route a finding to the right chapter, cross-walk…

maziyarpanahi/openmed · 209 tokens

evaluating-with-leakage-gates

Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…

maziyarpanahi/openmed · 158 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens

deidentifying-clinical-text

Remove, mask, or replace PHI/PII in clinical free text on-device with OpenMed's deidentify(). Use when the user needs to de-identify medical notes, strip patient identifiers, redact PHI before sharing or analysis, anonymize discharge summaries, or pick a de-id method (mask vs remove vs replace vs hash vs shiftdates).…

maziyarpanahi/openmed · 144 tokens

extracting-sdoh

Extracts social determinants of health (SDOH) — housing instability, food insecurity, unemployment, transportation barriers, social isolation, financial strain — from clinical narrative and maps the spans to ICD-10-CM Z-codes (Z55–Z65). Use after running OpenMed NER when the user wants SDOH surfacing, Z-code…

maziyarpanahi/openmed · 163 tokens

pick-a-pii-model

Select an on-device OpenMed PII model from the committed registry by language, runtime format, and size budget, then require recall validation before deployment. Use when an agent must choose a local PII detector for CPU, Apple Silicon, or a mobile export without relying on live model discovery.

maziyarpanahi/openmed · 64 tokens