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

templates/blog_write.yml

@@ -3,6 +3,13 @@ description: "Write a standalone blog post — draft, polish, deliver."
 debug: true
 system: agent_prompt
 
+requires:
+  - item_title
+  - item_brief
+  - voice
+  - audience
+  - item_target_words
+
 skills:
   - guides/BlogWritingGuide.md
 
@@ -21,55 +28,10 @@ sections:
   - instructions
 
 steps:
-  - type: think
-    max_tokens: 4000
-    hint: |
-      Your task message contains the blog content brief. Follow it exactly.
-
-      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
-        - 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:
-        - 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.
-
-  - type: think
-    max_tokens: 4000
-    model: power
-    hint: |
-      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?
-
-      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.
-
+  - include: steps/blog_draft_step.yml
+  - include: steps/blog_polish_step.yml
   - type: document
     filename: "{{task_name_slug}}"
-
   - type: close
     rag_update: true