87c01864dc
- book_chapter: Remove PASS 2+3 (internal polish cycle); replace with narrow
SELF-CHECK step (structural validation only — names/POV/hook/format/word-floor).
Add anti-overpolish drafting discipline rules to PASS 1.
Add genre-aware guide-use note (apply only the guide matching {genre_name}).
Update adjudication prose_quality description to match draft-quality standard.
- chapter_polish: Convert from broad 'Rewrite the chapter' pass to bounded
editorial control pass. Explicitly forbids expansion, sensory addition,
global voice upgrades, new content. Instructs verbatim preservation of
unaffected paragraphs. Adjudication rewritten around correction fidelity
rather than 'more polished is better'. Threshold lowered from 90 to 80.
- chapter_review: Add explicit output categories — STRENGTHS TO PRESERVE,
MUST-FIX CONTINUITY, MUST-FIX CLARITY, OPTIONAL, FORBIDDEN, VERDICT.
Remove 'REWRITE' verdict option (roundtable resolves that). Remove all three
writing-craft guides (editorial tasks do not need genre writing guidance).
- chapter_roundtable: Update CONSENSUS REACHED block to MUST APPLY / OPTIONAL /
PRESERVE / VERDICT categories. Require disagreements to be resolved before
calling consensus. Remove REWRITE verdict option. Remove all writing-craft
guides. Remove 'skills' from sections. Add package hint to populate key_changes
from the full structured consensus. Update adjudication to score structured output.
- book_outline: Strengthen Voice & Tone Guide as hard operating constraints
(not aspirations); include anti-overpolish rules, rhythm rules, and voice
don'ts. Expand per-chapter outline format to include Opens-at location,
Character state, and Dominant tension. Enrich chapter task description
packets with that state data so book_chapter has richer upstream context.
- skills/skills.md: Document writing-vs-editorial guide split established in
Sprint 56. Update Used-by column. Add boundary rules section.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
46 lines
2.6 KiB
Markdown
46 lines
2.6 KiB
Markdown
# Crimson Leaf Publishing — Skills Catalog
|
|
|
|
Skills are context-sensitive reference documents injected into an agent's prompt
|
|
when a template declares a `skills:` array. They provide craft knowledge without
|
|
permanently inflating RAG storage.
|
|
|
|
## Available Guides
|
|
|
|
| Path | Purpose | Used by |
|
|
|------|---------|---------|
|
|
| `guides/YAFictionGuide.md` | YA genre conventions, voice rules, tropes, audience sensitivities | `book_chapter` (when genre is YA — apply only this guide) |
|
|
| `guides/RomanceFictionGuide.md` | Romance beats, HEA/HFN requirement, sub-genre map, tension escalation | `book_chapter` (when genre is Romance — apply only this guide) |
|
|
| `guides/SciFiFictionGuide.md` | World-building discipline, tech credibility, sub-genre map, pacing | `book_chapter` (when genre is Sci-Fi — apply only this guide) |
|
|
| `guides/BlogWritingGuide.md` | Blog structure, hook styles, CTA patterns, voice rules | `blog_write`, `blog_research` |
|
|
| `guides/RecipeWritingGuide.md` | Recipe format, headnote style, ingredient conventions, method voice | `recipe_develop`, `recipe_collection_plan` |
|
|
|
|
## Writing vs Editorial Guide Rules (Sprint 56)
|
|
|
|
**Writing templates** (`book_outline`, `book_chapter`, `short_story`) receive genre-appropriate
|
|
craft guides. All three fiction guides are currently injected into `book_chapter` so it can
|
|
serve any fiction genre — the template instructs the agent to apply ONLY the guide matching
|
|
`{genre_name}` and ignore the others.
|
|
|
|
**Editorial templates** (`chapter_review`, `chapter_roundtable`, `chapter_polish`) do NOT
|
|
receive writing-craft guides. Writing-style guidance injected into editorial tasks creates
|
|
conflicting signals and can trigger unintended prose rewriting. Editorial agents rely on
|
|
their own domain expertise and the chapter text itself.
|
|
|
|
This boundary was established in Sprint 56 to prevent conflicting craft signals and reduce
|
|
downstream voice drift.
|
|
|
|
## How Skills Work
|
|
|
|
1. A template declares `skills: ["guides/YAFictionGuide.md"]` at the top level.
|
|
2. At prompt assembly time, the pipeline fetches each file from `pae/crimson_leaf_publishing/skills/{path}`.
|
|
3. Content is injected as the `*** SKILLS & GUIDES ***` section in the agent's prompt.
|
|
4. The agent reads the guide as authoritative reference material for the current task.
|
|
|
|
## Adding a New Skill Guide
|
|
|
|
1. Create the file in `guides/`
|
|
2. Add an entry to this table
|
|
3. Reference the path in the relevant template's `skills:` array
|
|
4. Follow the writing-vs-editorial boundary rule above: writing guides belong only in
|
|
writing templates; editorial templates should not inject writing-craft guides
|