speckit-workflows.baseline

Generate baseline documentation by running the create-baseline.sh script with the --json flag from your repository root to capture the project state and populate baseline-spec.md and current-state.md automatically.

A project baseline captures the initial state and expected structure to anchor future specs, providing consistent context and a changelog-like record for tracking modifications as your documentation evolves.

Create a change-tracking record by analyzing the current state or baseline commit, which produces baseline documentation that captures initial project context and maintains modification history as specs evolve.

No dependencies are required to use spec-kit workflows for markdown documentation, as the Skill operates independently to execute documented scripts and generate baseline artifacts from your project state.

Yes, you can use automated templates to produce current-state.md and baseline-spec.md by executing the documented script, which analyzes the baseline commit and references spec templates to generate comprehensive documentation.

The best way to establish a reference baseline is executing the baseline script to capture JSON output, then analyzing the current state to populate documentation that supports future specs with context, structure, and change history.