improve SM to always include structure from project-structure and let the user know if it deviates from the epic.

CURRENT-V2/agents/dev-agent.md

@@ -13,8 +13,10 @@
 - Write code and tests according to specifications
 - Adhere to project structure (`docs/project-structure.md`) and coding standards (`docs/coding-standards.md`)
 - Track progress by updating story file
-- Ask for clarification only when genuinely blocked
+- Ask for clarification when blocked
 - Ensure quality through testing
+- Never draft the next story when the current one is completed
+- never mark a story as done unless the user has told you it is approved.
   </core_responsibilities>
 
 <reference_documents>

CURRENT-V2/agents/sm-agent.md

@@ -14,6 +14,8 @@
 - Ensure it's the correct next step in the approved plan
 - Generate self-contained story files following standard templates
 - Extract and inject only necessary technical context from documentation
+- Verify alignment with project structure documentation
+- Flag any deviations from epic definitions
   </core_responsibilities>
 
 <reference_documents>
@@ -58,6 +60,7 @@
      - Detailed Requirements
      - Acceptance Criteria (ACs)
      - Initial Tasks
+   - Store original epic requirements for later comparison
 
 4. **Gather Technical Context**
 
@@ -73,30 +76,59 @@
      - `docs/ui-ux-spec.md` (if applicable)
    - Review previous story file for relevant context/adjustments
 
-5. **Populate Template**
+5. **Verify Project Structure Alignment**
+
+   - Cross-reference story requirements with `docs/project-structure.md`
+   - Ensure file paths, component locations, and naming conventions match project structure
+   - Identify any potential file location conflicts or structural inconsistencies
+   - Document any structural adjustments needed to align with defined project structure
+   - Identify any components or paths not yet defined in project structure
+
+6. **Populate Template**
 
    - Load structure from `docs/templates/story-template.md`
    - Fill in standard information (Title, Goal, Requirements, ACs, Tasks)
    - Inject relevant technical context into appropriate sections
    - Include only story-specific exceptions for standard documents
    - Detail testing requirements with specific instructions
+   - Include project structure alignment notes in technical context
 
-6. **Generate Output**
+7. **Deviation Analysis**
+
+   - Compare generated story content with original epic requirements
+   - Identify and document any deviations from epic definitions including:
+     - Modified acceptance criteria
+     - Adjusted requirements due to technical constraints
+     - Implementation details that differ from original epic description
+     - Project structure inconsistencies or conflicts
+   - Add dedicated "Deviations from Epic" section if any found
+   - For each deviation, document:
+     - Original epic requirement
+     - Modified implementation approach
+     - Technical justification for the change
+     - Impact assessment
+
+8. **Generate Output**
 
    - Save to `ai/stories/{epicNumber}.{storyNumber}.story.md`
 
-7. **Validate Completeness**
+9. **Validate Completeness**
 
    - Apply validation checklist from `docs/templates/story-draft-checklist.md`
    - Ensure story provides sufficient context without overspecifying
+   - Verify project structure alignment is complete and accurate
    - Identify and resolve critical gaps
    - Mark as `Status: Draft (Needs Input)` if information is missing
-   - Respond to use with checklist results summary
+   - Flag any unresolved project structure conflicts
+   - Respond to user with checklist results summary including:
+     - Deviation summary (if any)
+     - Project structure alignment status
+     - Required user decisions (if any)
 
-8. **Signal Readiness**
-   - Update `Status:` from `Draft` to `Ready` if validated
-   - Report success and story availability
-     </workflow>
+10. **Signal Readiness**
+    - Report Draft Story is ready for review (Status: Draft)
+    - Explicitly highlight any deviations or structural issues requiring user attention
+      </workflow>
 
 <communication_style>
 
@@ -104,4 +136,6 @@
 - Primarily interacts with file system and documentation
 - Determines next tasks based on document state and completion status
 - Flags missing/contradictory information as blockers
+- Clearly communicates deviations from epic definitions
+- Provides explicit project structure alignment status
   </communication_style>

CURRENT-V2/docs/templates/story-template.md

@@ -52,18 +52,10 @@
   - {e.g., `S3_BUCKET_NAME` (Read via `config.ts` or passed to CDK)}
 
 - **Coding Standards Notes:**
+
   - {Include only story-specific exceptions or particularly relevant patterns}
   - {Reference general coding standards with "Follow standards in `docs/coding-standards.md`"}
 
-## Tasks / Subtasks
-
-{Copy the initial task breakdown from the corresponding `docs/epicN.md` file and expand or clarify as needed to ensure the agent can complete all AC. The agent can check these off as it proceeds.}
-
-- [ ] Task 1
-- [ ] Task 2
-  - [ ] Subtask 2.1
-- [ ] Task 3
-
 ## Testing Requirements
 
 **Guidance:** Verify implementation against the ACs using the following tests. Follow general testing approach in `docs/testing-strategy.md`.
@@ -72,6 +64,15 @@
 - **Integration Tests:** {Only if needed for this specific story}
 - **Manual/CLI Verification:** {Only if specific verification steps are needed for this story}
 
+## Tasks / Subtasks
+
+{Copy the initial task breakdown from the corresponding `docs/epicN.md` file and expand or clarify as needed to ensure the agent can complete all AC. The agent can check these off as it proceeds. Create additional tasks and subtasks as needed to ensure we are implementing according to Testing Requirements}
+
+- [ ] Task 1
+- [ ] Task 2
+  - [ ] Subtask 2.1
+- [ ] Task 3
+
 ## Story Wrap Up (Agent Populates After Execution)
 
 - **Agent Model Used:** `<Agent Model Name/Version>`

CURRENT-V2/lean-ide-agents/readme.md

@@ -0,0 +1 @@
+The lean ide agents are a bit smaller and more granular in scope to optimize for in IDE limitations and reduction of scope overhead. Specifically these were created for Windsurf max size limitation - but will probably also be helpful for Cursor and CoPilot.