fix: remove Unicode chars from template
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
name: planning
|
||||
description: "Crimson Leaf executive planning — boardroom deliberation, structured task breakdown, child task dispatch."
|
||||
description: "Crimson Leaf executive planning -- boardroom deliberation, structured task breakdown, child task dispatch."
|
||||
debug: true
|
||||
system: agent_prompt
|
||||
participant_prompt:
|
||||
@@ -39,19 +39,19 @@ steps:
|
||||
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
|
||||
write_charter — draft a formal constitutional charter for a new Tenant
|
||||
create_company — incubate a new sovereign Tenant (full Genesis Protocol)
|
||||
market_intelligence — Orion scans for niche opportunities and portfolio gaps
|
||||
portfolio_architectural_review — Aris reviews the full Tenant portfolio for coherence
|
||||
audit_tenant — Sloane red-teams a Tenant's operational health
|
||||
charter_audit — Valerius checks a Tenant charter for constitutional drift
|
||||
financial_audit — Vance audits Genesis Fund health and per-Tenant ROI
|
||||
capital_allocation_audit — Vance reviews capital allocation discipline
|
||||
retire_tenant — Sloane/Vance executes Tenant dormancy or dissolution
|
||||
adjudicate_tenant — constitutional adjudication of a Genesis action or output
|
||||
quick — short single-step response or analysis
|
||||
hire_agent -- recruit a new agent to the CL roster
|
||||
write_template -- create or refine a PAE-Lang template
|
||||
write_charter -- draft a formal constitutional charter for a new Tenant
|
||||
create_company -- incubate a new sovereign Tenant (full Genesis Protocol)
|
||||
market_intelligence -- Orion scans for niche opportunities and portfolio gaps
|
||||
portfolio_architectural_review -- Aris reviews the full Tenant portfolio for coherence
|
||||
audit_tenant -- Sloane red-teams a Tenant's operational health
|
||||
charter_audit -- Valerius checks a Tenant charter for constitutional drift
|
||||
financial_audit -- Vance audits Genesis Fund health and per-Tenant ROI
|
||||
capital_allocation_audit -- Vance reviews capital allocation discipline
|
||||
retire_tenant -- Sloane/Vance executes Tenant dormancy or dissolution
|
||||
adjudicate_tenant -- constitutional adjudication of a Genesis action or output
|
||||
quick -- short single-step response or analysis
|
||||
|
||||
CRITICAL DISPATCH RULES:
|
||||
- Do NOT create planning or boardroom sub-tasks. You ARE the planning step.
|
||||
@@ -66,7 +66,7 @@ steps:
|
||||
They cannot run until market_intelligence, portfolio_architectural_review, and
|
||||
write_charter are all complete. This MUST be expressed using depends_on in the task list.
|
||||
|
||||
Be specific about agent assignments — use EXACT names from the TEAM ROSTER.
|
||||
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"
|
||||
@@ -81,7 +81,7 @@ steps:
|
||||
|
||||
For each task:
|
||||
- task_name: short, specific
|
||||
- description: full detail — enough that the assigned agent can execute without asking.
|
||||
- description: full detail -- enough that the assigned agent can execute without asking.
|
||||
CRITICAL: Include the ORIGINAL OPERATOR REQUEST verbatim in every child description
|
||||
so downstream agents know what was actually asked for. Start with
|
||||
"ORIGINAL REQUEST: <exact text>" followed by specific instructions.
|
||||
@@ -92,7 +92,7 @@ steps:
|
||||
Use the EXACT task_name strings of the blocking tasks.
|
||||
Omit this field entirely if this task has no blockers.
|
||||
|
||||
Order tasks correctly — blockers before dependents.
|
||||
Order tasks correctly -- blockers before dependents.
|
||||
No ambiguous assignments. No placeholder names.
|
||||
|
||||
VALID TASK TYPES (use ONLY these exact strings):
|
||||
@@ -114,14 +114,14 @@ steps:
|
||||
packet_type: PlanningResponsePacket
|
||||
schema:
|
||||
tasks:
|
||||
- task_name: "string — short descriptive name"
|
||||
description: "string — full instructions for the assigned agent"
|
||||
- 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"
|
||||
- "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)"
|
||||
depends_on:
|
||||
- "string — exact task_name of a blocking task (omit this field if no dependencies)"
|
||||
- "string -- exact task_name of a blocking task (omit this field if no dependencies)"
|
||||
insert_children: true
|
||||
|
||||
- type: close
|
||||
|
||||
Reference in New Issue
Block a user