grilling

Interviews the user one decision at a time and writes a confirmed implementation plan to .context/plans/.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill grilling-eklyukin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/grilling
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill grilling-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and designs often hide unexamined assumptions that surface only during implementation. This Skill forces every material decision to be made explicitly through a structured one-question-at-a-time interview before any code is written. ## Core Features & Use Cases - Decision-tree interview: Asks exactly one question at a time, each with a recommended answer and its main tradeoff, until no unresolved decisions, assumptions, acceptance criteria, or risks remain. - Evidence-based questioning: Inspects the filesystem, repository, and configured tools directly instead of asking the user for discoverable facts. - Confirmed plan artifact: After explicit user confirmation, writes a structured Markdown plan (context, decisions, scope, acceptance criteria, risks, implementation outline, Jira fields) to .context/plans/YYYY-MM-DD-<slug>.md without touching tracked files. - Use Case: Before refactoring a service architecture, invoke the skill to be grilled on scaling constraints, data migration, and rollback strategy, then receive a dated plan file ready for implementation. ## Quick Start Ask the AI to use the grilling skill to interview you one decision at a time about your planned feature and produce a confirmed implementation plan in .context/plans/.

Frequently Asked Questions about grilling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an AI to challenge my implementation plan before coding?▼

Invoke the grilling skill and state your goal. It interviews you one decision at a time, offering a recommended answer and tradeoff for each question, until all assumptions, scope, and acceptance criteria are settled.

What does the grilling skill produce after the interview?▼

After you explicitly confirm the shared understanding, it writes a structured Markdown plan to .context/plans/YYYY-MM-DD-slug.md covering context, agreed decisions, scope, acceptance criteria, risks, and an implementation outline.

Does the grilling skill modify my code or tracked files?▼

No. It never edits product code, configuration, or tracked files during the interview. It only creates untracked plan files under .context/ and adds .context/ to .git/info/exclude rather than modifying .gitignore.

Can the grilling skill create a Jira issue from the plan?▼

Not automatically. The plan includes Jira placeholder fields, and the skill offers to use the separate jira-worklog skill to link or publish it, but only after a separate preview and your explicit confirmation.

When should I not use a decision-interview workflow?▼

Avoid it for trivial, well-understood tasks where the decision tree has no material branches. The interview adds overhead, so it fits best for ambiguous designs, architectures, or implementations with real tradeoffs.