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 摘要。