120 Commits

Author SHA1 Message Date
Brian Madison
b3d455d0de architect checklist draft and readme updates 2025-05-04 11:28:11 -05:00
Brian Madison
e69d136224 gem enhancements with prompt examples for the larger context windows of the web gem or gpt 2025-05-04 10:32:35 -05:00
Brian Madison
b134905083 architect 3 operating modes - mode 2 main mode optimized 2025-05-04 10:04:42 -05:00
Brian Madison
a1ef16b8bc the PM has been improved to ensure it is eliciting proper information for epic 1, and also coaching the user into defining the MVP. instructional description added to the readme also for the PM 2025-05-04 09:26:26 -05:00
Brian Madison
f4b7cbd377 analyst updated with pm prompt output and missing brainstorming mode critical for ideation 2025-05-04 08:48:33 -05:00
Brian Madison
8c06be3fb0 more clarity in the instructions for new users 2025-05-03 18:44:43 -05:00
Brian Madison
a338fab016 custom gems and gpts! also a few minor agent and template corrections 2025-05-03 12:38:14 -05:00
Brian Madison
1f6c4c525c massive v2 update, and v1 moved to legacy folder 2025-05-02 23:06:11 -05:00
Brian
0012b71f29 Update README.md
Quick note about previous repo that this one replaces:

This method is a full replacement and enhancement to what was hinted at and partially described in the custom-agents-rules-generator [this repo](https://github.com/bmadcode/cursor-custom-agents-rules-generator). This is now more tailored to being generic and working with any IDE (not just cursor specific) and the custom rule used to generate rules is no longer needed in Cursor anyways as of 0.49x (And the other IDE's now support auto rule generation also) and with custom agents and agile artifacts, rules become less necessary. Rules that apply to general standards can be build into your developer agents. For example, you can expand the dev persona agent herein to be a typescript dev agent, or a python dev agent, or even a ui dev agent - all with the best practices you want it to follow baked in! By having multiple dev types, you can have specialized devs with the rules in their context primed for what they will be working on - instead of overall bloated rules that do not apply to every task at hand. This is all optional, but you can start to see why this replaces the detailed rules based workflows.

Where IDE rules will still apply, is for fine tuning quick one off rules as you are going if you find the agent making many mistakes in certain ways. In the future you can craft this adherance into your agile artifacts and stories, or the custom mode configurations!
2025-04-27 15:53:47 -05:00
Brian Madison
4de795fad8 adding back the SM with suggestion and rationale to not use it in its current state 2025-04-26 10:24:01 -05:00
Brian Madison
c15c75777c doc clarification on project setup 2025-04-25 23:02:15 -05:00
Brian Madison
64ef5b6d69 add some notes about the templates folder 2025-04-25 22:58:43 -05:00
Brian Madison
5ec77473a6 simplified and corrected a few mistakes in mode prompts 2025-04-25 22:54:05 -05:00
Brian Madison
64f9a9c3f8 massive update and guidance. 2025-04-16 22:13:31 -05:00
Brian Madison
965514f00a improvements to artifact generation, especially stories that were with recent models coming out way to granular and specific. might still need some tuning 2025-04-15 20:11:19 -05:00
Brian Madison
c709dec61e final cleanup ready for initial release 2025-04-13 17:56:54 -05:00
Brian Madison
765e928647 final note on indexing ignorance of some files in projects 2025-04-13 17:45:34 -05:00
Brian Madison
3460e94b70 Gems Prompts 2025-04-13 17:44:00 -05:00
Brian Madison
a3c12fd11c simple spelling of the method alignment 2025-04-13 13:39:26 -05:00
Brian Madison
67796c03c5 Initial Commit of the BMAaDd Workflow 2025-04-13 13:12:47 -05:00