Resource
Bug Triage Assistant
Convert scattered bug notes, Slack messages, or user complaints into structured engineering tasks with reproduction steps, severity, and root cause hypothesis.
SEO Content Brief Assistant
Build a structured content brief from a keyword or topic before drafting — so writers start with intent, not assumptions.
Overview
Content that ranks is aligned to search intent, not internal assumptions about what's important. This workflow turns a keyword or topic into a structured brief: intent classification, content angle, heading structure, and coverage gaps relative to what already ranks. Writers get clear direction; the brief encodes SEO logic before a word is written.
How to use this resource
-
Provide the keyword and context
Give the primary keyword and, optionally, who the target reader is and what action you want them to take.
-
Add SERP context if available
Optionally paste the titles of current top-ranking pages. The model uses this to identify gaps in existing coverage.
-
Review intent classification
The intent classification drives everything else in the brief. If it's wrong, the angle and structure will be wrong too.
-
Hand the brief to the writer
The brief replaces the conversation between SEO and writer — it should answer their questions before they ask.
Why This Works
- Classifying intent before structure prevents the brief from being built around internal assumptions
- Separating 'must-cover' from 'avoid' gives writers a clear scope — ambiguity in briefs produces off-target drafts
- Requiring a specific H1 instead of a generic one surfaces the key framing decision early
- Keeping the brief production separate from drafting means intent decisions don't get overridden mid-draft
Best for
- Content teams where the writer is not the same person doing keyword research
- Topics where intent is ambiguous or mixed across the SERP
- Producing consistent brief quality across multiple contributors
- Planning content before publishing, not revising after
Not for
- Generating the actual article content — this produces a brief, not a draft
- Brand-specific or highly proprietary topic areas with no public search signal
- Programmatic content generation at scale
Use cases
- Briefing a writer before they start drafting a new article
- Evaluating whether an existing page is structured to match its target intent
- Generating multiple brief variants to compare content angles before committing
- Aligning content calendars around specific intent types
FAQ
How does this brief classify search intent, and why does that step come first?
The system prompt forces intent into one of four labels — Informational, Navigational, Commercial, or Transactional — plus a line on what the searcher is trying to accomplish. That classification sits at the top on purpose: the Recommended Content Angle, H2 structure, and Must-Cover topics all derive from it, so a mislabelled intent cascades into a wrong brief. Verify the label before you trust anything below it.
Which specific sections does the generated brief contain, and in what order?
It outputs eight fixed markdown sections in sequence: Search Intent, Recommended Content Angle, Target Audience, Suggested H1, Suggested H2 Structure, Must-Cover Topics, Avoid, and Suggested Word Count Range. Each H2 in that structure is meant to map to a distinct sub-question the searcher has, so keep the sequence intact when you hand the brief to a writer.
Can I paste competitor titles to get coverage gaps, and where do I add them?
Add them to the prompt as the top-ranking pages' titles — the brief reasons only over the competitor titles you supply, then routes uncovered angles into Must-Cover Topics and shapes a Recommended Content Angle that differs from generic coverage. It never crawls live SERPs or confirms rankings, so the gaps are only as fresh as the titles you feed it wherever you run the prompt.
Why does the brief refuse generic H1s and fixed word-count rules?
The template bans placeholder titles like 'Everything You Need to Know About X' and demands a specific, intent-matched H1, because that framing decision is the one it surfaces early. The Suggested Word Count Range is likewise tied to the depth the topic needs, not a blanket rule. Both stay recommendations you edit before drafting in ChatGPT, Claude, or Gemini.
More resources from System Prompt Generator
Resource
Code Review Assistant
Turn AI into a structured pull request reviewer that catches risky changes, flags maintainability issues, and suggests missing test coverage.
Resource
Customer Support Agent
Configure AI to answer support questions within your actual policy boundaries — not generic best-guess answers.
Resources that pair well
Resource
Product Manager Role Prompt
A complete 'act as a product manager' role prompt — the perspective, responsibilities, and decision criteria a real PM brings, not just the job title.
Resource
Agent Task Template
A reusable AI agent task template with variables for objective, context, available tools, constraints, success criteria, failure handling, and output format.
Resource
Agent Instruction Prompt Formatter
Formats fuzzy agent instructions into a structured prompt with objective, available tools, constraints, success criteria, and failure handling.
Related tools
Tool
System Prompt Generator
Build structured system prompts from role, tone, constraints, and model target.
Workflows that use this resource
Workflow
AI Content Strategy Workflow
Decide what to publish and why before you write a word — set the business goals and audience, map needs to topics, brief the priority pieces, then turn it into a content plan you publish against.