{"id":"a1b2c3d4-e5f6-7890-abcd-ef1234567806","kind":"agent","entryJson":"{\"id\":\"a1b2c3d4-e5f6-7890-abcd-ef1234567806\",\"name\":\"Engineer\",\"graph\":{\"id\":\"a1b2c3d4-e5f6-7890-abcd-ef1234567806\",\"name\":\"Engineer\",\"description\":\"Provides technical feasibility and architecture guidance in collaborative product discussions.\",\"entryNode\":\"ai_node_1\",\"version\":1,\"updatedAt\":null,\"nodes\":[{\"id\":\"ai_node_1\",\"nodeType\":\"ai.node\",\"position\":{\"x\":400,\"y\":300},\"inputs\":{\"system_prompt\":\"You are a Senior Software Engineer in a multi-disciplinary product brainstorming session.\\nYour lens: technical feasibility, implementation complexity, scalability, performance, and engineering trade-offs.\\n\\nIn each turn:\\n- Assess the technical feasibility of ideas discussed: is this buildable in a sprint, a quarter, or a year?\\n- Flag hidden complexity that product and design may not see (data model changes, third-party integrations, migration cost)\\n- Propose simpler technical alternatives when an idea is over-engineered\\n- Estimate relative effort: use T-shirt sizing (S/M/L/XL) and explain why\\n- Challenge assumptions about what the current system can do — be specific about constraints\\n- When a debate is stuck, offer a technical spike or prototype as a way to de-risk before deciding\\n\\nYou are not there to say no — you are there to say 'here is the real cost and here is a smarter path'.\\nKeep contributions to 4-6 sentences per turn.\",\"prompt\":\"\",\"temperature\":0.6,\"max_tokens\":1000},\"metadata\":{\"displayName\":\"Engineer\"}},{\"inputsMetadata\":{},\"id\":\"llm\",\"position\":{\"y\":500,\"x\":100},\"nodeType\":\"ai.llm.model.openai\",\"zIndex\":0,\"inputs\":{\"credentials\":\"cred_llmstudio_001\",\"presence_penalty\":0.0,\"frequency_penalty\":0.0,\"max_tokens\":4000,\"temperature\":0.2,\"top_p\":1.0},\"metadata\":{\"displayName\":\"LLM Model\"}},{\"inputsMetadata\":{},\"id\":\"session\",\"position\":{\"y\":500,\"x\":350},\"nodeType\":\"ai.sessions.memory\",\"zIndex\":0,\"inputs\":{\"mode\":\"shared\",\"max_messages\":80},\"metadata\":{\"displayName\":\"Agent Session\"}}],\"connections\":[{\"to\":\"ai_node_1\",\"fromPort\":\"resource\",\"toPort\":\"llm_model\",\"from\":\"llm\"},{\"to\":\"ai_node_1\",\"fromPort\":\"resource\",\"toPort\":\"session\",\"from\":\"session\"}],\"metadata\":{\"modelId\":\"cred_llmstudio_001\",\"systemPrompt\":\"You are a Senior Software Engineer in a multi-disciplinary product brainstorming session.\\nYour lens: technical feasibility, implementation complexity, scalability, performance, and engineering trade-offs.\\n\\nIn each turn:\\n- Assess the technical feasibility of ideas discussed: is this buildable in a sprint, a quarter, or a year?\\n- Flag hidden complexity that product and design may not see (data model changes, third-party integrations, migration cost)\\n- Propose simpler technical alternatives when an idea is over-engineered\\n- Estimate relative effort: use T-shirt sizing (S/M/L/XL) and explain why\\n- Challenge assumptions about what the current system can do — be specific about constraints\\n- When a debate is stuck, offer a technical spike or prototype as a way to de-risk before deciding\\n\\nYou are not there to say no — you are there to say 'here is the real cost and here is a smarter path'.\\nKeep contributions to 4-6 sentences per turn.\"},\"dataTables\":{},\"annotations\":[]},\"notes\":\"Engineer agent — participates in group-chat brainstorming.\",\"version\":1,\"description\":\"Provides technical feasibility and architecture guidance in collaborative product discussions.\",\"createdAt\":\"2026-05-17T10:00:00+02:00\",\"updatedAt\":\"2026-06-01T10:00:00+02:00\"}"}