speckit-baseline

To establish a baseline specification, you can execute a script that captures your project state and analyzes code repositories, generating foundational documentation detailing initial architecture and functionality.

Tracking current project modifications involves analyzing your code repositories to enumerate and summarize recent changes, including new features, bugfixes, and refactors, providing a clear historical reference point.

Yes, generating baseline documentation requires a spec-kit project structure with a .specify/ directory present in your repository for the workflow execution scripts to run successfully.

You can automate project documentation generation by running a script that captures the initial project state, establishing a foundational specification automatically without manual writing.

You should create a baseline specification when starting a new project or integrating spec-kit, ensuring all initial project details are captured to provide a historical reference point for future development.

A key limitation is that the workflow execution strictly requires a .specify/ directory, meaning baseline specification generation and state tracking will not function without this specific spec-kit project structure.