Sprint 56f: Human-readable file naming - Chapter_N_draft/review_a/b/c/final

steps/blog_draft_step.yml

@@ -0,0 +1,36 @@
+type: think
+max_tokens: 4000
+hint: |
+  BLOG POST DRAFT
+
+  ASSIGNMENT
+  Title: {item_title}
+  Brief: {item_brief}
+  Target reader: {audience}
+  Voice: {voice}
+  Word count target: {item_target_words} words
+  Keywords to work in naturally: {item_keywords}
+
+  Before writing, confirm:
+    - TOPIC and TARGET READER
+    - HOOK: the first sentence drops the reader into a real scenario or provocative question
+    - PROMISE: the one thing they walk away with
+    - KEY POINTS to cover (use the brief above)
+    - TONE and WORD COUNT TARGET
+    - CALL TO ACTION
+
+  Write the full blog post:
+    - # Title as H1 (make it specific and curiosity-driven, not generic)
+    - Optional subhead in italics
+    - Opening hook: first 2–3 sentences pull the reader in immediately
+    - Body: 3–5 sections with bold subheadings, short readable paragraphs
+    - At least one concrete example, number, or real scenario per section
+    - "Try This Week" or equivalent action section before the closing
+    - Memorable closing line that reinforces the promise
+
+  Tone rules (apply the voice above):
+    - Peer-to-peer. Write like a knowledgeable friend, not a corporate brochure.
+    - Use "you" and "your" — not "one" or "the reader."
+    - Short sentences preferred. No filler paragraphs.
+    - No listicles of 10+ items without grouping them into themes.
+    - Work the keywords in naturally — never stuff them.