Files
crimson_leaf_publishing/templates/chapter_review.yml
David Baity ff38fff631 refactor: move all project folders into projects/ subdirectory
This change reorganizes the repository structure to keep the root directory
clean. All 15 project folders are now nested under projects/, alongside
infrastructure directories (agents/, templates/, deliverables/, rag/, skills/).

This allows the repository to grow without polluting the core service directories.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-12 11:09:34 -04:00

64 lines
1.5 KiB
YAML

name: chapter_review
description: >
Independent chapter review. Agent reads the chapter and produces a structured
critique in their editorial domain.
debug: true
model: power
system: agent_prompt
skills:
- guides/YAFictionGuide.md
- guides/RomanceFictionGuide.md
- guides/SciFiFictionGuide.md
agent_prompt:
- system.md
sections:
- project
- rag
- skills
- message
- instructions
steps:
- type: think
max_tokens: 4000
hint: |
TARGET AUDIENCE: {genre_audience}
GENRE: {genre_name}
CHAPTER: {chapter_ref}
---
CHAPTER TEXT:
{chapter_text}
---
Write a detailed editorial review from your perspective.
Be specific — cite line numbers or quote passages where relevant.
Structure your review as:
1. STRENGTHS (what is working)
2. CONCERNS (what needs attention, in priority order)
3. VERDICT (pass / revise / rewrite — and why)
- type: document
filename: "review-{chapter_ref}-{agent_slug}"
- type: close
rag_update: false
adjudication:
enabled: true
pass_threshold: 60
deliverable_type: editorial_review
criteria:
specificity:
weight: 40
description: "Review cites specific passages, scenes, or structural elements — not vague general commentary"
actionability:
weight: 35
description: "Each concern includes a concrete, implementable suggestion for improvement"
coverage:
weight: 25
description: "Review addresses both strengths and concerns, ending with a clear VERDICT (pass/revise/rewrite)"