From 18643702b280685508adcdac166ace9a0ce921de Mon Sep 17 00:00:00 2001 From: Mikael Hugo Date: Sat, 2 May 2026 18:39:38 +0200 Subject: [PATCH] fix(sf): give workflow-templates/product-audit.md an absolute prompt path MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Step 1 said "Load the audit prompt at \`prompts/product-audit.md\`". That's a relative path the dispatched LLM would resolve against the project's working directory — but \`prompts/product-audit.md\` doesn't live in the user's project; it lives in the bundled extension copied to \`~/.sf/agent/extensions/sf/prompts/\` (per prompt-loader.ts:50 __extensionDir/prompts). LLMs running this workflow would either fail to find the file, walk the filesystem looking for it, or skip the guidance silently. Now points at the canonical location and clarifies that the prompt holds evidence-collection guidance and output schema (the structured tool sf_product_audit handles persistence). Partially addresses sf-monzctqw-w4g85x — the path is now right; the broader prompt-vs-hardcoded-tool design tension is left for a real triage decision. Co-Authored-By: Claude Opus 4.7 (1M context) --- src/resources/extensions/sf/workflow-templates/product-audit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/resources/extensions/sf/workflow-templates/product-audit.md b/src/resources/extensions/sf/workflow-templates/product-audit.md index d85bae634..f0f20ee0e 100644 --- a/src/resources/extensions/sf/workflow-templates/product-audit.md +++ b/src/resources/extensions/sf/workflow-templates/product-audit.md @@ -24,7 +24,7 @@ hard-block milestone completion — actionable gaps become follow-up slices. **Goal:** Produce a structured PRODUCT-AUDIT artifact for the active milestone. -1. Load the audit prompt at `prompts/product-audit.md`. +1. Load the audit prompt at `~/.sf/agent/extensions/sf/prompts/product-audit.md` — that file holds the detailed evidence-collection guidance and output schema for this audit. 2. Treat repo docs (VISION.md, README.md, docs/RUNBOOKS.md, milestone artifacts) as the product contract. Do not invent expectations. 3. Inspect the codebase using native `lsp`, AST tools, and `rg`