Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/u9401066/rootcause-mcp/master/.claude/skills/feature-development/SKILL.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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.
[](https://agentmods.dev/skills/u9401066/rootcause-mcp/feature-development)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/feature-development"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/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.
<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/feature-development"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/feature-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.01335 |
| Opus 5.5 | $0.00000 | $0.00534 |
| Sonnet 5.5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00134 |
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 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.
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.
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.
功能開發工作流
描述
完整的功能開發流程，從規劃到部署，編排多個 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] 執行提交前檢查 │
│ └─ 提交變更 │
└─────────────────────────────────────────────────────────────┘
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 First seen · 160 lines · 0 tokens per session scan A e227f1dd4e3a
feature-development is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 1mo 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.
Other skills, from other repositories
sop-mcp-usage
How to use the SOP-MCP server to execute, create, and improve Standard Operating Procedures.
release
A release-preparation workflow for software projects. It covers checks before publishing, version-number updates, changelog and documentation updates, and deployment checks.
bug-fix
A structured process for fixing software bugs, including reproducing the problem, finding its root cause, and writing a test that prevents it from returning. A regression test is an automated check that catches a previously fixed problem.
code-review-workflow
A step-by-step process for reviewing a pull request or merge request, which is a proposed code change awaiting review. It combines file and change summaries, automated checks, and architecture review.
feature-development
A structured workflow for developing a feature from requirements and architecture through tests, implementation, and deployment.
git-precommit
A pre-commit workflow that coordinates updates to project memory, documentation, changelogs, roadmaps, architecture notes, and commit messages before code is saved to Git.