Content Design & Brief Creation › Create Content Brief
Author StackNarrative Team
Uses a pre-configured Gemini Gem to turn a blog topic or core thesis into a detailed, research-backed, execution-ready blog brief. The Gem researches forums, industry sources, reports, expert interviews, and other relevant material before producing the brief, then structures recommendations through both a B2B content strategist POV and a hospitality operations expert POV.
A reusable Gem removes the need to recreate the same research and briefing instructions for every article. It captures content methodology, audience context, quality standards, research process, SEO/AEO requirements, and output structure in one reusable workflow, making briefs more consistent across writers and content teams.
Content strategists; content marketing managers; B2B SaaS marketing teams; Hotel Tech and Travel Tech marketers; founders creating thought leadership; agencies managing multiple content briefs; editorial teams working with freelance writers.
Tools required
Google Gemini; Gemini Gems; web/research access within Gemini; optional Google Docs or another document tool for storing the generated brief.
Prerequisites
A clearly defined blog topic or core thesis; basic understanding of the target audience; relevant business/product context; a defined content objective is recommended; a pre-configured Gemini Gem containing the role, research methodology, quality rules, and output format; the Gem should be tested on several topics before production use.
Inputs
Required: blog topic
Expected output
A complete blog brief containing: Brief Overview; Introduction Framework; B2B Content Strategist POV; Hospitality Operations Expert POV; References & Strategic Citations; Important Brief Notes; and an SEO/AEO FAQ Engine.
Start a new Gem
Open Gemini → Gems → Create a new Gem. Give the Gem a clear Name that describes the specific task it performs and add a short Description explaining what it does and who it is designed for. Keep both task-specific.
Write the Gem's Instructions
This is the core of the Gem. It tells Gemini how to behave, think, research, and produce the work. Start by defining the role, then provide context, define the mission, explain the methodology, add quality standards and guardrails, and define the output structure.
Define the role
Specify who the Gem is, what expertise it should bring, and what professional perspective it should use. Avoid vague roles such as "AI content assistant." Example: the Blog Brief Gem acts as a Lead Content Strategist and Executive Editor specializing in Hotel Tech, B2B SaaS, and strategic narrative.
Give it context
Add the company or industry, audience, business problems, goals, terminology, and other stable context an expert would need. Keep changing information for the runtime input rather than putting every possible topic into the Gem.
Define the mission and methodology
State exactly what the Gem is responsible for producing and explain how it should perform the task. For research-heavy work, specify the research sources, questions to investigate, evidence to prioritize, and how research should influence the output.
Add quality rules and guardrails
Tell the Gem what it should always do, never do, and verify. Include evidence requirements, brand standards, terminology to avoid, accuracy rules, desired specificity, and common failure modes.
Define the output structure
Specify mandatory sections, fields, quantities, detail level, and formatting. A repeatable automation should produce a predictable output that can move into the next process without being restructured.
Add Knowledge
Use the Knowledge section for documents and information the Gem should consistently reference. Examples: upload your company brand document so the Gem follows approved voice, terminology, messaging, and positioning; upload product documentation so it uses accurate product information; upload a content strategy or editorial playbook so briefs align with broader goals; upload ICP/persona documents so it understands the audience; upload successful content examples so it understands the expected quality, structure, and style.
Set the right tools
Select the capabilities the Gem actually needs. For research-heavy content workflows, web/search access can be important for current sources, industry research, statistics, or user discussions. Instructions define how the Gem should work; tools give it capabilities; Knowledge gives it the organization's source of truth.
Use the exact prompt below
The exact prompt used for the Blog Brief Generator is provided in the Prompt / instructions section below. Copy it as a starting point, then adapt the role, context, methodology, guardrails, and output structure to your own repeatable content task.
Test and refine
Run several real examples through the Gem. Check whether it follows the role, uses the provided Knowledge, applies the methodology, and produces the required format. If the same problem appears repeatedly, improve the Gem's instructions or Knowledge rather than manually fixing every output.
Publish and share
Once the Gem consistently produces the expected quality, save/publish it and use the share option to generate a link. Add the live Gem link to the Template / Example Gem field so people can immediately test the working example.
Key principle
Instructions = how the Gem should work. Tools = what the Gem can do. Knowledge = what the Gem should know and reference.
Sample input: Topic: How AI is changing hotel guest communication
Sample Output:
1. BRIEF OVERVIEW
Blog Title: Why Hotel Tech Startups Are Failing at AI Content (And How AI Content Operations Fixes Product Drift)
Target Word Count: 1,800 – 2,200 words
Meta-Title: Why Hospitality Tech Needs AI Content Operations
Meta-Description: Stop publishing fluff. Learn how AI content operations connects hotel tech software features to real hospitality ROI and eliminates buyer friction.
Core Purpose / Problem Solved: Eliminates "Product Drift" and content production bottlenecks by replacing generic LLM drafting with a research-backed AI content engine grounded in hospitality operations.
Target Audience: Hotel Tech Founders, B2B SaaS CEOs, CMOs, Heads of Marketing, and Product Marketing Managers at growth-stage hospitality tech startups.
Primary Keywords: AI content operations hospitality tech, B2B hotel tech content strategy, hotel tech product messaging.
Long-Tail Keywords: how to fix product drift in hotel tech, AI content engine for hospitality SaaS, converting hotel tech features to operational ROI, B2B SaaS buying committee content strategy.
2. INTRODUCTION FRAMEWORK
(output continues, use the gem link below to see it yourself)
Prompt / instructions
The exact prompt used to build the example Gem is provided below. This is a working example you can copy and adapt for your own Gem -----> You are the Lead Content Strategist and Executive Editor for StackNarrative—a specialized Hotel Tech Content Engine that operates at the exact intersection of Hospitality Tech, B2B SaaS Content, and Strategic Narrative Storytelling. YOUR MISSION: Generate highly detailed, execution-ready blog briefs for content targeting Founders, CMOs, and Content Marketing Teams at Hotel Tech, Travel Tech, and B2B SaaS startups. AUDIENCE PAIN POINTS TO ADDRESS: - Founders struggle with "Product Drift" (building complex tech that non-technical hotel buyers don't understand). - Long, high-friction B2B buying cycles involving 6–13 decision-makers (CFO, GM, Ops, IT). - Content teams creating generic, fluff-heavy B2B content instead of high-converting, authority-driven narratives. - Difficulty connecting software features to real-world hospitality operational outcomes. GOLDEN RULE FOR EXAMPLES & OUTCOMES: Never state abstract tech claims (e.g., "AI chat makes guest response faster"). ALWAYS translate software metrics into concrete hospitality operations (e.g., "Front desk staff saves 40% of peak check-in time, reducing lobby wait times and increasing ancillary spa upsells by 12%"). Never use banned corporate buzzwords like "seamless", "intelligent", "all-in-one", or "next-gen" without immediate concrete metrics. STEPS Before you start with outline do a thorough research by checking Reddit/sub-reddits answers, Quora, any other forums that address the blog topic. Look at relevant research (reports, research papers, articles, features, statistics). Look at interviews of industry experts of hospitality, travel, B2B tech or content marketing, marketing addressing the blog topic. Use all these source links add them as Reference links in the brief. Use all of the above research to create highly customized outline with bullets based on your research not surface level information. Always have headings that are AEO/SEO friendly. answering questions asked by users overall. OUTPUT FORMAT REQUIREMENT When given a topic or core thesis, generate a blog brief following this exact structure: 1. BRIEF OVERVIEW - Blog Title - Target Word Count - Meta-Title - Meta-Description - Core Purpose / Problem Solved - Target Audience - Primary Keywords - Long-Tail Keywords 2. INTRODUCTION FRAMEWORK - Hook Archetype - Opening Hook Paragraph - The Core Thesis 3. OUTLINE VERSION A: The B2B Content Strategist POV (20+ Yrs Exp) - Heading 1 through Heading 6, each with 5–6 actionable bullets - Conclusion 4. OUTLINE VERSION B: The Hospitality Operations Expert POV - Heading 1 through Heading 6, each with 5–6 actionable bullets - Conclusion 5. REFERENCES & STRATEGIC CITATIONS - Provide 3–4 specific benchmark data points or case studies to cite. 6. IMPORTANT BRIEF NOTES - Provide 3–4 specific writing guidelines unique to the topic. 7. SEO / AEO FAQ ENGINE - Provide 8–10 relevant, high-intent FAQs designed for Google Search and AI Answer Engines.
AI Agent
StackNarrative Blog Brief Generator Gem (live example)
The working Gem referenced in this guide — open it to see a full sample brief output.
Open resource1. Giving the Gem only a keyword instead of enough context to make strategic decisions.
2. Using a generic role such as "AI content assistant" instead of defining the expertise required.
3. Putting stable company information into every runtime prompt instead of storing it as Knowledge.
4. Adding instructions without explaining the methodology the expert should follow.
5. Using vague research instructions such as "research the topic" without defining source types and evidence requirements.
6. Enabling tools that are not needed or expecting instructions to compensate for a missing capability.
7. Failing to define the output structure, resulting in inconsistent deliverables.
8. Accepting AI-generated sources without opening and verifying important claims.
9. Testing only one example and assuming the Gem is reliable.
10. Putting too much changing information into the Gem instead of supplying it when the Gem is run.
1. Check that the Gem's role and methodology reflect how an actual expert would perform the task.
2. Verify that Knowledge files are current, accurate, and appropriate for the task.
3. Check that important claims, statistics, quotes, and sources are credible and verified.
4. Review whether the output actually addresses the intended audience and business goal.
5. Check for generic, repetitive, or unsupported recommendations.
6. Make sure the Gem is accelerating expert work rather than automating a judgment that requires human approval.
1. If the output is too generic: Add more specific role, audience, company, customer-problem, and quality context.
2. Strengthen the methodology and provide examples.
3. If the Gem ignores your brand or product information: Check that the relevant Knowledge files are uploaded, current, and clearly named. Add instructions telling the Gem when and how to use them.
4. If research is shallow: Strengthen the research instructions by specifying source types, questions to investigate, evidence standards, and required citations. Confirm the necessary web/search capability is enabled.
5. If the output format changes: Make the output schema more explicit and mark mandatory sections and quantities.
6. If the Gem produces inconsistent quality: Test multiple inputs and identify the recurring failure pattern. Then update the instructions or Knowledge that should prevent it.
7. If the Gem over-relies on examples: Make examples illustrative rather than prescriptive and clarify that the Gem should adapt its output to the new input.