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
Extracting existing standard from codebase is awesome 💪
The next great step would be to have a tool that helps to build a constitution.md file for the project. 💡
It's not only about the standards, but all sorts of decisions that are made once and are generally non-negotiable (so all specs/tasks must follow them / adhere to them). Including tech stack, 3rd party code limitations, code standards included (although that can be done as a reference, so that the standards themselves are more flexible to change), any other rules.
Ideally, it would try to extract as many of these things as possible from the existing codebase (if there is such), and then ask to confirm each key point/decision. For a bare codebase, it would probably have hardly any values to offer and instead of confirmations it would be more about providing decisions to the specific questions.
So far this is a very rough idea, but I hope you see what I mean and where the value of this would be.
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.
-
Extracting existing standard from codebase is awesome 💪
The next great step would be to have a tool that helps to build a constitution.md file for the project. 💡
It's not only about the standards, but all sorts of decisions that are made once and are generally non-negotiable (so all specs/tasks must follow them / adhere to them). Including tech stack, 3rd party code limitations, code standards included (although that can be done as a reference, so that the standards themselves are more flexible to change), any other rules.
Ideally, it would try to extract as many of these things as possible from the existing codebase (if there is such), and then ask to confirm each key point/decision. For a bare codebase, it would probably have hardly any values to offer and instead of confirmations it would be more about providing decisions to the specific questions.
So far this is a very rough idea, but I hope you see what I mean and where the value of this would be.
Beta Was this translation helpful? Give feedback.
All reactions