From 243738551cb79b4bb883692363f949ee6bfc8e2f Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 16:37:25 +0000 Subject: [PATCH] fix: wizard README instructions explicitly require LLM to generate and write files The LLM was having the conversation with the user but never following through with wizard_generate calls. The instructions now spell out the full workflow: get hint, write content, stage it, show user, confirm. Also adds "keep moving" instruction so the LLM auto-advances to the next step after confirmation. Co-Authored-By: Claude Opus 4.6 (1M context) --- .storkit/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.storkit/README.md b/.storkit/README.md index d78af5ef..894cab3c 100644 --- a/.storkit/README.md +++ b/.storkit/README.md @@ -13,7 +13,8 @@ When you start a new session with this project: - **Be conversational.** Don't show tool names, step numbers, or raw wizard output to the user. - **On projects with existing code:** Read the codebase and generate each file, then show the user what you wrote and ask if it looks right. - **On bare projects with no code:** Ask the user what they want to build, what language/framework they plan to use, and generate files from their answers. - - Use `wizard_generate` to create content, show it to the user, then call `wizard_confirm` (they approve), `wizard_retry` (they want changes), or `wizard_skip` (they want to skip this step). + - **You must actually generate the files.** The workflow for each step is: (1) call `wizard_generate` with no args to get a hint, (2) write the file content yourself based on the conversation, (3) call `wizard_generate` again with the `content` argument containing the full file body, (4) show the user what you wrote, (5) call `wizard_confirm` (they approve), `wizard_retry` (they want changes), or `wizard_skip` (they want to skip). Do not stop after discussing — follow through and write the files. + - **Keep moving.** After each step is confirmed, immediately proceed to the next wizard step without waiting for the user to ask. 2. **Check for MCP Tools:** Read `.mcp.json` to discover the MCP server endpoint. Then list available tools by calling: ```bash curl -s "$(jq -r '.mcpServers["storkit"].url' .mcp.json)" \