singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

fix(sf): give workflow-templates/product-audit.md an absolute prompt path

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
Mikael Hugo 2026-05-02 18:39:38 +02:00
parent a3ef4bdf3f
commit 18643702b2
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/resources/extensions/sf/workflow-templates/product-audit.md
View file

@ -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`