docs: add sdd/roadmap.md index of all SDDs#102
Merged
Merged
Conversation
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.
Summary
Adds
sdd/roadmap.md— a single-table index of every Spec-Driven Development doc in this repo, with one-line purpose, status (planning / in-progress / shipped), and pointers to the relevant Linear epic and GitHub PR per row.Also adds a one-line pointer in
AGENTS.mdso contributors land here from the natural starting point.Why
The
sdd/directory has grown to 10 features on trunk plus 3 in-flight (PRs #90, #92, #93). Without an index, it's hard for a new contributor — or future-me — to know what exists, what's shipped, and what's in flight without reading 10 separate spec files. AGENTS.md already specifies that per-SDDplan.mdcarries a## Progresschecklist for task-level status; this roadmap rolls those up into a directory-level view.Inputs
sdd/on trunk (10 SDDs, drawn from theirspec.md/requirements.md).sdd/: SDD: FOSSE-native posting UI #90 (FOSSE-native posting UI), SDD: Deactivation lifecycle #92 (Deactivation lifecycle), SDD: Bundled backends migration #93 (Bundled backends migration).Test plan
roadmap.mdshould be enough guidance)