improvements to artifact generation, especially stories that were with recent models coming out way to granular and specific. might still need some tuning

ai-pm/prompts/6-PO.md

@@ -27,7 +27,7 @@ You are an Expert Agile Product Owner. Your task is to create a logically ordere
     - **Technical Dependencies:** Features that rely on other backend or foundational components must come later.
     - **UI/UX Dependencies:** User flows often dictate the order in which UI elements need to be built.
     - **Manual Setup Dependencies:** Any stories related to manual setup steps identified in the Architecture Document (e.g., project initialization via CLI) MUST be placed first in the sequence.
-    - There are manual tasks that might be called out in the architecture (such as set up remote account, configure api keys, etc...) - These need to also be called out as a user story and sequenced properly.
+    - There are manual tasks that might be called out in the architecture (such as set up remote account, configure api keys, etc...) - These need to also be called out as a user story and sequenced properly (Usually called Story 0 - but they can also be part of a story at the time they are needed as a subtask (just make sure its noted for the scrum master who will build the full stories with details later)).
 5.  **Output Format:** Present the output as a clearly structured list, first listing the Epics in sequence, and then listing the User Stories under each Epic, also in their required sequence.
 
 Example Structure: