Shaping your AI specializations: expert subroles (working with the ROLES folder and the /updateRoles command)

Once you have your know-how uploaded and processed (after successfully completing the /update command), it's time for the next crucial step: creating expert subroles. These subroles are like specialized "thought frames" or "expert identities" that your AI Expert dynamically deploys to best and most relevantly respond to specific questions and topics of conversation with users.

11.1 What are expert sub-roles and why are they key to the quality of responses?

Think of your AI Expert as one highly capable professional with many specialties. When a user asks him about topic A (e.g., "How to prepare content for a sales webinar?"), the AI internally activates the subrole "Webinar Content Creation Specialist". If the conversation then turns to topic B (e.g., "And what technical tools do you recommend for a webinar?"), the AI seamlessly transitions to the "Technical Advisor for Webinar Platforms" subrole.

• Dynamic activation: these sub-roles are activated and changed automatically in the background according to the current context of the conversation. The user doesn't directly see them or need to specify which role the AI should use - the AI will know this on its own from its queries.
• Detailed definitions from your know-how: Each expert subrole has its own detailed written definition. This definition is stored as a separate Google Document in the ROLES folder on your Google Drive and is automatically generated from your uploaded know-how. It typically contains:
  • The specific focus and goals of the subrole.
  • Key methods, frameworks, practices and knowledge relevant to that specialty (extracted from your content).
  • Alternatively, a slightly modified communication style that better fits the area of expertise.
• Quality relevance: with these sub-roles defined in detail, your AI Expert can provide significantly more specific, insightful and contextually relevant advice. This is the key to making AI truly act as a true expert in your domain, not just a general information seeker. The number of roles can run into the tens or hundreds, depending on the scope and complexity of your expertise.

11.2 How the list of suggested role names is created (working with the ROLES/list_of_roles.gdoc file)

After each successful completion of the /update command (when your know-how is uploaded and processed), BuddyPro will analyze all the currently available content in your knowledge base. Based on this analysis, it identifies key topics and natural specializations.

• List of role names: The names of these potential expert sub-roles are saved (or updated) in the Google Document list_of_roles.gdoc, which you can find on your Google Drive in the ROLES folder. Each role name is on a separate line.
• What to do with this list?
  • Take a look (recommended): you'll get an interesting insight into how AI structures your expertise.
  • Leave it alone (most common practice): An automatically designed list is usually very high quality.
  • Add custom roles (optional, for advanced): If the AI hasn't recognized an important specialization for which you have a foundation, you can add the role name to a new line. The AI will try to find relevant content for it and write a definition.

11.3 Key step: automatically create detailed content (definitions) for each role ( /updateRoles)

In order for your AI Expert to act competently in these specializations, it needs a detailed written definition for each of them. To create (or regenerate/update) these definitions for all the roles listed in list_of_roles.gdoc, use the command you enter in chat with your BuddyPro instance:

/updateRoles

• What happens when you enter the /updateRolescommand ?
  1. BuddyPro retrieves the current list of role names from ROLES/list_of_roles.gdoc.
  2. For each role name that is not already defined by a custom file in the ROLES folder , it performs an in-depth analysis of your uploaded know-how.
  3. From your know-how, it will select the most relevant information, methods and procedures for the role.
  4. Based on this, it will write a comprehensive, usually several pages long, detailed description (definition) of the role.
  5. This description is saved as a separate Google Document in the ROLES folder (e.g. Role_Specialist_on_SEO.gdoc).
• Progress and completion:
  • Content generation can take anywhere from a few minutes (for dozens of roles) to several hours (for hundreds of complex roles).
  • BuddyPro can keep you informed of the status of the processing in Telegram.
  • If you have hundreds of roles, you may need to run the /updateRoles command repeatedly. The AI remembers which roles it has already processed, and will continue or process only roles not yet defined the next time it runs.
  • You can tellif all roles have completed successfully by the fact that when you re-enter the /updateRoles command, BuddyPro responds very quickly (often almost immediately) with a completion message (e.g. Role definitions updated successfully. or finished successfully) because it has nothing new to generate.

11.4 Additional commands for more advanced management of role content generation

In addition to the bulk /updateRoles command, you have more targeted tools:

• ✨ /updateNextRole
  • Generates (or updates) content for only one, subsequent, pending role from the list_of_roles.gdoc list. Useful for incremental generation or testing.
