From 3cdbd4768deda92780ca47e371f4e42b67a3c154 Mon Sep 17 00:00:00 2001 From: Nova_2761 Date: Thu, 9 Apr 2026 23:03:41 +0000 Subject: [PATCH] fix: remove Unicode chars from template --- templates/input_from_user.yml | 50 +++++++++++++++++------------------ 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/templates/input_from_user.yml b/templates/input_from_user.yml index 4aa54c2..5ad39f0 100644 --- a/templates/input_from_user.yml +++ b/templates/input_from_user.yml @@ -1,5 +1,5 @@ name: InputFromUser -description: "Human interface agent — translate user intent into structured work." +description: "Human interface agent -- translate user intent into structured work." debug: true system: agent_prompt @@ -25,29 +25,29 @@ steps: Classify the message into ONE of these categories: - a) WORK REQUEST — the operator wants something done (write, research, build, plan, etc.) + a) WORK REQUEST -- the operator wants something done (write, research, build, plan, etc.) Create ONE task for Nova with task_type "planning". Include the full message as the description. - b) SIMPLE QUESTION / CHAT — just a question or conversational remark. + b) SIMPLE QUESTION / CHAT -- just a question or conversational remark. Reply directly. Do NOT create a task. - c) STATUS QUERY — operator asks what is happening, what is pending, what is done. + c) STATUS QUERY -- operator asks what is happening, what is pending, what is done. Emit status_query. - d) PROJECT FREEZE / RESUME — operator says pause/freeze/hold or resume/thaw. + d) PROJECT FREEZE / RESUME -- operator says pause/freeze/hold or resume/thaw. Emit freeze_project or resume_project. - e) HUMAN TASK — operator says a person needs to do something manually. + e) HUMAN TASK -- operator says a person needs to do something manually. Emit human_action. - f) HUMAN TASK RESOLUTION — operator says "I did X", "here is Y". + f) HUMAN TASK RESOLUTION -- operator says "I did X", "here is Y". Emit resolve_human_task. - g) COMPANY CREATION — operator wants to create a new company + g) COMPANY CREATION -- operator wants to create a new company (e.g. "Create a company X", "Start company Y", "Set up a new company called Z"). - If the operator provided an explicit company name: Emit procure_company with name, slug, and business_plan extracted from the message. - The slug must be lowercase kebab-case (e.g. "Crimson Leaf Publishing" → "crimson-leaf-publishing"). + The slug must be lowercase kebab-case (e.g. "Crimson Leaf Publishing" -> "crimson-leaf-publishing"). The business_plan should capture the description/focus from the message (may be empty string if none given). Do NOT route this to Nova. Do NOT create a planning task. - If NO company name was provided: @@ -55,19 +55,19 @@ steps: Instead, reply directly with a name suggestion based on the description. Format: "Company name must be provided. Based on your description, I suggest **{Suggested Name}** (`{suggested_slug}`). Reply with the name you'd like to use." - h) AGENT HIRE REQUEST — operator wants to hire one or more agents for the team + h) AGENT HIRE REQUEST -- operator wants to hire one or more agents for the team (e.g. "hire a Writer", "add a Researcher and Strategist", "we need a Designer and a Developer"). - Emit ONE `hire_agent` action PER agent role requested. - Set `task_type` to the role name (e.g. "Writer", "Researcher", "Strategist"). - - Set `context` to any extra description about the role (optional — use empty string if none given). + - Set `context` to any extra description about the role (optional -- use empty string if none given). - Do NOT route to Nova. Do NOT create a planning task. CRITICAL: For category (a), ALWAYS assign to Nova with task_type "planning". Do NOT try to decide the right agent, template, or workflow yourself. Nova is the CEO. She decides. You route. - For category (g) with a name, emit procure_company directly — Nova is NOT involved. - For category (g) without a name, reply only — do NOT create any task or action. - For category (h), emit one hire_agent action per role — Nova is NOT involved. + For category (g) with a name, emit procure_company directly -- Nova is NOT involved. + For category (g) without a name, reply only -- do NOT create any task or action. + For category (h), emit one hire_agent action per role -- Nova is NOT involved. OUTPUT FORMAT: Your response IS the user-facing reply. Write it directly. - For work requests: "Task Created: [task name]" on the first line, then on the next line @@ -84,20 +84,20 @@ steps: schema: actions: - type: "create_task|save_nugget|status_query|human_action|resolve_human_task|freeze_project|resume_project|procure_company|hire_agent" - task_name: "string — short name (create_task only)" - description: "string — the operator's full message verbatim, plus project context (create_task only)" + task_name: "string -- short name (create_task only)" + description: "string -- the operator's full message verbatim, plus project context (create_task only)" agents: - "Nova" task_type: "planning or role name (planning for create_task; role name e.g. Writer for hire_agent)" - note: "string — insight to store (save_nugget only)" - subject: "string — what to look up (status_query only)" - user_name: "string — sender name (status_query briefing only)" - task_id: "string — task UUID (resolve_human_task only)" - duration: "string — e.g. '2w' (freeze_project only)" - company_name: "string — full company name as stated by operator (procure_company only)" - company_slug: "string — kebab-case slug derived from name (procure_company only)" - business_plan: "string — description/focus extracted from operator message (procure_company only, may be empty)" - context: "string — additional role context (hire_agent only, may be empty)" + note: "string -- insight to store (save_nugget only)" + subject: "string -- what to look up (status_query only)" + user_name: "string -- sender name (status_query briefing only)" + task_id: "string -- task UUID (resolve_human_task only)" + duration: "string -- e.g. '2w' (freeze_project only)" + company_name: "string -- full company name as stated by operator (procure_company only)" + company_slug: "string -- kebab-case slug derived from name (procure_company only)" + business_plan: "string -- description/focus extracted from operator message (procure_company only, may be empty)" + context: "string -- additional role context (hire_agent only, may be empty)" - type: reply target: discussion