Skip to main content

​
What You’ll Learn

  • How to write a custom document prompt
  • What makes a good custom prompt
  • Examples you can use or adapt
  • When custom beats built-in

​
How It Works

  1. Open the Scribe panel (right sidebar)
  2. Click Master Document Generator
  3. Select Custom as the document type
  4. Write your instructions in the prompt field
  5. Choose your AI engine
  6. Click Generate
The AI reads your entire conversation and produces a document following your specific instructions.

​
Writing Effective Custom Prompts

​
Be Specific About Structure

Tell the AI exactly what sections you want: 
Generate a document with these sections:
1. Executive Summary (3 sentences max)
2. Problem Definition (what's broken, who's affected)
3. Proposed Solutions (table: option, cost, timeline, risk)
4. Recommendation (which option and why)
5. Next Steps (numbered action items with owners)

​
Define Tone and Audience

Write this as an internal memo for our engineering team.
Tone: technical, direct, no marketing language.
Assume the reader knows our tech stack.

​
Set Length Constraints

Keep the total document under 500 words.
Each section should be 2-3 sentences maximum.
Use bullet points over paragraphs.

​
Specify Format Details

Use markdown tables for any comparisons.
Bold key terms on first use.
Include a TL;DR at the top (one sentence).
Number all recommendations.

​
Examples

​
Investor Update Email

Format this as a monthly investor update email:
- Opening: one sentence on overall status
- Metrics table: MRR, DAU, burn rate, runway
- Top 3 highlights (one sentence each)
- One challenge and how we're addressing it
- One ask (if any)
- Close: one-line forward-looking statement
Keep it under 300 words. Tone: confident, transparent, concise.

​
Product Requirements Document

Generate a PRD with:
- Feature name and one-line description
- User stories (as a [user], I want [action], so that [benefit])
- Acceptance criteria (given/when/then format)
- Technical constraints
- Out of scope (explicit exclusions)
- Success metrics (how we measure this worked)

​
Weekly Team Standup Summary

Summarize this conversation as a weekly standup:
- What we accomplished (bullet points)
- What's blocked (with blocker owner)
- What's planned next week
- Decisions made (if any)
- Risks raised (if any)
Format for Slack: use emoji bullets, keep it under 200 words.

​
Sales Battle Card

Create a competitive battle card:
- Our strengths vs [Competitor] (3-5 bullets)
- Their strengths vs us (honest assessment)
- Common objections and responses (table)
- Win themes (what to emphasize in pitch)
- Landmines (what NOT to discuss without prep)
Audience: sales team. Direct, actionable.

​
Board Meeting Prep

Prepare board meeting talking points:
- 3 key messages we want the board to leave with
- Supporting data for each message
- Anticipated tough questions and prepared responses
- Decision items requiring board input
- Framing for each decision (our recommendation + why)

​
When Custom Beats Built-In

Use custom prompts when:
  • Your format doesn’t match any of the 22 types
  • You want a specific internal format your team uses
  • You need a hybrid of multiple document types
  • You want very specific length/tone constraints
  • You’re creating templates for repeated use

​
Tips

  • Save your best custom prompts somewhere - you’ll reuse them
  • Be explicit about what to include AND what to exclude
  • If the output isn’t right, refine your prompt and regenerate - it costs nothing
  • Start with a built-in type and customize from there if you’re not sure what you want
  • The more specific your instructions, the better the output matches your expectations

​
Still Need Help?

Reach out to us at [email protected] or use the feedback button in the app.