From 9d35a7451b122fc8361a7441d4697c64c904a4cf Mon Sep 17 00:00:00 2001 From: Lucas Santana Date: Wed, 15 Apr 2026 16:33:53 -0300 Subject: [PATCH 1/2] docs(specs): bootstrap spec and roadmap flow --- docs/roadmap.md | 15 +++++++++++++ .../spec.md | 21 +++++++++++++++++++ .../tasks.md | 7 +++++++ 3 files changed, 43 insertions(+) create mode 100644 docs/roadmap.md create mode 100644 docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md create mode 100644 docs/specs/2026-04-15-ecosystem-roadmap-specs/tasks.md diff --git a/docs/roadmap.md b/docs/roadmap.md new file mode 100644 index 0000000..6321299 --- /dev/null +++ b/docs/roadmap.md @@ -0,0 +1,15 @@ +# Roadmap - core + +_Auto-regenerated 2026-04-15 from `docs/specs/`._ + +## Now (active) + +_(none)_ + +## Next (proposed) + +- **2026-04-15-ecosystem-roadmap-specs** _(proposed)_ `roadmap,specs,ecosystem` + +## Recently shipped + +_(none)_ diff --git a/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md b/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md new file mode 100644 index 0000000..17afe00 --- /dev/null +++ b/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md @@ -0,0 +1,21 @@ +--- +status: proposed +created: 2026-04-15 +owner: lucassantana +pr: +tags: roadmap,specs,ecosystem +--- + +# ecosystem-roadmap-specs + +## Goal +Establish committed feature specs and a generated roadmap for the Forge Space core product surface. + +## Context +Core is the cross-repo coordination point for ecosystem plans and prompts. Keeping specs in-repo makes RAG retrieval precise without loading the whole docs tree. + +## Approach +Seed the spec lifecycle with one proposed roadmap/spec adoption item, keep the generated roadmap derived from frontmatter, and let future feature work add focused specs. + +## Verification +docs/roadmap.md lists this proposed spec and the spec files are picked up by the shared RAG spec/roadmap source types. diff --git a/docs/specs/2026-04-15-ecosystem-roadmap-specs/tasks.md b/docs/specs/2026-04-15-ecosystem-roadmap-specs/tasks.md new file mode 100644 index 0000000..b536fa6 --- /dev/null +++ b/docs/specs/2026-04-15-ecosystem-roadmap-specs/tasks.md @@ -0,0 +1,7 @@ +# Tasks - ecosystem-roadmap-specs + +- [ ] Review current roadmap/backlog signals for the repo +- [ ] Convert the next non-trivial feature into a focused spec +- [ ] Keep docs/roadmap.md generated from specs, not hand-edited +- [ ] Verify RAG returns this spec via source_type=spec or roadmap +- [ ] Link the implementation PR before marking shipped From 70ace5226c1cd1605201047de87b1090557e0554 Mon Sep 17 00:00:00 2001 From: Lucas Santana Date: Wed, 15 Apr 2026 16:42:00 -0300 Subject: [PATCH 2/2] docs(specs): format generated roadmap files --- docs/roadmap.md | 2 +- .../2026-04-15-ecosystem-roadmap-specs/spec.md | 18 ++++++++++++++---- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index 6321299..2fa5e0f 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -8,7 +8,7 @@ _(none)_ ## Next (proposed) -- **2026-04-15-ecosystem-roadmap-specs** _(proposed)_ `roadmap,specs,ecosystem` +- **2026-04-15-ecosystem-roadmap-specs** _(proposed)_ `roadmap,specs,ecosystem` ## Recently shipped diff --git a/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md b/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md index 17afe00..c54d01c 100644 --- a/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md +++ b/docs/specs/2026-04-15-ecosystem-roadmap-specs/spec.md @@ -9,13 +9,23 @@ tags: roadmap,specs,ecosystem # ecosystem-roadmap-specs ## Goal -Establish committed feature specs and a generated roadmap for the Forge Space core product surface. + +Establish committed feature specs and a generated roadmap for the Forge Space +core product surface. ## Context -Core is the cross-repo coordination point for ecosystem plans and prompts. Keeping specs in-repo makes RAG retrieval precise without loading the whole docs tree. + +Core is the cross-repo coordination point for ecosystem plans and prompts. +Keeping specs in-repo makes RAG retrieval precise without loading the whole docs +tree. ## Approach -Seed the spec lifecycle with one proposed roadmap/spec adoption item, keep the generated roadmap derived from frontmatter, and let future feature work add focused specs. + +Seed the spec lifecycle with one proposed roadmap/spec adoption item, keep the +generated roadmap derived from frontmatter, and let future feature work add +focused specs. ## Verification -docs/roadmap.md lists this proposed spec and the spec files are picked up by the shared RAG spec/roadmap source types. + +docs/roadmap.md lists this proposed spec and the spec files are picked up by the +shared RAG spec/roadmap source types.