Merge 7f20e7cae5 into e36f219c81

src/bmm-skills/1-analysis/bmad-prfaq/SKILL.md

@@ -69,7 +69,7 @@ Activation is complete. Continue below.
 
 ## Pre-workflow Setup
 
-1. **Output file resolution:** Set `prfaq_output_file` = `{planning_artifacts}/prfaq.md` and `prfaq_distillate_file` = `{planning_artifacts}/prfaq-distillate.md` by default. For resume detection, check whether `{planning_artifacts}/prfaq.md` exists. If it does not, check the legacy path `{planning_artifacts}/prfaq-{project_name}.md`; if the legacy file exists, set `prfaq_output_file` to that path and set `prfaq_distillate_file` to `{planning_artifacts}/prfaq-{project_name}-distillate.md` for the rest of the workflow. If either file exists, read only the first 20 lines to extract the frontmatter `stage` field and offer to resume from the next stage. Do not read the full document. If the user confirms, route directly to that stage's reference file.
+1. **Output file resolution:** Set `prfaq_output_file` = `{planning_artifacts}/prfaq.md` by default. For resume detection, check whether `{planning_artifacts}/prfaq.md` exists. If it does not, check the legacy path `{planning_artifacts}/prfaq-{project_name}.md`; if the legacy file exists, set `prfaq_output_file` to that path for the rest of the workflow. If either file exists, read only the first 20 lines to extract the frontmatter `stage` field and offer to resume from the next stage. Do not read the full document. If the user confirms, route directly to that stage's reference file.
 
 2. **Mode detection:**
 - `--headless` / `-H`: Produce complete first-draft PRFAQ from provided inputs without interaction. Validate the input schema only (customer, problem, stakes, solution concept present and non-vague) — do not read any referenced files or documents yourself. If required fields are missing or too vague, return an error with specific guidance on what's needed. Fan out artifact analyzer and web researcher subagents in parallel (see Contextual Gathering below) to process all referenced materials, then create the output document at `{prfaq_output_file}` using `./assets/prfaq-template.md` and route to `./references/press-release.md`.

src/bmm-skills/1-analysis/bmad-prfaq/references/verdict.md

@@ -31,7 +31,7 @@ Review the entire PRFAQ — press release, customer FAQ, internal FAQ — and de
 
 Throughout the process, you captured context beyond what fits in the PRFAQ. Source material for the distillate includes the `<!-- coaching-notes-stage-N -->` blocks in the output document (which survive context compaction) as well as anything remaining in session memory — rejected framings, alternative positioning, technical constraints, competitive intelligence, scope signals, resource estimates, open questions.
 
-**Always produce the distillate** at `{prfaq_distillate_file}`:
+**Always produce the distillate** at `{planning_artifacts}/prfaq-distillate.md`:
 
 ```yaml
 ---
@@ -58,7 +58,7 @@ purpose: "Token-efficient context for downstream PRD creation"
 "Your PRFAQ for {project_name} has survived the gauntlet.
 
 **PRFAQ:** `{prfaq_output_file}`
-**Detail Pack:** `{prfaq_distillate_file}`
+**Detail Pack:** `{planning_artifacts}/prfaq-distillate.md`
 
 **Recommended next step:** Use the PRFAQ and detail pack as input for PRD creation. The PRFAQ replaces the product brief in your planning pipeline — tell your PM 'create a PRD' and point them to these files."
 
@@ -67,7 +67,7 @@ purpose: "Token-efficient context for downstream PRD creation"
 {
   "status": "complete",
   "prfaq": "{prfaq_output_file}",
-  "distillate": "{prfaq_distillate_file}",
+  "distillate": "{planning_artifacts}/prfaq-distillate.md",
   "verdict": "forged|needs-heat|cracked",
   "key_risks": ["top unresolved items"],
   "open_questions": ["unresolved items from FAQs"]