Add Contributing Section to README to explain the use of openspec in this project

[ASRagab]

🗣️ Foreword

Thank for taking the time to fill this feature request fully. Without it we may not be able to , and the issue may be closed without resolution.

:person_frowning: Problem Statement

Users wishing to contribute may not be familiar with openspec or how this project intends to use it. It might be worth adding a section that explains the basic workflow as well as any preferences specifically for this project (i.e. when to archive, etc.)

❔ Possible Solution

I think mostly the contributing section should contain a reference to the openspec documentation, and a recommended workflow for the project using openspec native concepts. It should include worfklows, for features vs bug fixes (if there is a desire to treat those differently), as well as how to handle PR comments vis-a-vis the openspec workflow.

⤴️ Describe alternatives you've considered

N/A

➕ Additional context

I think openspec is useful, I think also how to leverage it for context would be worth elucidating.

[johannesjo]

Thank you very much! Personally I find it a bit cumbersome and that I prefer to read the actual code rather than the spec files. What's your experience to this point? Do you think it's an improvement?

[ASRagab]

I think it's useful context for agents building features-and I do read the artifacts during the exploring and specing phases. It does add a lot to each PR however. My last PR was only about 300 SLOC but the overall diff was over +1100 lines - so it's definitely noisy. If you decide to keep it I think some explanation is warranted in a Contributing section.

[johannesjo]

Let's test it for another week and then decide together. Maybe I need to give it another shot :)