@really-knows-ai/foundry 3.3.4 → 3.3.6

package/dist/.opencode/plugins/foundry-tools/agent-refresh.js

@@ -152,29 +152,13 @@ function resolveGuideSource(packageRoot) {
   return path.join(packageRoot, 'src', 'agents', 'foundry.md');
 }
 
-/**
- * Copy the Foundry guide agent (foundry.md) from the installed package
- * to the project's .opencode/agents/ directory.
- *
- * Resolves the source from `packageRoot/dist/agents/foundry.md` and
- * falls back to `packageRoot/src/agents/foundry.md` when the dist
- * path does not exist. Skips writing when the target file already
- * exists (uses existsSync check).
- *
- * @param {string} worktree - Absolute path to the project worktree root.
- * @param {string} packageRoot - Absolute path to the installed package root.
- * @returns {{ ok: true, written: boolean } | { ok: false, error: string }}
- */
 export function writeFoundryGuideAgent(worktree, packageRoot) {
   const targetDir = path.join(worktree, '.opencode', 'agents');
   const targetPath = path.join(targetDir, 'foundry.md');
 
-  if (existsSync(targetPath)) {
-    return { ok: true, written: false };
-  }
+  if (existsSync(targetPath)) return { ok: true, written: false };
 
   const sourcePath = resolveGuideSource(packageRoot);
-
   try {
     const content = readFileSync(sourcePath, 'utf8');
     mkdirSync(targetDir, { recursive: true });
@@ -184,3 +168,4 @@ export function writeFoundryGuideAgent(worktree, packageRoot) {
     return { ok: false, error: `Failed to write guide agent: ${err.message ?? String(err)}` };
   }
 }
+

package/dist/.opencode/plugins/foundry.js

@@ -218,6 +218,9 @@ export const FoundryPlugin = async ({ directory }) => {
         config.skills.paths.push(allSkillsDir);
       }
 
+      // Always ensure guide agent is up to date
+      ensureGuideAgent(directory, packageRoot);
+
       restartNeeded = runPluginBootstrap(directory, packageRoot);
     },
 

package/dist/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [3.3.6] - 2026-05-18
+
+### Fixed
+
+- **Foundry skills reference in agent.** The Foundry agent now lists all 27
+  skills in an "Available Skills" table with their purposes and instructions
+  on how to load them via the `skill` tool. The LLM can call
+  `skill({name: "add-flow"})` etc. without needing them listed in the
+  system prompt's `available_skills` section.
+
 ## [3.3.4] - 2026-05-18
 
 ### Fixed

package/dist/agents/foundry.md

@@ -9,7 +9,7 @@ Foundry is a framework for governed AI artefact generation. Your role is to help
 ## Operating Principles
 
 - Treat user requests as goals to satisfy through the wizard protocol.
-- Load the relevant authoring skill before creating or editing any configuration.
+- Call the `skill` tool to 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.
 - Handle config branches, validation, commits, and dependency ordering when safe.
@@ -28,9 +28,42 @@ Foundry is a framework for governed AI artefact generation. Your role is to help
 
 When discussing laws with the user, say they are "rules" or "criteria." Present which elements can be script-checked (with validators) and which elements require the appraiser's judgment. Never label a law itself as "deterministic" or "subjective."
 
+## Available Skills
+
+All skills are registered by the Foundry plugin and loadable via `skill({name: "<name>"})`. Load the relevant skill before creating or editing configuration, or when a user task matches a skill's purpose.
+
+| Skill | Use when |
+|-------|----------|
+| `add-flow` | Creating a complete flow from scratch — asks about artefacts, laws, appraisers, cycles |
+| `add-artefact-type` | Defining a new artefact type with file patterns and appraiser config |
+| `add-appraiser` | Creating a new appraiser personality |
+| `add-law` | Defining a law with passing/failing criteria and optional validators |
+| `add-cycle` | Creating a cycle within an existing flow |
+| `add-extractor` | Registering a memory extractor CLI that emits JSONL |
+| `add-memory-entity-type` | Declaring a new entity type in flow memory |
+| `add-memory-edge-type` | Declaring a new edge type between entity types |
+| `init-memory` | Scaffolding the flow memory directory structure |
+| `rename-memory-entity-type` | Renaming an entity type and migrating edges |
+| `rename-memory-edge-type` | Renaming an edge type |
+| `change-embedding-model` | Switching the embedding model and re-embedding entities |
+| `reset-memory` | Purging all memory data while keeping type definitions |
+| `drop-memory-entity-type` | Deleting an entity type and cascading to edges |
+| `drop-memory-edge-type` | Deleting an edge type and all its rows |
+| `orchestrate` | Running a foundry cycle by calling `foundry_orchestrate` in a loop |
+| `flow` | Running a defined flow — pass the user's request as the goal |
+| `forge` | Producing or revising an artefact during a cycle |
+| `quench` | Running deterministic validators on an artefact |
+| `appraise` | Subjectively evaluating an artefact against laws via appraisers |
+| `human-appraise` | Presenting the artefact to the human for review |
+| `assay` | Populating flow memory by running extractor scripts |
+| `dry-run` | Trial-running a flow on a dry-run branch |
+| `upgrade-foundry` | Rebuilding configuration for the current plugin version |
+| `list-agents` | Listing available foundry-* sub-agents |
+| `refresh-agents` | Regenerating foundry-* agent files after model changes |
+
 ## Authoring Posture
 
-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 the user asks to create or change a flow, call the `skill` tool to load the relevant authoring skill (`add-flow`, `add-artefact-type`, `add-appraiser`, `add-law`, `add-cycle`, or the memory authoring skills). These skills are registered by the Foundry plugin and are always available even if not listed in `available_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.
 
 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.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@really-knows-ai/foundry",
-  "version": "3.3.4",
+  "version": "3.3.6",
   "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",