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/roadmap-updater/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/roadmap-updater)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/roadmap-updater"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/roadmap-updater/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/roadmap-updater"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/roadmap-updater.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.01482 |
| Opus 5 | $0.00000 | $0.00741 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
roadmap-updater 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 8d 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 roadmap-updater — 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROADMAP 更新技能
描述
根據完成的功能自動更新 ROADMAP.md,保持專案路線圖與實際進度同步。
觸發條件
- 「更新 roadmap」「RM」「路線圖」
- 被
git-precommit編排器調用 - 完成規劃中的功能後
📁 ROADMAP.md 標準格式
# Roadmap
> Last updated: 2026-01-15
## ✅ 已完成 (Completed)
- [x] **功能名稱** - 簡短描述 `(2026-01-15)`
- [x] **另一功能** - 描述 `(2026-01-10)`
## 🚧 進行中 (In Progress)
- [ ] **功能名稱** - 描述 `(預計 2026-Q1)`
- [ ] **另一功能** - 描述
## 📋 計劃中 (Planned)
### Phase 1: 基礎建設 (2026-Q1)
- [ ] 計劃項目 1
- [ ] 計劃項目 2
### Phase 2: 功能擴展 (2026-Q2)
- [ ] 計劃項目 3
- [ ] 計劃項目 4
## 🔮 未來考慮 (Future)
- 可能的功能 1
- 可能的功能 2
🔧 操作步驟
Step 1: 讀取現有 ROADMAP
read_file("ROADMAP.md")
Step 2: 取得最近變更(選用)
如果從 git-precommit 調用,可取得變更資訊:
get_changed_files()
分析變更內容以判斷完成了什麼功能。
Step 3: 匹配 ROADMAP 項目
根據完成的工作,在 ROADMAP 中尋找匹配項目:
匹配策略:
- 精確匹配功能名稱
- 關鍵字匹配(如 "認證" 匹配 "用戶認證系統")
- 檔案路徑推斷(如
src/auth/變更可能對應認證功能)
Step 4: 執行狀態更新
使用 replace_string_in_file 更新狀態:
計劃中 → 進行中:
oldString: "## 📋 計劃中 (Planned)\n\n- [ ] **用戶認證**"
newString: "## 📋 計劃中 (Planned)\n\n"
oldString: "## 🚧 進行中 (In Progress)\n\n"
newString: "## 🚧 進行中 (In Progress)\n\n- [ ] **用戶認證** - 開發中"
進行中 → 已完成:
oldString: "- [ ] **用戶認證** - 開發中"
newString: "" (從進行中移除)
oldString: "## ✅ 已完成 (Completed)\n\n"
newString: "## ✅ 已完成 (Completed)\n\n- [x] **用戶認證** - 完成登入/註冊功能 `(2026-01-15)`\n"
Step 5: 更新最後修改日期
oldString: "> Last updated: 2026-01-10"
newString: "> Last updated: 2026-01-15"
📊 狀態轉換圖
📋 計劃中 (Planned)
│
▼ [開始開發]
🚧 進行中 (In Progress)
│
▼ [完成]
✅ 已完成 (Completed)
⚡ 更新原則
1. 保留歷史
✅ 正確:
- [x] **功能 A** - 描述 `(2026-01-15)`
- [x] **功能 B** - 描述 `(2026-01-10)`
❌ 錯誤:移除已完成的項目
2. 時間標記
✅ 正確:`(2026-01-15)` 或 `(預計 2026-Q1)`
❌ 錯誤:沒有日期標記
3. 新功能處理
如果完成了 ROADMAP 未列出的功能:
📝 建議新增:
在「✅ 已完成」區塊新增:
- [x] **密碼重設功能** - 實作忘記密碼流程 `(2026-01-15)`
🔄 與其他 Skills 整合
| Skill | 整合方式 |
|---|---|
git-precommit |
自動調用,傳入變更資訊 |
changelog-updater |
完成的功能同步到 CHANGELOG |
memory-updater |
progress.md 的 Done 可參考 |
release |
發布時確認 ROADMAP 狀態 |
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.
- 8d ago First seen · 207 lines · 0 tokens per session scan A cda66746077b
roadmap-updater is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,482 tokens. A static security scan graded it A with 0 findings. It is 100% identical to roadmap-updater, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
doc-management
Documentation lifecycle management skill. Activates when user mentions documentation, docs, sync, quality, validation, releases, or setup. Routes to appropriate agent (doc-expert for orchestration, doc-writer for content) and provides gentle reminders about documentation health.
roadmap-updater
A tool that updates ROADMAP.md, a project file listing completed, ongoing, and planned work. It matches finished features to roadmap entries and changes their status.
increment
Plan a unit of work as a SpecWeave increment - spec.md with Problem, Scope, numbered ACs and an Approach, plus tasks.md. Use when starting a feature, bug, hotfix or refactor.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
sw-increment
Open a SpecWeave increment - a numbered folder with spec.md (problem, scope, numbered ACs, approach) and tasks.md - before any code. Use for "plan a feature", "new increment", "let's build X".
handoff
Write a portable, secret-scrubbed handoff doc so this work can continue in any AI tool or on any machine. Use when saying "handoff", "running out of tokens", or "continue elsewhere".