pae/crimson_leaf_publishing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: remove Unicode chars from template

Browse Source
This commit is contained in:
Nova_2761
2026-04-09 23:03:31 +00:00
parent a56394a6d3
commit 18c9d13e69
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
templates/book_editorial.yml
View File

@@ -1,5 +1,5 @@
name: book_editorial
description: "Editorial boardroom — agents review the full manuscript, debate quality, and produce written editorial notes."
description: "Editorial boardroom -- agents review the full manuscript, debate quality, and produce written editorial notes."
debug: true
rag_exclude: [business_plan, charter]
system: agent_prompt
@@ -31,19 +31,19 @@ steps:
hint: |
You are {agent.name}. This is the editorial review boardroom for the manuscript.
TASK: Review all completed chapters (look in PROJECT DELIVERABLES — files named
TASK: Review all completed chapters (look in PROJECT DELIVERABLES -- files named
"final-chapter-*.md"). Read them carefully as a professional editor would.
For each round, discuss:
1. CONTINUITY — Does each chapter open by continuing the previous chapter's cliffhanger?
1. CONTINUITY -- Does each chapter open by continuing the previous chapter's cliffhanger?
Quote specific chapter-to-chapter handoffs that work well or need repair.
2. CHARACTER VOICE — Are POV voices distinct across chapters?
2. CHARACTER VOICE -- Are POV voices distinct across chapters?
Call out any chapters where the voice felt off.
3. WATTPAD HOOKS — Do chapters open with a strong hook that stops a teen scrolling?
3. WATTPAD HOOKS -- Do chapters open with a strong hook that stops a teen scrolling?
Which openings are weakest and need a rewrite?
4. PACING — Any chapters that drag or that rush past important emotional beats?
5. CLIFFHANGERS — Which chapter endings are strong? Which are weak or generic?
6. SERIES HOOK — Does the final chapter end in a way that makes readers desperate for the next book?
4. PACING -- Any chapters that drag or that rush past important emotional beats?
5. CLIFFHANGERS -- Which chapter endings are strong? Which are weak or generic?
6. SERIES HOOK -- Does the final chapter end in a way that makes readers desperate for the next book?
Speak in your own professional voice. Debate. Challenge each other.
When the editorial team has reached consensus on the manuscript's strengths and
@@ -62,7 +62,7 @@ steps:
(1-2 paragraphs on the manuscript's readiness for publication)
**STRENGTHS** (specific, with chapter references)
**REVISION PRIORITIES** (ranked 1–5, most critical first)
**REVISION PRIORITIES** (ranked 1-5, most critical first)
- For each: what the issue is, which chapters are affected, suggested fix
**CONTINUITY CHECK** (chapter-by-chapter handoff assessment)
**CHARACTER VOICE CONSISTENCY** (POV analysis across chapters)
@@ -75,7 +75,7 @@ steps:
- type: package
packet_type: IntakeResponse
hint: |
You are the Project Manager. The editorial report above lists REVISION PRIORITIES ranked 1–5.
You are the Project Manager. The editorial report above lists REVISION PRIORITIES ranked 1-5.
Convert each revision priority into a sequential create_task action for Iris.
After all revision tasks, add ONE final task to compile the project index.
@@ -85,7 +85,7 @@ steps:
- agent_name: "Iris"
- task_type: "book_chapter"
- description: Include the specific issue, affected chapters, and suggested fix from the editorial report.
Start with: "EDITORIAL REVISION — [Priority N]: [issue]. Affected chapters: [chapters]. Fix: [fix]."
Start with: "EDITORIAL REVISION -- [Priority N]: [issue]. Affected chapters: [chapters]. Fix: [fix]."
- depends_on: the exact task_name of the PREVIOUS revision task (empty string for the first revision)
Final task (always add this LAST):