roadmap-updater
Skill3 starsChanged 9 months agoApache-2.0View on GitHub
Auto-update ROADMAP.md status based on completed features. Triggers: RM, roadmap, 路線, 規劃, 完成功能, milestone, 里程碑, 路線圖, 計畫, plan, planning, 進度, progress, 功能完成, feature done, 待辦, todo, backlog.
4 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- u9401066/zotero-keeperedited, first seen Nov 8, 2026
- u9401066/pubmed-search-mcpedited, first seen Oct 20, 2026
- u9401066/asset-aware-mcpedited, first seen May 6, 2026
- u9401066/nsforge-mcpedited, first seen Jan 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- u9401066/pubmed-search-mcp★ 2828% same
- u9401066/zotero-keeper★ 728% same
- u9401066/nsforge-mcp★ 428% same
- u9401066/asset-aware-mcp★ 028% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- bug-fixSkill
- changelog-updaterSkill
- code-auditSkill
- code-refactorSkill
- code-reviewerSkill
- code-review-workflowSkill
- ddd-architectSkill
- feature-developmentSkill
- git-doc-updaterSkill
- git-precommitSkill
- memory-checkpointSkill
- memory-updaterSkill
- project-initSkill
- readme-i18nSkill
- readme-updaterSkill
- releaseSkill
- security-reviewerSkill
- skill-generatorSkill
- skill-health-checkSkill
- test-generatorSkill
The file
Files
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 狀態 |
📝 輸出格式
執行完成後回報:
🗺️ ROADMAP 更新報告
狀態變更:
- ✅ 用戶認證 - 📋→✅ (標記為已完成)
- 🚧 API 文檔 - 維持進行中
建議新增:
- 💡「密碼重設」功能已完成,建議加入 ROADMAP
已更新:
- ROADMAP.md (Last updated: 2026-01-15)⚠️ 注意事項
- 不要刪除計劃項目:即使決定不做,也應標註而非刪除
- Phase 調整需確認:Phase 的調整通常需要與使用者確認
- 版本對應:已完成功能應對應到具體版本或日期
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

