Feature Request: Project-Level PRD Generation and Phase/Status Tracking

[harishkm83]

Is your feature request related to a problem? Please describe.
Currently, the /speckit.specify command works very well for individual feature specifications, but there is no structured way to capture, view, or manage an overall list of project features or their implementation status in one place. In larger projects, it becomes difficult to track high-level progress, plan upcoming phases, or update the project status holistically. This lack of visibility increases the risk of misalignment and impedes effective planning.

Describe the solution you'd like
I propose introducing a new Spec Kit command to generate and manage a project-wide Product Requirements Document (PRD) from a comprehensive list of requirements.

• This command should:
  • Accept the complete project’s requirements and generate a structured PRD representing the full scope of the project, broken down by phases and sub-tasks.
  • Allow phases/sub-tasks to be updated with status indicators (e.g., Not Started, In Progress, Done).
  • Support linking phases/sub-tasks to their respective feature specifications.
  • Enable referencing specific phases or tasks when invoking the /speckit.specify or /speckit.plan commands (e.g., “specify phase 1 in prd”).
• The PRD should be an evolving artifact:
  • Each project phase can be planned and tracked from inception, and individual phases can be specified, updated, or re-planned as needed.
  • Provide real-time visibility on where the project stands, facilitating planning, coordination, and reporting.

Describe alternatives you’ve considered
Workarounds include maintaining a separate document or external tracker, but these quickly become unsynchronized and lack the tight integration with Spec Kit’s existing workflow and automation.

Additional context
Having a project-wide PRD feature will enable teams to:

• Plan ahead with visibility of all features and their statuses.
• Update status for each phase, making progress tracking transparent at every project stage.
• Reference phases/sub-tasks in existing Spec Kit commands, improving usability and alignment.