Add technical tracking and task issue templates, tweak existing issue templates. #39
Conversation
| - For frontend new features: include screenshots/mockups of desired end state | ||
| - For backend work: describe the expected behavior, not the implementation | ||
|
|
||
| Focus on WHAT and WHY, not HOW. The developer determines the implementation. |
There was a problem hiding this comment.
Generally, definitely. In some cases, I've found it important to specify architecture. But perhaps it doesn't need to reflected in a template. We can chat about it more later.
There was a problem hiding this comment.
I agree with this @MisRob -- sometimes specifying the implementation is important, although my suspicion is that at least part of this is to support AI written issues that are overly detailed. Is that right, @rtibbles. Maybe a small addition such as "add specific architectural constraints or considerations" could be enough?
There was a problem hiding this comment.
Yes, this was definitely biased by the tendency of LLMs to just write out the implementation, but I do think it goes overboard. Updating before merge.
marcellamaki
left a comment
marcellamaki
left a comment
There was a problem hiding this comment.
One small suggestion to Misha's point, but not blocking. (And I think internally, we would already be doing this)
Summary
Adds new technical tracking issue and task templates
Makes small tweaks to other existing templates for consistency
Adds AI generation comment to all tempaltes.