Brainforge Knowledge

step-by-step-guide

3 min read

Writing Recipes for Cursor

Quick reference for common writing tasks at Brainforge.

Core rule: Cursor writes fast, but you must review for correctness.

Where files live:

  • Client deliverables (SOWs, PRDs, notes) → client repo
  • Templates and patterns → standards/ (within brainforge-platform)

SOW (Statement of Work)

Goal: Create a client-ready SOW using meeting context and Brainforge standards.

Single template: There is one SOW template. All SOWs and proposals (including GTM sales in knowledge/sales/sales/leads/) use it. Do not use a different structure.

Resources:

  • Template: 02-writing/SOWs/sow-template.md (Sections 1–13 + optional)
  • Checklist: 02-writing/SOWs/sow-checklist.md
  • Examples: 02-writing/SOWs/examples/ (8 examples)
  • SOW Writing Agent: 04-prompts/sow/sow-writing-agent.md

Useful prompts:

  • “Insert the SOW template and fill it using the meeting notes in this repo.”
  • “Summarize the key goals, constraints, stakeholders, and requirements from the discovery docs.”
  • “Highlight any missing assumptions, unclear scope boundaries, or invented claims.”
  • “Rewrite to be more concise and clear without removing important detail.”
  • “Check this against the SOW checklist.”

Output: client-repo/sows/sow-[client-name]-[date].md

PRD (Product Requirements Document)

Goal: Capture requirements clearly without hallucinations.

Resources:

  • Template: 02-writing/PRDs/prd-template.md
  • Checklist: 02-writing/PRDs/prd-checklist.md
  • Examples: 02-writing/PRDs/examples/
  • Prompt guide: 04-prompts/prd/prd-prompts.md

Useful prompts:

  • “Insert the PRD template and fill it using discovery notes and meeting summaries.”
  • “Extract goals, users, key workflows, constraints, and open questions from this repo.”
  • “Convert the requirements section into bullet-point functional requirements that are testable and measurable.”
  • “Identify gaps: missing success metrics, unclear data inputs, unclear user roles, or ambiguous requirements.”
  • “Do not invent details that aren’t in the source material.”

Output: client-repo/prds/prd-[project-name]-v1.md

SOP (Standard Operating Procedure)

Goal: Create a step-by-step process someone can follow without asking questions.

Resources:

  • Template: 02-writing/SOPs/sop-template.md
  • Prompt guide: 04-prompts/sop/sop-prompts.md

Useful prompts:

  • “Insert the SOP template into this file.”
  • “Ask me 5 clarifying questions before writing the SOP.”
  • “Fill the SOP using my answers. Make every step short, numbered, and unambiguous.”
  • “Rewrite so a brand-new person can follow it with zero background knowledge.”
  • “Add a Quality Checks section that tells the reader how to confirm they did it correctly.”

Output: Client repo for client-specific SOPs, or standards/ for reusable internal SOPs.

Meeting Notes

Goal: Turn messy transcripts into a clean, structured summary.

Resources:

  • Template: 02-writing/Project-Setup/meeting-agenda-template.md
  • Workflow guide: 02-writing/Project-Setup/meeting-workflow-guide-template.md

Useful prompts:

  • “Create a structured meeting summary with: Summary, Key Points, Decisions, Action Items, Open Questions.”
  • “Rewrite action items to be specific, testable, and include an owner.”
  • “List any missing context required to follow up properly.”
  • “Extract the key decisions and who made them.”

Output: client-repo/meetings/YYYY-MM-DD-meeting-[topic].md

Client Email

Goal: Draft a concise, professional email.

Resources:

  • Template: 02-writing/Communications/email-update-template.md

Useful prompts:

  • “Draft a client email about [topic]. Professional tone, short, with clear next steps and ask.”
  • “Shorten this by 40% while keeping the key points.”
  • “Make it warmer and more human, but still professional.”

Output: Copy to email tool (usually not committed to repo).

Editing and Polishing (Any Document)

Goal: Improve clarity and catch errors before finalizing.

Resources:

  • Prompt guide: 04-prompts/review/review-prompts.md

Useful prompts:

  • “Improve clarity and remove vague language. Keep meaning the same.”
  • “Check for any invented details or unsupported claims. Flag them.”
  • “Check for internal inconsistencies or contradictions.”
  • “Rewrite in a polished, client-facing tone.”
  • “What sections are weak or vague?”
  • “Does anything sound too AI-generated or fluffy?”

The Brainforge Writing Workflow

  1. Create file
  2. Insert template
  3. Ask Cursor to find context
  4. Ask Cursor to fill template
  5. Ask Cursor to review and polish
  6. You verify
  7. Commit + push

That’s it.

Graph View