How Can We Setting Up a Custom Knowledge Base for Project #213
SunshinePeace213
started this conversation in
General
Replies: 1 comment 1 reply
-
|
If you have robust documentation already, such as a README.md that describes your project's objectives, approach, and tech stack, then you can just point your agents to this. If you don't, you can prompt the BMAD Orchestrator to create one for you. It'll likely tap the roles/checklists for the Product Manager and Architect - and perhaps the Analyst - to have conversations with you to help create such documentation. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm new to this platform and recently upgraded to Version 4. It's a fantastic update that integrates the BMAD-agent directly into the IDE, making it even simpler to work with different agents.
To further enhance collaboration among various agents, it would be beneficial to incorporate our project's own knowledge base. However, for new users, are there any recommended methods or initial setup procedures – perhaps akin to prompting the BMAD-agent – that could help define the project scope? This would allow other agents to better understand our objectives and provide more customized outputs.
Beta Was this translation helpful? Give feedback.
All reactions