update

Author: Brian Casel

CHANGELOG.md

@@ -10,6 +10,7 @@ https://buildermethods.com/agent-os
 - Tightened up template and istructions for writing spec.md, aiming to keep it shorter, easier to scan, and covering only the essentials.
 - Tweaked create-task-list workflow for consistency.
 - When planning product roadmap, removed instruction to limit it to 12 items.
+- Clarified instructions in implement-tasks in regards to useage of Playwright and screenshots.
 
 ## [2.1.0] - 2025-10-21
 

profiles/default/workflows/implementation/implement-tasks.md

@@ -9,8 +9,12 @@ Implement all tasks assigned to you and ONLY those task(s) that have been assign
 
 ## Guide your implementation using:
 - **The existing patterns** that you've found and analyzed in the codebase.
+- **Specific notes provided in requirements.md, spec.md AND/OR tasks.md**
+- **Visuals provided (if any)** which would be located in `agent-os/specs/[this-spec]/planning/visuals/`
 - **User Standards & Preferences** which are defined below.
 
 ## Self-verify and test your work by:
 - Running ONLY the tests you've written (if any) and ensuring those tests pass.
 - IF your task involves user-facing UI, and IF you have access to browser testing tools, open a browser and use the feature you've implemented as if you are a user to ensure a user can use the feature in the intended way.
+  - Take screenshots of the views and UI elements you've tested and store those in `agent-os/specs/[this-spec]/verification/screenshots/`.  Do not store screenshots anywhere else in the codebase other than this location.
+  - Analyze the screenshot(s) you've taken to check them against your current requirements.