Files
crimson_leaf/templates/company_design.yml

161 lines
6.0 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: company_design
description: "Boardroom deliberation — the full Crimson Leaf board debates and designs a new company."
debug: true
system: agent_prompt
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}. This is round {task.iteration} of the Crimson Leaf boardroom.
You are in a room with {agent_roster}.
The board is designing a new autonomous company based on the Market Opportunity Pitch
in the deliverables above. Every voice matters — this is a real debate, not a presentation.
YOUR RESPONSIBILITIES BY ROLE:
- Sarah: Defend your research. Challenge assumptions about market size and demand.
Push back if the board drifts from what the data supports.
- Elena: Propose the agent roster (48 roles), chain of command, and pipeline SOP.
Specify exact task dependencies and execution order.
- Nolan: Map Elena's pipeline to concrete PAE templates and tools. Flag any step
that can't be executed with existing infrastructure. Propose procurement list.
- Victor: Challenge profitability. Ask hard questions about revenue model, cost
structure, and time to first deliverable. You have Go/No-Go authority.
Write YOUR perspective on this round's discussion. React to what others said.
Challenge what you disagree with. Build on what resonates.
THE DESIGN MUST INCLUDE (when consensus is reached):
1. Company name and slug
2. One-paragraph business plan
3. Agent roster: name, role, title, department, key responsibility (48 agents)
4. Template procurement list: which generic templates to import from Global
5. Pipeline SOP: numbered sequence of task types with dependencies
6. Revenue model and success metrics
When the group has genuinely reached consensus, include exactly:
"consensus_reached: true"
If debate should continue, do NOT include that line.
- type: think
route: llm
agent: "Victor"
hint: |
You are Victor, CEO of Crimson Leaf LLC.
The boardroom debate is complete. Synthesize the full transcript into a
COMPANY DESIGN SPECIFICATION document with these exact sections:
1. EXECUTIVE SUMMARY — Company name, slug, one-paragraph mission
2. MARKET JUSTIFICATION — Why this company, why now (from Sarah's research)
3. AGENT ROSTER — Table: Name | Role | Title | Department | Responsibility
4. CHAIN OF COMMAND — Who manages whom, department structure
5. TEMPLATE STACK — Exact list of templates to procure (from Nolan's analysis)
6. PIPELINE SOP — Numbered steps with task_type, agent, dependencies (from Elena)
7. REVENUE MODEL — How the company makes money
8. SUCCESS METRICS — Measurable targets for the first 30/60/90 days
9. RISKS & MITIGATIONS — Top 3 risks with mitigation strategies
10. GO/NO-GO DECISION — Your final verdict with reasoning
Be precise. This document is the blueprint that bootstrap_company will execute.
- type: document
filename: "company-design-spec-{{task_name_slug}}"
- type: reply
target: discussion
style: |
Present the Company Design Specification to the operator. Highlight the key
decisions: company name, agent roster size, template stack, and revenue model.
End with: "Does this design align with your vision? Reply to approve or suggest changes."
- type: package
hint: |
The design specification is complete and presented to the operator.
Spawn a human approval gate — the review cycle will NOT start until
the operator confirms the design direction is correct.
schema:
design_spec: string
spawn:
- task_type: human_action
task_name: "Operator Review: Approve Design Direction — {task.message}"
agent_name: Victor
priority: 8
context:
design_spec: "{design_spec}"
gate_purpose: "Review company design spec, approve before review cycle begins"
- task_type: design_review
task_name: "Design Review (Victor): {task.message}"
agent_name: Victor
priority: 6
context:
design_spec: "{design_spec}"
review_focus: financial_viability
depends_on:
- "Operator Review: Approve Design Direction — {task.message}"
- task_type: design_review
task_name: "Design Review (Nolan): {task.message}"
agent_name: Nolan
priority: 6
context:
design_spec: "{design_spec}"
review_focus: technical_feasibility
depends_on:
- "Operator Review: Approve Design Direction — {task.message}"
- task_type: design_review
task_name: "Design Review (Sarah): {task.message}"
agent_name: Sarah
priority: 6
context:
design_spec: "{design_spec}"
review_focus: market_fit
depends_on:
- "Operator Review: Approve Design Direction — {task.message}"
- task_type: design_review
task_name: "Design Review (Elena): {task.message}"
agent_name: Elena
priority: 6
context:
design_spec: "{design_spec}"
review_focus: operational_completeness
depends_on:
- "Operator Review: Approve Design Direction — {task.message}"
- task_type: design_roundtable
task_name: "Design Roundtable: {task.message}"
agents: [Victor, Nolan, Sarah, Elena]
priority: 7
context:
design_spec: "{design_spec}"
depends_on:
- "Design Review (Victor): {task.message}"
- "Design Review (Nolan): {task.message}"
- "Design Review (Sarah): {task.message}"
- "Design Review (Elena): {task.message}"
- type: close
rag_update: true