fix(clp): genericise templates — no hardcoded agents/companies/task-types
- planning.yml: roster-driven task types, no hardcoded agent names or generic types - chapter_roundtable.yml: removed fixed [Devon,Lane,Cora] participant list, any editor can join - book_chapter.yml: removed hardcoded agents from roundtable spawn - book_research.yml: removed agent: Atlas from book_outline spawn (Bouncer routes by type) - ai_article_research.yml: removed agent_name: Atlas from plan spawn - book_editorial.yml: removed Shadow Heir/Elara/Kai/Alpha Publishing/Wattpad hardcoding - project_index.yml: removed Wattpad reference - ai_article_write.yml: fixed adjudication criteria (article, not fiction chapter) - chapter_review.yml: reply→document so reviews are committed and accessible Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
@@ -30,12 +30,13 @@ steps:
|
||||
- Which agents from the TEAM ROSTER are best suited to each piece?
|
||||
- What risks, gaps, or open questions do you see?
|
||||
- What do you agree or disagree with from prior planning rounds above?
|
||||
Reference these TASK TYPES when recommending work: research_plus, outline, draft, review, roundtable, polish, quick, writing, analysis, brainstorm, code.
|
||||
Reference the TEAM ROSTER above for agent names and the task types they own.
|
||||
Use EXACT task type names from each agent's supported_templates list — these are the
|
||||
template filenames the Bouncer uses to route tasks. Do NOT invent task type names.
|
||||
Be specific about agent assignments — use EXACT names from the TEAM ROSTER.
|
||||
ROUNDTABLE CHAIR RULE: For business strategy, planning, or operations roundtables, the chair
|
||||
must be a business-register agent (Atlas, Selene, Devon, or Lane). Do NOT assign Cassius,
|
||||
Lyra, or other fiction-specialist agents as chair for business deliverables — their creative
|
||||
voice will contaminate formal strategy documents with genre-specific jargon.
|
||||
ROUNDTABLE CHAIR RULE: For business strategy or operations deliberations, assign the chair
|
||||
to a business-register agent (director or executive role). Do NOT assign pure writing or
|
||||
creative-execution agents as chair for planning deliverables.
|
||||
When the group has genuinely agreed on a complete plan, include exactly:
|
||||
"consensus_reached: true"
|
||||
If the plan still has gaps or unresolved assignments, do NOT include that line.
|
||||
|
||||
Reference in New Issue
Block a user