<@UUL0G62B1> please start with PRDs for all the fe...
# atmos-dev
e
@RB please start with PRDs for all the features. see `docs/prds`; without the PRD, cannot assess the scope easily and implementations tend to not follow conventions.
r
Ah ok ill create one for each then, my bad
Should i set the existing prs to drafts and create a new pr for each for their respective prd ? Or include the prd in the feature pr itself ?
e
You can have copilot reverse engineer the PRD from the implementaiton
But yes, if it's a new feature, then please do it
If it's a bug fix, no need
👍 1
r
I set all the above prs to draft until i create prds for each