How to make spec-kit work across repositories?

[RCFans]

Context

I'm using Spec Driven Development (SDD) with spec-kit for two distinct but connected projects:

1. Project A (StrategyAI Platform)

   • Tech: Next.js + AI SDK (TypeScript/JavaScript)
   • Goal: A chatbot application that queries a knowledge graph backend

2. Project B (KnowledgeGraph System)

   • Tech: Python + LangChain + Jupyter
   • Goal: Extract knowledge graphs from source files and store in Neo4J
   • Status: Already have working graph queries, tested with LLMs, and saved specs in spec-kit format

The Challenge

Currently, spec-kit's init command creates a spec/ folder only within the current repository. However, I need to:

• Share SDD specifications between these two repositories
• Keep API contracts, test examples, and functionality descriptions synchronized
• Maintain separate codebases (different languages, different teams)

Specific Questions

1. Is there a recommended workflow for cross-repository spec sharing in spec-kit?
2. Should we use submodules, monorepo approach, or separate spec repository?
3. How can we reference specs from another repository while maintaining versioning?
4. Are there plans for spec-kit workspace features that support multi-repo scenarios?

Current Workaround Considered

• Creating a separate "specs-only" repository
• Using git submodules to link specs into each project
• But wondering if spec-kit has native support planned

Use Case Example

When Project B defines a new graph query API in its spec, Project A should be able to:

• Reference that spec directly
• Generate client code or at least have type-safe API definitions
• Run compatibility tests

Would appreciate guidance from the community or spec-kit maintainers on best practices for this multi-repo, multi-language SDD workflow!

[jonathanmv]

I'm also curious. The way I've been solving it is by having the specs in a parent folder.

parent/
  specs/
  repo1/
  repo2/

But my specs are not versioned.