Add spec-kit integration documentation and examples #6600
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users need comprehensive documentation on using spec-kit with gh-aw for spec-driven development, including directory structure, workflow commands, and practical examples.
Documentation Added
Main guide (
docs/src/content/docs/guides/spec-kit-integration.md, 556 lines).specify/) and file organization/speckit.specify,/speckit.plan,/speckit.tasks,/speckit.implementComplete example (
.specify/specs/example-feature/, 1,109 lines)spec.md: User stories, functional/non-functional requirements, success metricsplan.md: Go-based architecture, TDD strategy, component designtasks.md: Phase-based task breakdown (Setup → Tests → Core → Integration → Polish)README.md: Usage guide and learning pointsRepository Updates
Example Usage
All documentation follows Astro Starlight format, GitHub Docs voice, and emphasizes constitution-aligned development with TDD principles.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.