diff --git a/templates/ai_article_write.yml b/templates/ai_article_write.yml index a9f51fd..a80b27b 100644 --- a/templates/ai_article_write.yml +++ b/templates/ai_article_write.yml @@ -10,7 +10,6 @@ agent_prompt: sections: - agent - project - - history - rag - deliverables - message diff --git a/templates/blog_write.yml b/templates/blog_write.yml index 75eecb7..64c00ab 100644 --- a/templates/blog_write.yml +++ b/templates/blog_write.yml @@ -10,7 +10,6 @@ agent_prompt: sections: - agent - project - - history - rag - deliverables - message diff --git a/templates/book_chapter.yml b/templates/book_chapter.yml index 08a1f4e..f1ba9b0 100644 --- a/templates/book_chapter.yml +++ b/templates/book_chapter.yml @@ -17,7 +17,6 @@ agent_prompt: sections: - agent - project - - history - rag - deliverables - message @@ -27,7 +26,7 @@ sections: steps: - type: think hint: | - PASS 0 — BIBLE & CONTINUITY CHECK (do this FIRST, before drafting) + PASS 0 — BIBLE & CONTINUITY PLAN (produce a PLAN only — do NOT write chapter prose yet) GENRE: {genre_name} | AUDIENCE: {genre_audience} PROSE STYLE GUIDE: {prose_style} @@ -57,44 +56,53 @@ steps: Label them: "PREVIOUS CHAPTER ENDED WITH: ..." Your new chapter MUST pick up from this exact moment. - STEP 4 — PLAN YOUR CHAPTER: - State your plan: + STEP 4 — CHAPTER PLAN: + State your plan — do NOT write prose yet: - CHAPTER: Exact chapter number and title (from the task message) - POV CHARACTER: Whose perspective are we in? - - FIRST LINE: How does this chapter begin, continuing from the previous ending? + - FIRST LINE: The exact opening sentence, continuing from the previous ending - EMOTIONAL ARC: What does the protagonist feel at start vs end? - CHAPTER GOAL: What plot event MUST happen here? - - CLOSING HOOK: Exact last image or line that makes readers continue? + - KEY BEATS: 3–5 numbered scene beats that will form the chapter + - CLOSING HOOK: Exact last image or line that makes readers continue - Now write the full draft chapter following the prose style guide above. - Be consistent with ALL character names and world rules from the bible. + Stop here. Output ONLY the plan above. The full chapter will be written next. - type: think model: power hint: | - PASS 2 — DEEPEN & SHARPEN + PASS 1 — WRITE THE FULL CHAPTER - Read your draft critically through an editor's eyes: - - Does the first line continue naturally from the previous chapter's ending? - - Does the opening hook land in the first two lines? - - Are ALL character names consistent with the bible/outline? - - Is every dialogue exchange tight and voice-distinct between characters? - - Are there any "telling" moments that should be "showing"? - - Does every scene beat move the story forward OR reveal character? - - Is the closing hook specific and compelling, not generic? - - Does the prose match the genre style guide above? - - Is the chapter at the target length? ({chapter_target_words} words — write the full chapter) + Using the plan from your previous step, write the complete chapter now. - Rewrite the COMPLETE final chapter incorporating all improvements. - Output ONLY the polished chapter text — no commentary, no "Pass 2" headings. - Start directly with the chapter title and opening line. + Requirements: + - Start with the FIRST LINE you planned — make it continue naturally from the previous chapter + - Follow the KEY BEATS in order, but write with full scene depth — don't skip + - All character names must be consistent with the bible/outline + - Every dialogue exchange must be tight and voice-distinct + - Show, don't tell — externalize emotion through action, detail, and dialogue + - Every scene beat moves the story forward OR reveals character (no filler) + - End with the CLOSING HOOK you planned + - Match the prose style guide: {prose_style} + - Target length: {chapter_target_words} words — write the full chapter, not a summary + + Output ONLY the polished chapter text. + Start directly with the chapter title (e.g., "Chapter N: [Title]") and opening line. + No commentary, no plan headers, no "Pass 1" label. - type: document filename: "chapter-{chapter_ref}" - type: package hint: | - The chapter has been written and committed. Now spawn the three independent editorial reviewers + The chapter has been written and committed. + + CRITICAL — include the `chapter_text` field: + Copy the COMPLETE chapter text you just wrote into the `chapter_text` field. + Reviewers have NO other way to access the chapter content. + Do NOT summarize or truncate it — include every word of the final chapter. + + Now spawn the three independent editorial reviewers and the roundtable debate. Use the exact task_names shown — the roundtable depends_on all three. schema: chapter_text: string diff --git a/templates/chapter_polish.yml b/templates/chapter_polish.yml index 5cce877..4a1f31c 100644 --- a/templates/chapter_polish.yml +++ b/templates/chapter_polish.yml @@ -8,7 +8,6 @@ sections: - agent - project - rag - - deliverables - message - instructions diff --git a/templates/chapter_roundtable.yml b/templates/chapter_roundtable.yml index 42e1793..3dd9269 100644 --- a/templates/chapter_roundtable.yml +++ b/templates/chapter_roundtable.yml @@ -51,13 +51,21 @@ steps: - Continuity with prior chapters and world rules If the group has reached sufficient consensus for the polish step, - end your response with: CONSENSUS REACHED + end your response with this EXACT block — no variations, no paraphrasing: + + CONSENSUS REACHED + CRITIQUE: [One concise paragraph summarizing the full editorial consensus] + KEY CHANGES: + - [Specific change 1] + - [Specific change 2] + - [Specific change 3 if needed] + VERDICT: [PASS / REVISE / REWRITE] - type: package schema: consensus_critique: string chapter_verdict: string - key_changes: list + key_changes: string spawn: - task_type: chapter_polish task_name: "Polish: {chapter_ref}" diff --git a/templates/recipe_develop.yml b/templates/recipe_develop.yml index 42ce16c..0c8d564 100644 --- a/templates/recipe_develop.yml +++ b/templates/recipe_develop.yml @@ -10,7 +10,6 @@ agent_prompt: sections: - agent - project - - history - rag - deliverables - message diff --git a/templates/short_story.yml b/templates/short_story.yml index ad2b8f3..bd30a9c 100644 --- a/templates/short_story.yml +++ b/templates/short_story.yml @@ -10,9 +10,7 @@ agent_prompt: sections: - agent - project - - history - rag - - deliverables - message - rejection_feedback - instructions @@ -20,17 +18,18 @@ sections: steps: - type: think hint: | - PASS 0 — STORY PLAN (do this before drafting) + PASS 0 — STORY PLAN (produce a PLAN only — do NOT write prose yet) GENRE: {genre_name} | AUDIENCE: {genre_audience} PROSE STYLE: {prose_style} - (If any of the above are empty, infer genre, audience, and prose style from the task description and project goal.) + NOTE: If any field above shows as a literal placeholder (e.g. {genre_name}), it was not + provided — infer genre, audience, and prose style from the project description and task message. TARGET LENGTH: 3,000–15,000 words (short story to novelette) - Before writing, plan the story: + Before writing, plan the story — output ONLY this plan block, no prose: TITLE: [Working title] - HOOK: [The first sentence or image that pulls the reader in] + HOOK: [The exact first sentence or image that pulls the reader in] PREMISE: [One sentence — the "what if" or core situation] PROTAGONIST: [Name, age, voice, fatal flaw, want vs need] ANTAGONIST / OBSTACLE: [What opposes the protagonist — person, force, or internal] @@ -41,32 +40,25 @@ steps: EMOTIONAL CORE: [What does this story make the reader FEEL?] POINT OF VIEW: [1st / 3rd limited / 3rd omniscient] TENSE: [Past / present] + KEY SCENES: [3–5 numbered scene beats] - Now write the complete first draft. - Follow the prose style guide. Stay in chosen POV throughout. - Show — don't tell. Use dialogue. Use sensory detail. - End with purpose: the final line should feel earned and resonant. + Stop here. The full story will be written in the next step. - type: think model: power hint: | - PASS 2 — DEEPEN & SHARPEN + PASS 1 — WRITE THE COMPLETE STORY - Read your draft critically through an editor's eyes: + Using the plan from your previous step, write the full story now. - - Does the opening line hook the reader immediately? - - Is every scene earning its place in the story? - - Are there any "telling" passages that should be "showing"? - - Is the protagonist's want vs need clearly felt (not stated) by the end? - - Is the dialogue tight, voice-distinct, and advancing the story? - - Does the pacing serve the emotional arc? (Slow the key moments. Cut the connective tissue.) - - Is the final line earned and resonant — not a summary? - - Is the prose consistent with the style guide? - - Is the total length appropriate for the story being told? + Follow the prose style from the plan. Stay in chosen POV throughout. + Show — don't tell. Use dialogue. Use sensory detail. + Start with the HOOK from your plan as the literal first sentence. + End with the RESOLUTION — the final line must feel earned and resonant. + Target: reach the word count appropriate for the story (3,000–15,000 words). - Rewrite the COMPLETE final story incorporating all improvements. - Output ONLY the polished story starting with the title as # [Title]. - No commentary, no "Pass 2" label, no preamble. + Output the complete story starting with # [Title]. + No commentary, no "Pass 1" label, no preamble. - type: document filename: "{{task_name_slug}}"