Is your feature request related to a problem? Please describe.
I've been looking through the openfasttrace-spec-driven-development skill, and found that it proposes the requirements file structure and a requirement hierarchy.
However, I think one of the main powers of OFT is that it is flexible, and one can structure the requirements however they want, and propose their own requirement chain.
What if the project doesn't have a lot of maintainers, and one doesn't need to have a very deep requirement chain? Or no one has time to maintain arc12 template.
Describe the solution you'd like
Instead of forcing to one file structure and requirement hierarchy, somehow make it general.
Describe alternatives you've considered
My knowledge of Software Engineering is at very low level, and, maybe, on the other hand, what you propose is an industry standard, and other projects have to achieve this level, instead of providing their own schema?
Additional context
I think it might be hard to generalize the skill... One of my ideas (that I used once in AGENTS.md, though nto a skill) is to say that there is some link in the org's repo that explains how the conventions. And then, in the SKILL write that "you should follow the org's convention"
Is your feature request related to a problem? Please describe.
I've been looking through the
openfasttrace-spec-driven-developmentskill, and found that it proposes the requirements file structure and a requirement hierarchy.However, I think one of the main powers of OFT is that it is flexible, and one can structure the requirements however they want, and propose their own requirement chain.
What if the project doesn't have a lot of maintainers, and one doesn't need to have a very deep requirement chain? Or no one has time to maintain
arc12template.Describe the solution you'd like
Instead of forcing to one file structure and requirement hierarchy, somehow make it general.
Describe alternatives you've considered
My knowledge of Software Engineering is at very low level, and, maybe, on the other hand, what you propose is an industry standard, and other projects have to achieve this level, instead of providing their own schema?
Additional context
I think it might be hard to generalize the skill... One of my ideas (that I used once in
AGENTS.md, though nto a skill) is to say that there is some link in the org's repo that explains how the conventions. And then, in the SKILL write that "you should follow the org's convention"