| name | grill-knowledge |
| description | Interview the user about life events, decisions, or personal context until the facts are clear, then draft a Notion write plan without writing until approved. Use when the user says /grill-knowledge, wants to capture something from life, wants to be grilled before saving knowledge, or discusses personal context that may belong in Notion. |
Grill Knowledge
Quick Start
Interview Giacomo one question at a time, clarify the story or decision, then draft the exact Notion update. Use Notion only for reading context until Giacomo explicitly approves the latest exact draft.
Workflow
-
Establish the topic:
- What happened?
- Why does it matter?
- Is it a task, project, decision, application, relationship, preference, profile fact, or reflection?
-
Inspect Notion only for context:
- Search relevant existing Notion pages/databases when available.
- Use Notion to avoid duplicates and understand where the update might belong.
- Do not rely on committed docs or old snapshots.
-
Grill one question at a time:
- Ask the most important unresolved question.
- Provide your recommended answer or framing when helpful.
- Stop asking when the remaining uncertainty would not change the Notion draft.
- Do not write, update, or create Notion pages during the interview.
-
Produce the final draft:
- Target Notion database/page.
- New page vs update existing page.
- Field/value mapping, using the live Notion fields.
- Page body draft that follows the structure, section names, length, and density already established in the target Notion page and nearby siblings.
- Links or relations to add.
- What is intentionally not being captured.
- Open questions, if any.
-
Ask for confirmation:
- Write only after Giacomo explicitly approves the latest exact draft.
- Approval must come after all discussion, corrections, and follow-up changes. If the chat continues after a draft, treat prior approval as stale and ask again.
- Use a direct approval question such as "Should I apply these exact Notion writes now?"
- If approval is not given, leave the draft in the chat only.
-
Write and verify when approved:
- Apply only the approved latest draft.
- Read back the Notion item.
- Summarize what changed.
Question Style
- Keep it tight: one question at a time.
- Preserve Giacomo's wording when it carries meaning.
- Challenge vague terms when they affect where the knowledge goes.
- Ask before turning subjective models into advice or stronger claims.
Draft Format
## Proposed Notion Capture
Topic: <short label>
Target: <database/page>
Action: <create/update>
Fields:
- <field>: <value>
Body:
<draft content>
Not capturing:
- <item and reason>
Confirmation:
Should I apply these exact Notion writes now?
Rules
- Notion is the source of truth.
- No Notion writes while grilling.
- NEVER write, edit, append, relate, archive, move, rename, or delete anything in Notion before explicit approval of the latest exact draft.
- Treat Notion writes as highly destructive and hard to version. "Looks good", clarifying answers, or pointing out where something belongs are not approval unless Giacomo explicitly says to apply/write/create/update the exact draft.
- If Giacomo replies after a draft with any correction, new fact, target change, or question, update the draft and ask for approval again before writing.
- Do not hallucinate missing facts.
- Follow the structure, length, heading style, and density already established in the target Notion page and nearby sibling pages. When live examples are shorter than your draft, trim to match them.
- If Notion access is unavailable, produce only a draft and say it was not verified against live Notion.