README

Communications Templates

This folder contains templates for client and internal communications. Use these templates to maintain consistent, professional communication across all Brainforge engagements.

---

Templates Included

Template	Purpose	When to Use
email-update-template.md	Client status updates and follow-ups	Weekly or milestone updates
slack-notes-template.md	Running documentation of async conversations	Capturing important Slack threads
email-communication-standards.md	Standards for calendar titles, meeting links, and client email writing	Any Gmail/Calendar client communication workflow

---

How to Use These Templates

Client Email Updates

1. Copy email-update-template.md to your client repo’s /emails/ folder.
2. Name the file with the date: YYYY-MM-DD_update_topic.md.
3. Fill in the sections with project-specific content.
4. Review for tone and completeness before sending.

Weekly Kick-Off Updates

To generate weekly kick-off updates (last week’s achievements + this week’s focus) for one or more clients: follow the SOP standards/04-prompts/weekly-kick-off-update-sop.md and run the Cursor command .cursor/commands/weekly-kick-off-update.md (or say “Run weekly kick-off update” in chat). The agent will ask for target client(s), then for each client gather Linear and recent transcripts, save a draft to knowledge/clients/{client}/meeting-notes/YYYY-MM-DD_weekly-kick-off-update.md, and output a Slack-formatted summary in the chat for copy-paste. Structure follows the email-update template adapted for kick-off format (concise summary; no Linear ticket IDs in client-facing text).

Slack Notes

1. Copy slack-notes-template.md to your client repo’s /slack_notes/ folder.
2. Name the file descriptively: running_slack_messages.md or YYYY-MM-DD_topic.md.
3. Add important messages as they occur.
4. Periodically synthesize into meeting notes or the Discovery Wiki.

---

Best Practices

Email Communications

• Keep updates concise, one page maximum.
• Lead with the most important information.
• Include specific next steps with owners and dates.
• Use bullet points for easy scanning.
• Proofread for clarity and professionalism.

Slack Documentation

• Capture context, not just the message.
• Note who said what and when.
• Link to related documents or threads.
• Flag decisions and action items clearly.
• Review weekly and transfer important items to permanent documentation.

---

Questions

If you have questions about these templates or want to propose improvements, discuss with the team.