Exporting Markdown to Git

Treat planning documents as repository context

SpecKit exports blueprint documents as standard Markdown files. Markdown is readable in a text editor, reviewable in a pull request, and rendered by common Git hosting services. Keeping planning artifacts near the application code gives contributors and coding agents a stable place to find product and technical context.

Recommended repository structure

my-software-project/
├── src/
├── public/
├── docs/
│   ├── PRD.md
│   ├── REQUIREMENTS.md
│   ├── DATABASE.md
│   ├── API.md
│   ├── ARCHITECTURE.md
│   └── ROADMAP.md
├── package.json
└── README.md

The exact files depend on the blueprint. Keep related documents together and add a short note in the repository README so contributors know where the project specification lives.

Export and commit

1. 1. Download the archive. Use the download action in the SpecKit workspace to export the available Markdown documents as a ZIP archive.
2. 2. Inspect and unpack it. Review the archive, then place its files in a docs/ directory or another documented location in your repository.
3. 3. Commit through your normal Git workflow. Check the diff, use a descriptive commit message, and push to GitHub, GitLab, Bitbucket, or your existing Git remote.