Skip to content

site-spec: strengthen Round 1 stop instruction to prevent tool calls in same turn#3615

Open
lezama wants to merge 1 commit into
trunkfrom
fix-site-spec-round1-stop-instruction
Open

site-spec: strengthen Round 1 stop instruction to prevent tool calls in same turn#3615
lezama wants to merge 1 commit into
trunkfrom
fix-site-spec-round1-stop-instruction

Conversation

@lezama
Copy link
Copy Markdown
Contributor

@lezama lezama commented May 26, 2026

What

Fixes a bug in the /site-spec skill where the agent would ask the site name in text output and immediately call AskUserQuestion for Round 2 layout choices in the same turn — effectively skipping the name question entirely.

Why

The previous instruction said "Stop here and wait for their reply — do NOT call any tools" but the model violated it. The updated wording makes the constraint explicit: the response must end immediately after the name question, with no tool calls and no additional text.

Changes

  • apps/cli/ai/skills/site-spec/SKILL.md: Rewrites the Round 1 stop instruction with a Critical callout that spells out the constraint unambiguously.

Testing

  1. Run npm run cli:build
  2. In Studio AI chat, say something like "ayudame a crear un sitio" (no site name provided)
  3. Agent should ask for the name in text and stop — no tool calls, no layout question
  4. Reply with the name → agent should proceed to Round 2 (AskUserQuestion for layout)

…in same turn

If the agent asks for the site name in text, it must end the response
immediately — no tool calls, no Round 2 questions. The previous instruction
('Stop here and wait for their reply — do NOT call any tools') was too weak
and the agent violated it by asking in text then immediately calling ask_user
for Round 2 in the same turn, skipping the name question entirely.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant