Question: How do I set guidance at project level. Example: Kiro Steering Docs, Spec Kit Constitution

[harikrishnan83]

Hello Team,

First of all, congrats on all the traction this repo has been receiving. And I am thoroughly enjoying how fast the workflow is in OpenSpec.

Just a question on how to setup project level Non Negotiable Aspects, Architectural Style etc. which I quite like in GitHub Spec Kit Constitution and Kiro Steering Docs. Tried going through the docs fully, however I did not find anything on similar lines. Do correct me if I am looking for the wrong feature (since this may already be covered in setting up the overall spec).

Thanks.

[harikrishnan83]

I am guessing below line which we run after init, is the equivalent for setup guidance and convention. CMIIW.

Please read openspec/project.md and help me fill it out with details about my project, tech stack, and conventions

[TabishB]

Hey @harikrishnan83

Yep there's a openspec/project.md that you can populate that acts similarly to kiro's steering. Though to be honest, I did lots of testing with and without the steering doc and I found that it usually makes minimal difference in how the agent performs.

Usually the agentic search using ripgrep, glob, ls is usually good enough for an agent to be able to navigate and understand the repository. Hence maybe why I haven't placed a similar level of enough of emphasis on the project doc.