This commit updates JMAD.md to:
1. Rebrand "BMad Gem" to "JMAD Gem" throughout the document. References to the original BMad-METHOD and its assets (like team-all.txt and BMad agent personas) are retained for attribution.
2. Modify the information gathering strategy for the JMAD Gem. It's now instructed to:
- Request Jules to generate markdown reports in a `docs/jules_reports/` subdirectory for extensive analysis or multiple file content.
- Ask the user for direct input (e.g., copy-paste) for simpler queries involving one or two files, to help conserve Jules' daily task limits.
3. Ensure workflow examples and key principles reflect these changes.
4. General review for clarity and consistency.
Adds JMAD.md, a comprehensive guide for users on how to:
1. Create a specialized Google Gemini Gem (BMad Gem) using the team-all.txt prompt from the BMad-METHOD.
2. Configure this Gem to leverage Jules for codebase diagnostics and analysis during planning.
3. Detail the workflow for using the BMad Gem to generate Jules-executable plans for both greenfield and brownfield projects.
The document emphasizes the distinct roles of the BMad Gem (planning) and Jules (execution), and the user's role in relaying information between them. It includes examples of how the Gem should instruct the user to query Jules and how the final plan for Jules should be formatted.
google-labs-jules[bot]
Codechilla