Grill the presentation product
Use when product-grill is the current gate.
- Read repo instructions,
SOURCE-INVENTORY.md, and cited source files before asking anything.
- Finding facts is your job, never the user's: explore files, data, and citations directly instead of asking the user for discoverable facts.
- Map the product definition as a design tree: Audience, Problem, Outcome, Promise, Evidence threshold, Constraints, Success test, and Out of scope.
Wang Yong-Fu (福哥) Teaching Craft Integration (wang-yongfu-teaching-craft)
In PRESENTATION-BRIEF.md:
- ASK Objective Model: Explicitly declare 3 dimensions of learning objectives:
- Knowledge (知識/知道): What concepts or frameworks must the audience understand?
- Skill (技巧/得到): What actionable methods or tools will they master?
- Attitude (態度/心態): What emotional shift or mindset change will take place?
- Learning Levels (知道 → 得到 → 做到): Ensure the session does not stop at mere cognitive knowledge ("知道"); design concrete moments where the audience converts insight into practice ("做到").
- Observable Success Criteria: Reject vague slogans ("improve parenting quality"); require measurable, observable end-of-session behaviors (e.g. completing a 3-rule compact card, passing an alignment roleplay).
Frontier Grilling Flow
- Work the tree in rounds. The frontier is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you haven't heard yet.
- Ask the whole frontier in one round: number each question, explain downstream impact, and provide your recommended answer.
- Format every question in a round with the standard grilling card syntax:
❓ **Q1** - **<question title>**: <question body, trade-offs, options>
➡️ <your recommended answer & downstream impact>
---
❓ **Q2** - **<question title>**: <question body, trade-offs, options>
➡️ <your recommended answer & downstream impact>
- Each round the user answers unblocks downstream decisions: recompute the frontier and ask the next round.
- Use
references/autonomous-brief.md for the autonomous fallback when the user is unavailable (headless run) or the remaining product decisions are resolvable from sources — resolve each open field with a defensible value, rationale, and confidence level, and flag low-confidence load-bearing decisions for later human review.
- Let any consequential change to Audience, Problem, Outcome, Promise, Evidence threshold, Constraints, Success test, or Out of scope invalidate downstream gates.
- Confirmation Gate: Do not finalize or advance past the product-grill gate until the user confirms you have reached a shared understanding on the brief.
Write PRESENTATION-BRIEF.md from templates/PRESENTATION-BRIEF.md.
- Update the brief as soon as decisions are settled.
- Keep the brief decision-oriented and concrete.
- Prefer short sentences, explicit tradeoffs, and measurable success tests.
Write only consequential decisions to GRILL-LOG.md from templates/GRILL-LOG.md.
- Append new decisions without deleting or rewriting entries from other grill phases or earlier runs.
- Preserve existing decisions from story or stage grilling.
- Log decisions that materially change evidence, story, prototype, stage, or production work.
- Skip minor wording preferences and reversible drafting details.
- Stop once the brief is coherent and confirmed.
1---2name: presentation-product-grill-23description: Turns a source inventory into a presentation brief by resolving audience, problem, outcome, promise, constraints, and success decisions through round-by-round frontier grilling. Use when the product-grill gate is current for a presentation project or when a router asks for the presentation brief and consequential decision log.4---56# Grill the presentation product78Use when `product-grill` is the current gate.910- Read repo instructions, `SOURCE-INVENTORY.md`, and cited source files before asking anything.11- **Finding facts is your job, never the user's**: explore files, data, and citations directly instead of asking the user for discoverable facts.12- Map the product definition as a **design tree**: Audience, Problem, Outcome, Promise, Evidence threshold, Constraints, Success test, and Out of scope.1314## Wang Yong-Fu (福哥) Teaching Craft Integration (`wang-yongfu-teaching-craft`)1516In `PRESENTATION-BRIEF.md`:17- **ASK Objective Model**: Explicitly declare 3 dimensions of learning objectives:18 - **Knowledge (知識/知道)**: What concepts or frameworks must the audience understand?19 - **Skill (技巧/得到)**: What actionable methods or tools will they master?20 - **Attitude (態度/心態)**: What emotional shift or mindset change will take place?21- **Learning Levels (知道 → 得到 → 做到)**: Ensure the session does not stop at mere cognitive knowledge ("知道"); design concrete moments where the audience converts insight into practice ("做到").22- **Observable Success Criteria**: Reject vague slogans ("improve parenting quality"); require measurable, observable end-of-session behaviors (e.g. completing a 3-rule compact card, passing an alignment roleplay).2324## Frontier Grilling Flow25- Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask *now* without guessing at answers you haven't heard yet.26- Ask the whole frontier in one round: number each question, explain downstream impact, and provide your recommended answer.27- Format every question in a round with the standard grilling card syntax:2829```30❓ **Q1** - **<question title>**: <question body, trade-offs, options>3132➡️ <your recommended answer & downstream impact>3334---3536❓ **Q2** - **<question title>**: <question body, trade-offs, options>3738➡️ <your recommended answer & downstream impact>39```4041- Each round the user answers unblocks downstream decisions: recompute the frontier and ask the next round.42- Use `references/autonomous-brief.md` for the autonomous fallback when the user is unavailable (headless run) or the remaining product decisions are resolvable from sources — resolve each open field with a defensible value, rationale, and confidence level, and flag low-confidence load-bearing decisions for later human review.43- Let any consequential change to Audience, Problem, Outcome, Promise, Evidence threshold, Constraints, Success test, or Out of scope invalidate downstream gates.44- **Confirmation Gate**: Do not finalize or advance past the product-grill gate until the user confirms you have reached a shared understanding on the brief.4546Write `PRESENTATION-BRIEF.md` from `templates/PRESENTATION-BRIEF.md`.4748- Update the brief as soon as decisions are settled.49- Keep the brief decision-oriented and concrete.50- Prefer short sentences, explicit tradeoffs, and measurable success tests.5152Write only consequential decisions to `GRILL-LOG.md` from `templates/GRILL-LOG.md`.5354- Append new decisions without deleting or rewriting entries from other grill phases or earlier runs.55- Preserve existing decisions from story or stage grilling.56- Log decisions that materially change evidence, story, prototype, stage, or production work.57- Skip minor wording preferences and reversible drafting details.58- Stop once the brief is coherent and confirmed.
samulee003