Files
crimson_leaf/templates/design_roundtable.yml

95 lines
2.9 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.
debug: true
participant_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- participants
- participants_prompt
- rag
- deliverables
- message
- instructions
steps:
- type: think
route: boardroom
rotate_participants: true
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}
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: true
- type: think
agent: "Victor"
hint: |
You are Victor, CEO of Crimson Leaf LLC.
The design roundtable is complete. Synthesize the board's debate into a
structured consensus summary:
1. DESIGN VERDICT — GO or KILL, with Victor's final reasoning
2. KEY CHANGES — exact list of changes to apply during design_polish
3. CONSENSUS CRITIQUE — one paragraph summary of the board's unified position
4. VICTOR FINAL — Victor's closing statement
5. NOLAN FINAL — Nolan's final position summary
6. SARAH FINAL — Sarah's final position summary
7. ELENA FINAL — Elena's final position summary
- type: package
schema:
consensus_critique: string
design_verdict: string
victor_final: string
nolan_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}"
victor_final: "{victor_final}"
nolan_final: "{nolan_final}"
sarah_final: "{sarah_final}"
elena_final: "{elena_final}"
- type: close
rag_update: true