Files
crimson_leaf/templates/design_roundtable.yml
David Baity 63e715d570 fix: agent template mappings + roundtable sections injection
Critical: Peter was missing design_review — spawned tasks would go unclaimed.
All 4 agents now have design_roundtable in supported_templates.
Removed design_polish from Peter (Elena does polish, not Peter).
Added sections block to design_roundtable for deliverables/RAG access.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-01 01:04:47 -05:00

85 lines
2.3 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name: design_roundtable
description: >
The Crimson Leaf board debates their independent design reviews in 23
structured rounds, reaching consensus on required changes before polish.
participants:
- Peter
- David
- Sarah
- Elena
iteration_limit: 3
convergence_signal: "CONSENSUS REACHED"
sections:
- agent
- project
- rag
- deliverables
- message
- instructions
steps:
- type: boardroom
loop:
max_iterations: 3
condition: until_consensus
hint: |
You are {agent.name}.
{agent.identity}
You have the Company Design Specification and all independent reviews above.
COMPANY DESIGN UNDER REVIEW: {task.message}
YOUR REVIEW:
{this_agent_review}
OTHER REVIEWS:
[Peter] {peter_review}
[David] {david_review}
[Sarah] {sarah_review}
[Elena] {elena_review}
Round {task.iteration} of the design review debate.
Respond to the other board members' most critical points:
- Where you agree, say so clearly and move on.
- Where you disagree, argue your position with specific evidence.
- If you've changed your mind based on someone's argument, say so.
Focus on ACTIONABLE changes. The output of this roundtable will be used
to polish the design specification before bootstrap.
The group must converge on:
1. Final verdict: GO (proceed to polish) or KILL (abandon this company)
2. If GO: the exact list of changes to make during polish
3. Any unresolved risks that must be accepted or mitigated
When the group has reached sufficient consensus for the polish step,
end your response with: CONSENSUS REACHED
- type: package
schema:
consensus_critique: string
design_verdict: string
peter_final: string
david_final: string
sarah_final: string
elena_final: string
key_changes: list
spawn:
- task_type: design_polish
task_name: "Polish Design: {task.message}"
agent_name: Elena
context:
design_spec: "{design_spec}"
consensus_critique: "{consensus_critique}"
key_changes: "{key_changes}"
design_verdict: "{design_verdict}"
peter_final: "{peter_final}"
david_final: "{david_final}"
sarah_final: "{sarah_final}"
elena_final: "{elena_final}"