Repository navigation
chore: adopt Spec Kit development workflow - #10
Merged
Merged
Conversation
This was referenced Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Share repository-local Spec Kit setup so feature work follows a committed constitution and review workflow.
This adoption changes development tooling and governance. Application behavior, public contracts, dependencies, model weights, deployment configuration, and package versions are preserved. Historical OpenSpec records remain available in the aggregate workspace.
Validation: the local artifact audit passed on 2026-10-05 across all eight repositories: 48 Bash syntax checks, 32 template resolutions, 256 managed-file hash checks, eight read-only path checks, relative links, ignore rules, and commit scope. Application tests were not rerun locally for this tooling-only change; this PR runs the repository's existing CI.
The cross-repository adoption uses
chore/spec-kit-adoption. These changes can be reviewed independently; publication and merge of the other adoption PRs are tracked separately.Related adoption PRs: