From 37d1c5d90f0798a9c19dda2a6590c1d83f77c2e1 Mon Sep 17 00:00:00 2001 From: Backtalk6858 Date: Sat, 27 Jun 2026 16:39:16 -0500 Subject: [PATCH] =?UTF-8?q?docs:=20sprint=20day=2011=20session=203=20?= =?UTF-8?q?=E2=80=94=20agent-sudo=20design,=20projects=20DB,=20infrastruct?= =?UTF-8?q?ure=20migration?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Sonnet 4.6 --- agent-builder/.claude/playbook_agent_builder_agent.md | 2 +- agent-builder/.claude/playbook_n8n_builder_agent.md | 2 +- agent-builder/.claude/playbook_testing_methodology.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/agent-builder/.claude/playbook_agent_builder_agent.md b/agent-builder/.claude/playbook_agent_builder_agent.md index b9a7f66..3b58b36 100644 --- a/agent-builder/.claude/playbook_agent_builder_agent.md +++ b/agent-builder/.claude/playbook_agent_builder_agent.md @@ -96,7 +96,7 @@ If Ollama call fails or times out (>120s): set builder_status = 'failed', log er Pass the generated code to `claude -p` for structural review. Keep the prompt minimal to conserve SDK credits: ```bash -claude -p "Review this {type} automation code for the following only: +claude -p --model claude-sonnet-4-6 --thinking medium "Review this {type} automation code for the following only: 1. Does it correctly fetch secrets from Vault via AppRole (never hardcoded)? 2. Are there any obvious syntax errors or missing imports? 3. Does the logic match this spec summary: {name} — {task_description[:200]} diff --git a/agent-builder/.claude/playbook_n8n_builder_agent.md b/agent-builder/.claude/playbook_n8n_builder_agent.md index 9feee1b..0ab7877 100644 --- a/agent-builder/.claude/playbook_n8n_builder_agent.md +++ b/agent-builder/.claude/playbook_n8n_builder_agent.md @@ -110,7 +110,7 @@ If Ollama call fails or times out (>120s): set builder_status = 'failed', log er Pass the generated JSON to `claude -p` for structural review. Keep prompt minimal to conserve SDK credits: ```bash -claude -p "Review this N8N workflow JSON for the following only: +claude -p --model claude-sonnet-4-6 --thinking medium "Review this N8N workflow JSON for the following only: 1. Is it valid N8N workflow JSON with required fields (name, nodes, connections, active, settings)? 2. Do all nodes have id, name, type, typeVersion, position, parameters? 3. Do connections reference node names that exist in the nodes array? diff --git a/agent-builder/.claude/playbook_testing_methodology.md b/agent-builder/.claude/playbook_testing_methodology.md index 03cec99..d218d4d 100644 --- a/agent-builder/.claude/playbook_testing_methodology.md +++ b/agent-builder/.claude/playbook_testing_methodology.md @@ -48,7 +48,7 @@ Does it deploy to sandbox without errors? | Type | Check | |---|---| | `n8n_automation` | `POST /api/v1/workflows` succeeds; workflow appears in sandbox N8N UI; all credentials are assigned (no empty credential IDs) | -| `claude_agent` | Container builds and starts; `docker ps` shows healthy; `claude -p "echo ok"` returns without error from within the agent's execution context | +| `claude_agent` | Container builds and starts; `docker ps` shows healthy; `claude -p --model claude-sonnet-4-6 --thinking medium "echo ok"` returns without error from within the agent's execution context | | `script` | Docker image builds; container starts; first log line appears within 30 seconds; exit code is 0 for one-shot scripts or container stays running for daemon scripts | **Pass criteria:** No deployment errors, artifact is reachable. **Fail action:** Log to `agent_test_results`, NTFY user, tear down partial deployment in sandbox.