4.4 KiB

Raw Blame History

Language: Use {communication_language} for all output. Output Language: Use {document_output_language} for documents. Output Location: {planning_artifacts} Paths: Bare paths (e.g. prompts/foo.md) resolve from the skill root.

Stage 5: Finalize

Goal: Save the polished brief, offer the LLM distillate, and point the user forward.

Step 1: Polish and Save

Resolve brief_output_file before updating: keep the existing value if it is already set, otherwise use {planning_artifacts}/product-brief.md. If this is a legacy in-progress brief created before generic filenames were introduced and {planning_artifacts}/product-brief.md does not exist, set brief_output_file to {planning_artifacts}/product-brief-{project_name}.md instead. Update the active product brief document at {brief_output_file}:

Update frontmatter status to "complete"
Update updated timestamp
Ensure formatting is clean and consistent
Confirm the document reads well as a standalone 1-2 page executive summary

Step 2: Offer the Distillate

Throughout the discovery process, you likely captured detail that doesn't belong in a 1-2 page executive summary but is valuable for downstream work — requirements hints, platform preferences, rejected ideas, technical constraints, detailed user scenarios, competitive deep-dives, etc.

Ask the user: "Your product brief is complete. During our conversation, I captured additional detail that goes beyond the executive summary — things like [mention 2-3 specific examples of overflow you captured]. Would you like me to create a detail pack for PRD creation? It distills all that extra context into a concise, structured format optimized for the next phase."

If yes, create the distillate at {planning_artifacts}/product-brief-distillate.md:

---
title: "Product Brief Distillate: {project_name}"
type: llm-distillate
source: "{brief_output_file}"
created: "{timestamp}"
purpose: "Token-efficient context for downstream PRD creation"
---

Distillate content principles:

Dense bullet points, not prose
Each bullet carries enough context to be understood standalone (don't assume the reader has the full brief loaded)
Group by theme, not by when it was mentioned
Include:
- Rejected ideas — so downstream workflows don't re-propose them, with brief rationale
- Requirements hints — anything the user mentioned that sounds like a requirement
- Technical context — platforms, integrations, constraints, preferences
- Detailed user scenarios — richer than what fits in the exec summary
- Competitive intelligence — specifics from web research worth preserving
- Open questions — things surfaced but not resolved during discovery
- Scope signals — what the user indicated is in/out/maybe for MVP
Token-conscious: be concise, but give enough context per bullet so an LLM reading this later understands WHY each point matters

Headless mode: Always create the distillate automatically — unless the session was too brief to capture meaningful overflow (in that case, note this in the completion output instead of creating an empty file).

Step 3: Present Completion

"Your product brief for {project_name} is complete!

Executive Brief: {brief_output_file} [If distillate created:] Detail Pack: {planning_artifacts}/product-brief-distillate.md

Recommended next step: Use the product brief (and detail pack) as input for PRD creation — tell your assistant 'create a PRD' and point it to these files." [If distillate created:] "The detail pack contains all the overflow context (requirements hints, rejected ideas, technical constraints) specifically structured for the PRD workflow to consume."

Headless mode: Output the file paths as structured JSON and exit:

{
  "status": "complete",
  "brief": "{brief_output_file}",
  "distillate": "{path or null}",
  "confidence": "high|medium|low",
  "open_questions": ["any unresolved items"]
}

Stage Complete

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete

If the resolved workflow.on_complete is non-empty, follow it as the final terminal instruction before exiting. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to prompts/draft-and-review.md. Otherwise, exit.

4.4 KiB Raw Blame History