• 🎯 /updateRole:{name_of_role}
  • Generates (or updates) content for one specific role you specify.
  • Instead of {name_of_role}, specify the exact role name as it appears in list_of_roles.gdoc (e.g. Expert_on_Email_Marketing).
  • Ideal for:
    • Retrieving a manually modified role definition.
    • Generating content for a newly added role name in the list.
• 🛑 /stopUpdateRoles
  • Stops the currently running process of generating content for roles.

11.5 What does a Google Doc with a specific role definition contain?

Each Google Document role in the ROLES folder is a detailed "script" for the AI in that subrole. It typically contains:

• Role Name: A clear specialization.
• Purpose and Goals: What the AI in this role is supposed to accomplish.
• Core competencies and knowledge: A list of expertise derived from your know-how.
• Preferred methods and practices: Specific techniques and strategies from your know-how.
• Specific communication style (if relevant)
• Examples of typical issues/situations.

The language of the role definition (e.g. Czech, English) may vary depending on the source know-how, but does not affect the AI's ability to communicate with the user in their preferred language.

11.6 Options for manual editing of the content (definitions) of expert sub-roles

In most cases (>99%) there is no need to manually intervene in automatically generated role definitions. The BuddyPro platform creates them comprehensively based on your know-how.

• When exceptionally consider manual editing?
  • When there are repeated problems with the behavior in a given role: If the AI in a specific subrole repeatedly responds inappropriately, incompletely, or contrary to your approach, despite sufficient know-how and a well-configured System Prompt. (Use the /lastRole and /investigateAnswer:{message} commands for diagnostics.)
  • To insert very specific instructions or links: e.g., a recommendation for a specific product, course, video, or specific method in a very narrow context.
• How to make a manual edit:
  1. Identify the file: In the ROLES folder, locate the .gdoc file of the role being edited.
  2. (Recommended) Create a backup: Copy the original file.
  3. Make textual changes. Try to maintain style and structure.
  4. In Telegram, run the command to update this particular role: /updateRole:{updated_role_name}. The AI will retrieve your edited version.
• ⚠️ Note: This is the procedure for advanced debugging. Unprofessional interventions can degrade the consistency of the AI. If you are unsure, consult support or the community. In most cases, leave the roles as generated by BuddyPro. If you want the AI to completely rewrite the role definition based on new or significantly updated know-how (not just load your manual modification of an existing definition), delete the appropriate .gdoc file for the role in the ROLES folder on Google Drive, then run /updateRoles (or /updateRole:{role_name} if the role name still exists in list_of_roles.gdoc). The AI will then generate a completely new definition for that role.

---

---

Frequently Asked Questions (FAQ) for this step:

• What is the difference between /update and /updateRoles?
  • The/update processes your uploaded source files (PDFs, videos, text, URLs) in the sources folder, creates transcripts from them, stores them in a vector database, and updates the list of role names in ROLES/list_of_roles.gdoc. It also retrieves changes in system_prompt.gdoc and onboarding.gdoc. So it is a command for updating "raw" know-how and basic settings.
  • The/updateRoles takes the list of role names from list_of_roles.gdoc and generates a detailed written definition (role content) for each name based on the currently processed know-how. It stores these definitions as separate .gdoc files in the ROLES folder. It is thus a command to create or update "expert specializations" of your AI.
  • The order is important: Always /update first (to keep the know-how up-to-date), and then /updateRoles (to generate roles from the current know-how).
• Do I always have to generate content for all roles at once using /updateRoles?
  • No. You can use /updateNextRole to generate one role at a time, or /updateRole:{name_of_role} to generate targeted content for a specific role. This is useful for testing or incremental builds.
• If I manually edit the contents of the .gdoc file of a role, will the AI overwrite my changes the next time I run /updateRoles?
  • If you run the generic /updateRoles command, the AI should respect the existing file content and not automatically overwrite it if the file already exists. Rather, it tries to process new or pending roles from the list.
  • If you want the AI to retrieve your manual change, it is best to use the targeted /updateRole:{update_role_name} command.
  • If, on the other hand, you want the AI to ignore your manual changes and completely overwrite the role definition based on your current know-how (e.g., you messed up or want to start over with automatic generation), then it's best to delete the entire .gdoc file for that role from the ROLES folder and then use /updateRoles or /updateRole:{role_name}. The AI will then create a new, clean definition.

---

---