Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
#4,705 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
cli, developer-experience

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Python
Stelle
138k
Fork
12.4k
Merge medio
3g 2h
PR unite (30g)
169

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/spec-kit

Tutte le issue di github/spec-kit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.