# Writing Direction Verification

## When to use this reference

- Reviewing document outlines, presentation flow, or content positioning
- Verifying targeted readers, narrative structures, and content tone
- Checking email copy, blog structures, or key presentation slide outlines
- Refining marketing copy or corporate positioning statements

## When not to use this reference

- Reviewing user personas or product feature ideas → Use `product-idea-grill.md`
- Verifying code models or API specifications → Use `technical-design-grill.md`
- Generating bulk blog paragraphs or editing spelling directly

## Question Priority

1. **Target Reader** — Who is the primary audience? What is their background?
2. **Core Message** — What is the single most important takeaway?
3. **Reader Value** — Why does the reader care about this? What is their payoff?
4. **Tone & Voice** — What is the emotional or professional tone of this piece?
5. **Narrative Structure** — How does the logical flow progress?
6. **Objections & Obvious Questions** — What objections will the reader raise?
7. **Call to Action (CTA)** — What should the reader do after reading?
8. **Smallest Next Action** — What outline section needs to be drafted first?

## Strong Question Patterns

- "Who is the primary reader? What background context or vocabulary do they already have?"
- "If the reader only remembers one sentence from this document, what should it be?"
- "What is the reader's immediate objection at page 2? How do we address it early?"
- "What do you want the reader to do next? (e.g., sign up, reply, schedule a call)"

## Weak Question Patterns

- "Is this writing good?"
- "Does this sound professional?"
- "Should we write more pages?"

## Recommended Option Rules

- **Reader Ambiguity**: Recommend `(Recommended) Readers who are interested in the topic but lack specific background technical knowledge` and include junior/senior options to build the option set.
- **Tone Ambiguity**: Recommend `(Recommended) A clear, objective tone using facts and data without jargon` and include informal/formal options to build the option set.
- **Structure Ambiguity**: Recommend `(Recommended) Problem → Core Solution → Supporting Evidence → Counter-objections → CTA` structure to build the option set.

## Handling Vague Answers

- "Everyone should read this" → Narrow down: "If only one person's opinion matters for this document's success, who is that person?"
- "I want it to sound smart and casual" → Force choice: "Let's stick to an 'objective expert tone using concrete data'. Shall we use this as our voice guideline?"
- "They just need to understand it" → Force Action: "After reading, what is the single next step they should take? Let's add a clear CTA."

## Stopping Conditions

In addition to common stopping conditions, ensure:
- The target reader's context/knowledge level is defined.
- The single core message is clear.
- Tone and voice guidelines are established.
- Logical outline structure is mapped.
- The Call to Action (CTA) is explicit.

## Final Synthesis Required Items

Add the following to the common final synthesis format:
- Refined Reader Profile
- Core Message Statement
- Outline Structure Map
- Tone & Voice Guidelines
- Core CTA Definition
