Files
crimson_leaf/templates/planning.yml
David Baity 51dbf9f089 fix: remove recursive task types from planning template
Planning was spawning sub-planning and boardroom tasks which cascaded into dozens
of duplicate create_company attempts. Now only emits leaf tasks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-10 12:19:15 -04:00

106 lines
4.0 KiB
YAML

name: planning
description: "Crimson Leaf executive planning — boardroom deliberation, structured task breakdown, child task dispatch."
debug: true
system: agent_prompt
participant_prompt:
- "= identity.md"
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- history
- rag
- participants
- participants_prompt
- roster
- templates
- message
- instructions
steps:
- type: think
rotate_participants: true
loop:
max_iterations: 3
hint: |
You are {agent.name}. This is round {task.iteration} of the Crimson Leaf planning session.
The executive board is breaking down this initiative into a concrete work plan.
Write YOUR perspective from your area of expertise:
- What work streams or tasks need to exist?
- What order must they happen in? What depends on what?
- 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?
CRIMSON LEAF CONTEXT:
Crimson Leaf is a holding company and incubator. It does NOT produce consumer deliverables.
Valid work for CL includes: market research, corporate architecture, executive recruitment,
portfolio governance, charter design, template authoring, and company incubation.
Reference these TASK TYPES when recommending work:
hire_agent — recruit a new agent to the CL roster
write_template — create or refine a PAE-Lang template
create_company — incubate a new sovereign Tenant
quick — short single-step response
CRITICAL DISPATCH RULES:
- Do NOT create planning or boardroom sub-tasks. You ARE the planning step.
All deliberation happens HERE in this session, not as child tasks.
- Produce ONLY actionable leaf tasks (hire_agent, write_template, create_company, quick).
- For company creation: emit ONE create_company task with ALL details in the description.
Do NOT split charter design, CEO recruitment, and company creation into separate tasks.
The create_company template handles the full flow internally.
Be specific about agent assignments — use EXACT names from the TEAM ROSTER.
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.
- type: think
agent: first_available
hint: |
Structure the team's agreed plan into a precise task list.
IMPORTANT: Do NOT re-deliberate or reconsider what was agreed above.
Your only job is to serialize the decisions into clean task records.
For each task:
- task_name: short, specific
- description: full detail — enough that the assigned agent can execute without asking
- agents: EXACT name(s) from TEAM ROSTER
- task_type: MUST be one of the valid template names listed below
- priority: 1 (critical) to 5 (nice-to-have)
Order tasks correctly — blockers before dependents.
No ambiguous assignments. No placeholder names.
VALID TASK TYPES (use ONLY these exact strings):
hire_agent, write_template, create_company, quick
RULES:
- Do NOT emit planning or boardroom tasks. Deliberation already happened above.
- For create_company: emit ONE task with the full opportunity in the description.
- type: package
packet_type: PlanningResponsePacket
schema:
tasks:
- task_name: "string — short descriptive name"
description: "string — full instructions for the assigned agent"
agents:
- "string — EXACT agent name from TEAM ROSTER"
task_type: "string — MUST be a template name from the valid list"
priority: "integer 1 (critical) to 5 (nice-to-have)"
insert_children: true
- type: close
rag_update: false
adjudication:
enabled: false