Repository navigation
docs(sdd): adopt specification-driven development - #271
Merged
Merged
Conversation
streambinder
force-pushed
the
feat/sdd-onboarding
branch
from
October 26, 2026 13:32
53feee0 to
dd68c89
Compare
The project decisions must live in the repository so a new session resumes from its files alone.
streambinder
force-pushed
the
feat/sdd-onboarding
branch
from
October 26, 2026 13:38
dd68c89 to
c334ef5
Compare
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
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.
This pull request onboards the project to Specification-Driven Development, per unciae section 25 and the instruction of the owner.
The change adds the Spec Kit v1.2.2 scaffold (generic integration, shell scripts), a constitution in Draft status, an architecture baseline, and decision 0001 in Proposed status in the register under
.specify/memory/decisions/. The constitution derives from the unciae golden standard and adds the project constraints: pipeline shape, graceful enrichment, honest reporting, the ID3 metadata as the library index, the library surface that external tools import, and production care for the daily synchronization. The super-linter gains one targeted exclusion for the Spec Kit managed subtrees; authored content under.specify/memory/stays linted.No application code changes. Ratification of the constitution and of decision 0001 stays with the owner: the merge deposits the drafts, the formal ratification stays open. The first cycle,
specs/001-lyrics-reporting, follows in a pull request stacked on this branch.