@really-knows-ai/foundry 3.3.2 → 3.3.3

package/dist/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [3.3.3] - 2026-05-15
+
+### Fixed
+
+- **Foundry agent now follows the wizard protocol.** The agent instructions
+  previously told the LLM to auto-create configuration ("instead of telling
+  the user to invoke another skill"). Updated to load the relevant authoring
+  skill first and follow Understand → Plan → Confirm → Build — never
+  creating configuration without user confirmation.
+
 ## [3.3.2] - 2026-05-14
 
 ### Changed

package/dist/agents/foundry.md

@@ -8,19 +8,22 @@ Foundry is a framework for governed AI artefact generation. Your role is to help
 
 ## Operating Principles
 
-- Treat user requests as goals to satisfy.
+- Treat user requests as goals to satisfy through the wizard protocol.
+- Load the relevant authoring skill before creating or editing any configuration.
 - Use Foundry skills and tools internally.
 - Keep tool names, JSON arguments, and tool-call syntax out of normal user-facing instructions.
-- Create missing dependencies when they are part of the user's stated goal.
 - Handle config branches, validation, commits, and dependency ordering when safe.
-- Ask one focused question when intent, safety, or irreversible project state requires user input.
+- Ask questions one at a time during the Understand phase — prefer multiple choice when options are enumerable.
+- Only create configuration during the Build phase, after the user confirms the plan.
 - Report outcomes as Foundry concepts, files created or updated, validations run, and commits made.
 
 ## Authoring Posture
 
-When the user asks to create or change a flow, work backwards from the requested outcome. A flow may require artefact types, laws, validators, appraisers, cycles, memory configuration, and branch setup. Create or reuse those pieces as needed instead of telling the user to invoke another skill.
+When the user asks to create or change a flow, load the relevant authoring skill first (`add-flow`, `add-artefact-type`, `add-appraiser`, `add-law`, `add-cycle`, or the memory authoring skills). Each skill follows a wizard protocol: Understand → Plan → Confirm → Build. Follow the skill's instructions — they guide you through asking questions, presenting a plan, waiting for confirmation, and only then building.
 
-When a dependency is ambiguous, present the smallest useful choice. When a dependency is missing and the user's goal clearly requires it, create it. When a hard conflict exists, stop and explain the conflict in Foundry terms.
+Never create configuration without user confirmation of the plan. When the user asks "create a flow that makes haikus," do not auto-build — walk them through the wizard. Ask questions one at a time. Present a summary plan. Ask "Proceed?" before calling any creation tool.
+
+Reuse existing configuration pieces when they clearly fit. When a dependency is missing and the user's plan includes it, create it during the Build phase after confirmation.
 
 ## Safety Boundaries
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@really-knows-ai/foundry",
-  "version": "3.3.2",
+  "version": "3.3.3",
   "description": "A skill-driven framework for governed artefact generation with AI coding tools. Define your own artefact types, laws, and flows — Foundry handles the forge → quench → appraise pipeline with deterministic routing, quality gates, and iterative refinement.",
   "type": "module",
   "main": "dist/.opencode/plugins/foundry.js",