Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Feature]: speckit-status - provide brief status report on project flow across all stages of development

未關閉
#4,705 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
65/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
python

研究方向

Look at the spec-kit CLI commands in the codebase, likely under a commands or cli module. Understand how spec states (specify, plan, tasks, implement) are tracked. The new command should read this state and output a structured checklist. Start by running existing commands like /speckit-specify to see their output and state storage. Check for existing tests for CLI commands to follow the pattern.

由索引模型根據 Issue 內容生成。

描述

enhancement needs-triage triage-out-of-scope
Problem Statement

I do some work with spec-kit, maybe run /speckit-specify, then /speckit-plan, but then leave the session. Later I come back and don't remember where I left off. It would be great to quickly get a status to know where to start next. This should be defined so other agents doing automation of spec-kit can consume and learn where to resume work.

Proposed Solution

I would imagine a nice checklist, perhaps with hierarchy of multiple "specs" and their list of phases or stages and which have been completed with a [X] and not completed with a [ ] preceding each line.

  • Constitution created
  • 001-feature-a
    • Spec
    • Plan
    • Tasks
    • Implement
Alternatives Considered

Internet research says there are other extensions that do this, but this should be native with spec-kit, it is the one that owns the process and all state, so should provide it and should be AI-consumption first, not human first.

Component

Specify CLI (initialization, commands)

AI Agent (if applicable)

None

Use Cases

Human teams or Agentic systems doing work with spec-kit where work sessions stop and start across days or hours and status where left off needs to be checked to determine next steps to resume work.

Acceptance Criteria

No response

Additional Context

No response

AI Disclosure

N/A

主要語言
Python
星號
138k
分支
12.4k
平均合併
3 天 2 小時
30 天內合併 PR
169

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/spec-kit 的其他 Issue

查看 github/spec-kit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。