Add original_operator_prompt chain of custody to templates
- planning.yml: instructs LLM to include ORIGINAL REQUEST in child descriptions
- create_company.yml: references {original_operator_prompt} as hard constraint + ALIGNMENT CHECK
- create_company.yml: adds request_alignment criterion (weight 15) to adjudication
- hire_agent.yml: references {original_operator_prompt} for hiring context
- quick.yml: single-pass execution template
This commit is contained in:
@@ -71,7 +71,10 @@ 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.
|
||||
- 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)
|
||||
|
||||
Reference in New Issue
Block a user