# Research brief blueprint Human Guide

## What This Is For
When to Use Kicking off any market research or insights program. It gives the agent a clearer input/output frame for competitive research: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Research brief blueprint agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for research brief blueprint.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Research brief blueprint guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Kicking off any market research or insights program.
- Aligning stakeholders on objectives, hypotheses, timelines, and deliverables.
- Auditing vendor proposals or internal requests for completeness.
- **Business Question** – decisions to inform, stakeholders, success metrics.
- **Audience & Sample** – personas, geos, quotas, existing panels, exclusion criteria.
- **Methods & Sources** – qualitative, quantitative, desk, experimentation, telemetry.
- **Logistics** – budget, timeline, approvals, compliance considerations.
- **Deliverables** – format, fidelity, access model, follow-up cadence.
- Brief doc (Notion/Doc) with structured sections + prompts.
- Intake form or ticket template for repeating the process at scale.
- Executive summary format to socialize scope before kickoff.
- Capture "out of scope" explicitly to avoid scope creep.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Capture "out of scope" explicitly to avoid scope creep.

## Copy-And-Paste Prompt
```text
Use the Research brief blueprint human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `research-brief-blueprint`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Research Brief Blueprint Skill

## When to Use
- Kicking off any market research or insights program.
- Aligning stakeholders on objectives, hypotheses, timelines, and deliverables.
- Auditing vendor proposals or internal requests for completeness.

## Framework
1. **Business Question** – decisions to inform, stakeholders, success metrics.
2. **Audience & Sample** – personas, geos, quotas, existing panels, exclusion criteria.
3. **Methods & Sources** – qualitative, quantitative, desk, experimentation, telemetry.
4. **Logistics** – budget, timeline, approvals, compliance considerations.
5. **Deliverables** – format, fidelity, access model, follow-up cadence.

## Templates
- Brief doc (Notion/Doc) with structured sections + prompts.
- Intake form or ticket template for repeating the process at scale.
- Executive summary format to socialize scope before kickoff.

## Tips
- Capture "out of scope" explicitly to avoid scope creep.
- Tie every method to a decision owner to keep studies focused.
- Pair with `run-market-landscape-study` and `launch-quantitative-survey` to auto-populate briefs.

---