Green Hat AI Blue Hat Writing Playbook

Internal Green Hat Tool

AI Blue Hat: control, not autopilot.

AI Blue Hat is Green Hat's control layer for writing. It defines constraints, checks quality, and enforces guidelines so AI supports strategy instead of diluting it.

What This Is

A practical writing operator for project work. You use it before, during, and after each draft to keep content specific, human, and verifiable.

How To Use It

Load context in VP Content Engine.
Write a human first draft from real project inputs.
Run Blue Hat phases 1 to 4 in order.
Run Slop Bin checker on each pass and clean obvious slop.
Capture Retro Notes and save high-performing prompts for next time.

Step 1, Prime

Use VP Content Engine inputs first: value pillars, proof points, and source notes.

Step 2, Draft

Human writes the messy first draft with a real POV and concrete examples.

Step 3, Edit

Run AI Blue Hat phases 1 to 4. Ask questions, not rewrites.

Step 4, Improve System

Update Slop Bin and save any high-performing prompts to Prompt Library.

Golden Rule (AI Blue Hat)

Never ask AI to rewrite your text. Ask it to evaluate against rubric criteria and ask probing questions that force a stronger rewrite by the human author.

Centaur vs Default AI

VP Content Engine

Use this as the pre-writing layer for project work. It keeps copy tied to strategy, proof, and activation before drafting starts.

1) Messaging + CVP Core

Distill to 4-6 value pillars before drafting.
Capture benefit statements, proof points, and use cases.
Treat framework output as the central writing brain.

2) Harness Guardrails

Tell AI what this project needs and what we can deliver.
Explicitly forbid invention and unsupported claims.
Require source checks and missing-evidence flags.

3) Context Reuse

Use Five Pillars and readiness logic as context headers.
Align copy to stage, buying party, and project signal.
Keep strategy-to-content handoff explicit, not implied.

4) Activation From Day One

Decide format/channel fit while shaping message.
Do not park activation until after writing assets.
Frame content as ecosystem, not isolated artifacts.

Practical Run (GH Internal)

Run one complete cycle on Green Hat itself so the team can practice the method before applying it to project delivery.

Step 1

Hero Thesis

Choose one Green Hat thesis and state it in one sentence in plain language.

Step 2

Value Pillars

Extract 4-6 pillars with proof points and risks. This becomes your prompt context block.

Step 3

Activation Map

Map outputs to channels early: POV, social sequence, webinar narrative, and outreach copy.

Prompt: VP Content Engine Stress Test

Act as a skeptical B2B buying committee.
Context: This draft is for Green Hat's internal perspective piece.
Use only the value pillars and proof points provided. Do not invent facts.
Tasks:
1) Identify where the argument is generic or unsupported.
2) Flag where activation logic is missing (format, channel, audience stage).
3) Ask 5 probing questions that force stronger specificity.
Do not rewrite the draft.

4-Phase AI Blue Hat Workflow

Use these phases in order. After each phase, rewrite manually. Do not move to the next phase until changes are made.

Phase 1, Ideation and Angle Check

Ask AI what boring conclusion the draft currently leads to, and what insider angle is missing.

Phase 2, Structure and Flow

Ask where energy sags, where transitions fail, and where intro or ending falls into summary habits.

Phase 3, Voice and Anti-Slop

Use Slop Bin findings to remove generic language and push for concrete lived details.

Phase 4, Fact Check and Clarity

Extract claims for manual verification and flag lines over 25 words that are hard to parse.

Operator Loop

Run Slop Bin Draft Checker on current version.
Pick one Prompt Library template for the next phase.
Run the phase, get questions, rewrite manually.
Repeat until Phase 4 is complete.

Anti-Slop Lab

Slop Bin

Click to strike

Draft Checker

Run this before every phase. Fix obvious slop first, then use AI for higher-value critique.

Retro Notes + Prompt Library

Retro Notes Capture

After each piece, capture what worked, what failed, and what to avoid next time. This keeps the Blue Hat system improving over time.