[Feature]: Deprecate the core taskstoissues command
維護者通常 1 天內回覆
已經有一個關聯 PR 被合併了。
- #4879 來自 @rohanz —— 已合併
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 55/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github, python
- 領域
- cli, documentation
研究方向
#4421 發布後，從核心 /speckit.taskstoissues CLI 入口點開始，檢查命令清單和面向使用者的文件。在新增警告之前，驗證現有行為、安全性檢查、去重，以及 before_taskstoissues/after_taskstoissues hooks。完成標準是命令仍然正常運作、遷移命令和棄用狀態已有文件說明，且相依工作可以針對該擴充功能。
由索引模型根據 Issue 內容生成。
描述
Problem Statement
/speckit.taskstoissues is currently presented as a core Spec Kit command even though it performs GitHub-specific issue-tracker integration. Once the bundled GitHub Issues extension from #4421 is available, users should be guided toward the extension before the core command is removed.
Removing the command without a deprecation period would provide no transition window for existing projects, automation, presets, or dependent extensions.
Proposed Solution
After #4421 has shipped, mark the core /speckit.taskstoissues command as deprecated while preserving its behavior for this stage.
When invoked, the command should display a concise warning that:
- The core command is deprecated and will be removed in a future minor release.
- Its replacement is the bundled
github-issuesextension. - Users can migrate with:
specify extension add github-issues
/speckit.github-issues.taskstoissues
The deprecation must not automatically install or enable the extension. Existing command behavior, safety checks, deduplication, and lifecycle hooks should remain unchanged until the removal stage.
Update user-facing command inventories and documentation to distinguish the deprecated core command from the recommended extension command.
Alternatives Considered
- Deprecate before adding the extension: Rejected because the warning would point users toward a replacement that is not yet available.
- Silently document the migration without an invocation warning: Easy to miss for users who do not regularly read release notes.
- Remove the command in the same release: Provides no practical migration window for existing users or dependent extensions.
Component
Specify CLI (initialization, commands)
AI Agent (if applicable)
All agents
Use Cases
- Existing users learn how to migrate while their current command still works.
- Preset and extension authors have time to update dependencies and hook references.
- Teams can schedule the extension installation before a later upgrade removes the core command.
Acceptance Criteria
- This issue is implemented only after #4421 has shipped.
- Invoking the core
speckit.taskstoissuescommand displays an actionable deprecation warning. - The warning identifies
speckit.github-issues.taskstoissuesas the replacement and includes the installation command. - The deprecated core command retains its existing behavior.
-
before_taskstoissuesandafter_taskstoissueshooks continue to work. - Core command documentation and inventories clearly mark the command as deprecated.
- Migration documentation covers existing projects, integrations, presets, and extensions.
- #4370 and other dependent work can update their dependency target to the extension command.
- The change is included in a minor release after the extension release.
Additional Context
This is stage 2 of the three-stage migration:
- #4421 adds the bundled extension while retaining core behavior.
- This issue deprecates the core command.
- A follow-up issue will remove it from core after the deprecation window.
Related discussion: #4370, especially https://github.com/github/spec-kit/issues/4370#issuecomment-5525946904.
- 主要語言
- Python
- 星號
- 140k
- 分支
- 12.6k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 184
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/spec-kit 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 66/100
維護者通常 1 天內回覆
-
feature-assess feature-go triage-can-wait
難度 2/5 1-3 小時 新手友好度 78/100
github/spec-kit#4804 · 6 則留言 ·
維護者通常 1 天內回覆
-
needs-triage triage-nice-to-have
難度 2/5 1-3 小時 新手友好度 72/100
github/spec-kit#4527 · 1 則留言 ·
維護者通常 1 天內回覆
-
[Bug]: specify init writes speckit.manifest.json without the speckit-converge skill it just installed可能重新可做 關聯的 PR 已關閉且未合併。 未關閉bug-assess severity-medium
難度 2/5 1-3 小時 新手友好度 72/100
github/spec-kit#4273 · 3 則留言 ·
維護者通常 1 天內回覆
-
[Bug]: /speckit-implement counts checkbox markers inside fenced code blocks — example checkboxes can falsely block implementation可能已有人在做 @ntdatt812 於 32 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
相似的 Issue
-
SSM GetParameter throttling during concurrent workflow launches可能已有人在做 @alexiswl 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 80/100
-
[Bug] Dev image build fails: `npm install` in the root Dockerfile runs out of memory (exit 134)可能已有人在做 @andest01 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 79/100
pesu-dev/discord_bot#97 ·
-
難度 1/5 1-3 小時 新手友好度 88/100
gradio-app/gradio#13964 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 93/100
BSData/horus-heresy-3rd-edition#3232 · 1 則留言 ·
維護者通常 1 天內回覆