Humanity's Last Prompt Engineer
Craft effective prompts using proven techniques from Forward Future's prompt engineering guide. Diagnose weak prompts, apply the right technique, and deliver concrete rewrites.
Source: Based on "Humanity's Last Prompt Engineering Guide" by Matthew Berman & Nick Wentz (Forward Future).
https://www.forwardfuture.ai/p/humanity-s-last-prompt-engineering-guide
Core Workflow
Follow these five steps for every prompt request:
1. Receive the prompt (or a description of what the user needs)
2. Diagnose: Identify what's missing (role, context, format, task clarity)
3. Select technique(s): Determine which of the 11 techniques applies best
4. Rewrite: Produce an improved prompt
5. Explain: Briefly describe why the changes work
Step 1: Diagnose the Prompt
Evaluate against these 6 diagnostic questions:
| # |
Question |
If Missing |
| 1 |
Is the task clearly defined? |
Add a specific action verb |
| 2 |
Is there a role/persona? |
Add "You are a [expert]..." |
| 3 |
Is input/context complete? |
Add background data or scenario |
| 4 |
Is output format specified? |
Add format constraint (bullets, JSON, table) |
| 5 |
Is reasoning requested (if needed)? |
Add "think step by step" or "explain logic" |
| 6 |
Is it broken into steps (if complex)? |
Decompose into subtasks |
Step 2: Select the Right Technique
| Technique |
When to Apply |
Complexity |
| Zero-Shot |
Simple, obvious tasks requiring no examples |
Low |
| Few-Shot |
Need specific structure, tone, or output format |
Low |
| System Prompt |
Control persistent behavior or format rules |
Low |
| Role Prompt |
Need specific domain expertise or persona |
Low |
| Contextual |
Task requires background data or domain knowledge |
Medium |
| Step-Back |
Complex reasoning benefits from broader perspective first |
Medium |
| Chain-of-Thought |
Math, logic, planning, or multi-step reasoning |
Medium |
| Self-Consistency |
High-stakes or ambiguous tasks needing multiple reasoning paths |
High |
| Tree of Thoughts |
Brainstorming, exploration of multiple valid solution paths |
High |
| ReAct |
Tasks requiring tool use (search, code execution, APIs) |
High |
| APE |
Optimizing prompt performance at scale with automated testing |
High |
For detailed examples, tips by experience level, and advanced usage of each technique, see references/techniques-detailed.md.
Step 3: Apply the Prompt Formula
Every strong prompt contains four components:
- Role: Define expertise — "You are a [specific expert]..."
- Task: Use a clear action verb — Summarize, List, Write, Analyze, Compare, Generate
- Input: Provide what to work with — text, data, scenario, constraints
- Format: Specify response structure — bullets, JSON, table, word count, tone
Example transformation:
Weak: "Help me with marketing"
Strong: "You are a B2B SaaS copywriter. Write 3 LinkedIn post variations
promoting our new analytics feature. Each post should be under
150 words, use a professional but approachable tone, and end
with a clear CTA."
Step 4: Fix Common Problems
| Problem |
Diagnosis |
Fix |
| Too vague |
No specifics or constraints |
Add specifics: "3 bullet points focusing on X" |
| Wrong audience |
No target reader defined |
Add target: "for a busy executive" |
| Missing role |
No expertise context |
Add persona: "You are a brand copywriter" |
| Unstructured output |
No format specified |
Specify: "as a numbered list with explanations" |
| Shallow reasoning |
No thinking requested |
Add: "explain your logic" or "think step by step" |
| Inconsistent results |
Single inference path |
Apply Self-Consistency: generate 3 answers, pick majority |
Step 5: Deliver the Output
Structure every response using this format:
## Analysis
[What's working in the original prompt, what's missing or weak]
## Technique Applied
[Which technique(s) were selected and why they fit this case]
## Improved Prompt
[The complete rewritten prompt, ready to copy-paste]
## Why This Works
[1-2 sentences explaining the key improvements]
Temperature Guide
Match temperature to the task type:
| Range |
Best For |
Examples |
| 0-0.3 |
Factual, precise, deterministic |
Summaries, data analysis, extraction |
| 0.4-0.6 |
Balanced (default) |
General tasks, explanations |
| 0.7-1.0 |
Creative, exploratory |
Brainstorming, writing, ideation |
Operational Rules
- Diagnose before rewriting — never skip the analysis step
- Explain which technique is being applied and why
- Provide a concrete, copy-pasteable improved prompt in every response
- Never just list tips without delivering a rewritten prompt
- Never over-complicate simple prompts — match complexity to the task
- Offer 2-3 variations when multiple techniques fit equally well
- Score the improved prompt against the diagnostic questions to verify quality
Reference Files
For detailed guidance and tools, consult:
references/techniques-detailed.md — Extended examples, tips by experience level, and advanced usage for all 11 techniquesreferences/role-templates.md — Ready-to-use role-based prompt templates for common business scenarios (operations, marketing, sales, HR)references/scorecard.md — Prompt quality scorecard (1-35 rating) and refinement worksheet for systematic prompt evaluation
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: humanitys-last-prompt-engineer3description: This skill should be used when the user asks to "write a prompt", "improve my prompt", "fix this prompt", "optimize a prompt", "learn prompting techniques", "get prompt templates", or mentions prompt engineering, prompt quality, or prompt rewriting. Applies 11 foundational techniques from Forward Future's guide. Use when this capability is needed.4---56# Humanity's Last Prompt Engineer78Craft effective prompts using proven techniques from Forward Future's prompt engineering guide. Diagnose weak prompts, apply the right technique, and deliver concrete rewrites.910> **Source**: Based on "Humanity's Last Prompt Engineering Guide" by Matthew Berman & Nick Wentz (Forward Future).11> <https://www.forwardfuture.ai/p/humanity-s-last-prompt-engineering-guide>1213---1415## Core Workflow1617Follow these five steps for every prompt request:1819```text201. Receive the prompt (or a description of what the user needs)212. Diagnose: Identify what's missing (role, context, format, task clarity)223. Select technique(s): Determine which of the 11 techniques applies best234. Rewrite: Produce an improved prompt245. Explain: Briefly describe why the changes work25```2627### Step 1: Diagnose the Prompt2829Evaluate against these 6 diagnostic questions:3031| # | Question | If Missing |32|---|----------|------------|33| 1 | Is the task clearly defined? | Add a specific action verb |34| 2 | Is there a role/persona? | Add "You are a [expert]..." |35| 3 | Is input/context complete? | Add background data or scenario |36| 4 | Is output format specified? | Add format constraint (bullets, JSON, table) |37| 5 | Is reasoning requested (if needed)? | Add "think step by step" or "explain logic" |38| 6 | Is it broken into steps (if complex)? | Decompose into subtasks |3940### Step 2: Select the Right Technique4142| Technique | When to Apply | Complexity |43|-----------|--------------|------------|44| **Zero-Shot** | Simple, obvious tasks requiring no examples | Low |45| **Few-Shot** | Need specific structure, tone, or output format | Low |46| **System Prompt** | Control persistent behavior or format rules | Low |47| **Role Prompt** | Need specific domain expertise or persona | Low |48| **Contextual** | Task requires background data or domain knowledge | Medium |49| **Step-Back** | Complex reasoning benefits from broader perspective first | Medium |50| **Chain-of-Thought** | Math, logic, planning, or multi-step reasoning | Medium |51| **Self-Consistency** | High-stakes or ambiguous tasks needing multiple reasoning paths | High |52| **Tree of Thoughts** | Brainstorming, exploration of multiple valid solution paths | High |53| **ReAct** | Tasks requiring tool use (search, code execution, APIs) | High |54| **APE** | Optimizing prompt performance at scale with automated testing | High |5556For detailed examples, tips by experience level, and advanced usage of each technique, see **`references/techniques-detailed.md`**.5758### Step 3: Apply the Prompt Formula5960Every strong prompt contains four components:6162- **Role**: Define expertise — "You are a [specific expert]..."63- **Task**: Use a clear action verb — Summarize, List, Write, Analyze, Compare, Generate64- **Input**: Provide what to work with — text, data, scenario, constraints65- **Format**: Specify response structure — bullets, JSON, table, word count, tone6667**Example transformation:**6869```text70Weak: "Help me with marketing"71Strong: "You are a B2B SaaS copywriter. Write 3 LinkedIn post variations72 promoting our new analytics feature. Each post should be under73 150 words, use a professional but approachable tone, and end74 with a clear CTA."75```7677### Step 4: Fix Common Problems7879| Problem | Diagnosis | Fix |80|---------|-----------|-----|81| Too vague | No specifics or constraints | Add specifics: "3 bullet points focusing on X" |82| Wrong audience | No target reader defined | Add target: "for a busy executive" |83| Missing role | No expertise context | Add persona: "You are a brand copywriter" |84| Unstructured output | No format specified | Specify: "as a numbered list with explanations" |85| Shallow reasoning | No thinking requested | Add: "explain your logic" or "think step by step" |86| Inconsistent results | Single inference path | Apply Self-Consistency: generate 3 answers, pick majority |8788### Step 5: Deliver the Output8990Structure every response using this format:9192```markdown93## Analysis94[What's working in the original prompt, what's missing or weak]9596## Technique Applied97[Which technique(s) were selected and why they fit this case]9899## Improved Prompt100[The complete rewritten prompt, ready to copy-paste]101102## Why This Works103[1-2 sentences explaining the key improvements]104```105106---107108## Temperature Guide109110Match temperature to the task type:111112| Range | Best For | Examples |113|-------|----------|---------|114| **0-0.3** | Factual, precise, deterministic | Summaries, data analysis, extraction |115| **0.4-0.6** | Balanced (default) | General tasks, explanations |116| **0.7-1.0** | Creative, exploratory | Brainstorming, writing, ideation |117118---119120## Operational Rules121122- Diagnose before rewriting — never skip the analysis step123- Explain which technique is being applied and why124- Provide a concrete, copy-pasteable improved prompt in every response125- Never just list tips without delivering a rewritten prompt126- Never over-complicate simple prompts — match complexity to the task127- Offer 2-3 variations when multiple techniques fit equally well128- Score the improved prompt against the diagnostic questions to verify quality129130---131132## Reference Files133134For detailed guidance and tools, consult:135136- **`references/techniques-detailed.md`** — Extended examples, tips by experience level, and advanced usage for all 11 techniques137- **`references/role-templates.md`** — Ready-to-use role-based prompt templates for common business scenarios (operations, marketing, sales, HR)138- **`references/scorecard.md`** — Prompt quality scorecard (1-35 rating) and refinement worksheet for systematic prompt evaluation139140---141> Converted and distributed by [TomeVault](https://tomevault.io/claim/back1ply) — claim your Tome and manage your conversions.142<!-- tomevault:4.0:skill_md:2026-04-15 -->
tomevault-io