From odoo-skills
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against their project's language and documented decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/odoo-skills:grill-with-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interview the user relentlessly about every aspect of this plan until there is shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.
Interview the user relentlessly about every aspect of this plan until there is shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.
Ask exactly one question at a time, waiting for feedback before continuing.
If a question can be answered by exploring the codebase, inspect the codebase instead of asking.
During codebase exploration, also look for existing documentation:
/
├── CONTEXT.md
├── docs/
│ └── adr/
└── src/
If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives.
Create files lazily. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
When the user uses a term that conflicts with existing language in CONTEXT.md, call it out immediately.
When the user uses vague or overloaded terms, propose a precise canonical term.
When domain relationships are being discussed, stress-test them with specific scenarios that probe edge cases and force precise boundaries between concepts.
When the user states how something works, check whether the code agrees. If you find a contradiction, surface it.
When a term is resolved, update CONTEXT.md immediately. Use CONTEXT-FORMAT.md.
Do not couple CONTEXT.md to implementation details. Only include terms that are meaningful to domain experts.
Only offer to create an ADR when all three are true:
If any condition is missing, skip the ADR. Use ADR-FORMAT.md.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub mart337i/odoo-skills