DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to share one plan across several repos with Stores with Open Spec

Keep cross-repo specs in a separate shared repo that code repos and agents can read.

Who it is forA platform or product team whose feature spans an API server, a web app, and a shared library, and who wants one source of truth for requirements.

The problemRequirements drift across repos and wikis, and a feature that touches several codebases has no single plan.

The outcomeA planning repo holding the shared openspec/ specs and changes, pushed with git, that your team and coding agents can read across repos.

What you need first

  • Node.js 20.19.0 or higher, or Homebrew on macOS or Linux
  • A project directory you want to use OpenSpec in
  • An AI coding assistant that OpenSpec supports (30+ tools listed in the docs)

Steps

  1. Read the Stores guide at https://openspec.dev/docs/stores, since Stores is in beta
  2. Create a dedicated planning repo for the team and set up its openspec/ folder following the guide
  3. Add the planning repo to each code repo's agent context as the guide describes (inferred, check the README)
  4. Capture the cross-repo plan as a change in the store before the code repos are updated
  5. Push the planning repo with git push so the whole team and every coding agent can read it

Prompt for your agent

Using the Stores guide at openspec.dev/docs/stores for Fission-AI/OpenSpec, set up a planning repo at <store-path> with the openspec/ shape of specs and changes. Expected output: a committed store containing one cross-repo change folder. Verify that the change folder is present and pushed with git before any code repo is modified.

Caveat. The README describes Stores as beta and points to the docs for setup, so the steps here stay at a high level and the guide is the source of truth.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page