You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been working on different ways to breadcrumb cross-project intelligence for in-context agents, whether bringing in JIRA tickets/epics, doing the spec work itself within the context of VSCode (e.g. "let's look at our current postgres schema within the context of our app and create a proposal for integrating Neo4j as a vector search layer based on its potential use cases, and how it might address the criteria in JIRA epic FC-123").
I'm curious if anyone has tried anything like this, and whether there might be a way to formalize Spec Kit extension outside of a single project. I like the spec kit structure and would like to try leveraging it to define distributed or cross-project system features, rather than simply working in a single project or monorepo.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been working on different ways to breadcrumb cross-project intelligence for in-context agents, whether bringing in JIRA tickets/epics, doing the spec work itself within the context of VSCode (e.g. "let's look at our current postgres schema within the context of our app and create a proposal for integrating Neo4j as a vector search layer based on its potential use cases, and how it might address the criteria in JIRA epic FC-123").
I'm curious if anyone has tried anything like this, and whether there might be a way to formalize Spec Kit extension outside of a single project. I like the spec kit structure and would like to try leveraging it to define distributed or cross-project system features, rather than simply working in a single project or monorepo.
Beta Was this translation helpful? Give feedback.
All reactions