← Cino ToolkitCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Cino Toolkit
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "grill-me",
"description": "Interview the user relentlessly about a plan or design until reaching shared understanding and resolving each branch of the decision tree. Use when the user asks to be grilled, challenged, stress-tested, have holes poked in a plan, or be walked through design choices before code or documentation is produced. Do not use when the design is settled and the user only wants execution or a finished artifact.",
"included_files": [
{
"relative_path": "LICENSE",
"size_in_bytes": 1105
},
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 272
},
{
"relative_path": "assets/icon.svg",
"size_in_bytes": 2134
}
],
"skill_md_contents": "---\nname: grill-me\ndescription: Interview the user relentlessly about a plan or design until reaching shared understanding and resolving each branch of the decision tree. Use when the user asks to be grilled, challenged, stress-tested, have holes poked in a plan, or be walked through design choices before code or documentation is produced. Do not use when the design is settled and the user only wants execution or a finished artifact.\n---\n\n# Grill me\n\nInterview the user about every material part of the plan until both sides share the same understanding.\n\nAsk one question at a time. Walk through the decision tree in dependency order so later questions build on settled answers.\n\nFor each question:\n\n1. Explain what decision the question controls.\n2. Give a recommended answer and a short reason.\n3. Ask the user for their answer.\n4. Record the decision before moving to the next dependent question.\n\nIf the codebase, supplied files or connected sources can answer a question, inspect them instead of asking the user.\n\nChallenge contradictions, missing constraints and risky assumptions directly. Do not produce code or final documentation until the important branches are resolved, unless the user asks to stop the interview and proceed.\n"
}SHA-256: 129263a3daf50261b11e2d04228fec5b6eb7b500555f2a43e5b331945cb91747