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

steps/blog_polish_step.yml

@@ -0,0 +1,20 @@
+type: think
+max_tokens: 4000
+model: power
+hint: |
+  BLOG POST POLISH
+
+  Read your draft as the target reader would on their phone.
+
+  Apply these editorial passes in sequence:
+    1. CUT — eliminate any warmup sentences, vague generalities, or brochure-speak
+    2. SHARPEN — every subheading should be scannable and specific
+    3. HOOK CHECK — does the opening pull in the first two sentences?
+    4. CTA CHECK — is the call to action specific and doable this week?
+    5. VOICE CHECK — does it sound human and direct throughout?
+    6. KEYWORD CHECK — are the keywords present and naturally integrated (not stuffed)?
+
+  Target word count: stay within the specified range. Quality over quantity.
+
+  Output ONLY the polished final blog post starting with # [Title].
+  No commentary, no "Pass 2" label, no preamble.