Beta 3 Feature List and Community BIG THANK YOU! #44
Replies: 3 comments 6 replies
-
|
I have also tested a lot and ChatGPT currently does not come close to Gemini 2.5 pro, I use deep research with Gemini 2.5 a lot and try to verify every assumption through deep research and it has often turned out that the assumptions were wrong. 2 things that I personally find important.
SEO Checklist1. Technical SEO:
2. On-Page: Content & Keywords:
3. On-Page: Structure & Metadata:
4. Off-Page Factors:
5. User Experience (UX):
6. Local SEO (if relevant to the business model):
7. Future Orientation:
|
Beta Was this translation helpful? Give feedback.
-
|
Foremost, thank you so much! I'm still on v2 but wanted the highlight story ordering instructions in the SM prompt and sequencing in general:
I also had to update Cursor agent instructions to always use What are your thoughts on sequencing? Should this be sorted out before epics ever reach the SM, or should BMAD method follow Scrum/agile more closely (as I had to do in my case)? I haven't tested v3, so maybe this is not even an issue anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Brian - thank you for your Bmad Methods again and for starting this project, YouTube and repository and making it available to all of us aspiring developers! And of Cource, I just also want to thank of of you others out there contributing to this - I't's really awesome! Things are moving fast, I just finished a website using the origional V1, my next project is goiong to use V2, but i see we are already getting onto V3 BETA! - such good stuff! I guess the only think a can contribute right now, is my 50c - I agree, we need that 1M context window that Gemini 2.5 offers! What i have discovered is that these models all seem to be carving out niches for themselves, and I find that I'm using more and more different models for different needs, e.g. Gemini 2.5 for big context window, GPT for images etc. Like most, ive been IDE hopping, but i see big potential again for terminal based AIDER, but it's still hard to see a clear winner here. My take, we should focus on owning what we do to avoid vendor lock in (We also need to make a living, they cant have the whole cake to themselves). finally, I like the control these new web agents give us. I actually feel like i'm contributing as an engineer! or should i say, i'm able to x10 my junior engineering skills. I still dont trust YOLO mode - I like to do things step by step, yes, it slows me down a bit, but I get to wrestle with all the ins and outs of my project - I truly own it! and I can speak to it! Thanks all! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Really want to thank everyone that has commented, contributed or raised issues - so much of this has fed into V3 Beta - mostly thanks to all of you for testing and trying to use these agents and workflows, and reporting also issues with different environments and platforms.
Some key items (and I am probably forgetting a lot) that will be in the final beta release (and are mostly in place)
Reminder first - It's really hard to beat the performance of the Web Agents in Gemini 2.5 pro - As much as I love chatGPT - these things really need the power of the massive 1M context window - and a larger 2M is coming soon. For document wrangling and the type of deep thinking and planning we are doing to produce these amazing detailed artifacts that will improve our agent performance in development - large context is king still!
What remains before removing the Beta tag?
BTW - Ideas are already stewing for V4 :)
Beta Was this translation helpful? Give feedback.
All reactions