// Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Write or update Shotomatic landing-page blog posts in `shotomatic-landing-page/src/content/blog/` with correct frontmatter, internal intent metadata, supporting links, stock hero images, and publish-readiness QA. Use when asked to draft, revise, or QA Shotomatic blog posts.
Commit all local changes as a single Conventional Commit by using the `commit-all` skill, then push commits to the remote tracking branch. Use when the user explicitly asks to commit everything and push.
Commit all local changes in the current repository, including tracked, untracked, and deletions, as a single Conventional Commit. Use only when the user explicitly wants all changes committed together.
Finish local Git work by first using the `commit` skill to split and create Conventional Commits, then push the resulting commits to the remote tracking branch. Use when the user asks to commit and push changes.
Split only the changes you made into clear, reviewable Git commits grouped by behavior or concern. Use when Codex must avoid pre-existing local edits, stage partial hunks safely, and create Conventional Commits messages for your changes.
Scoped parallel refactor for files Codex changed in the current task. Use when the user says "$refactor" after asking for implementation. Build an explicit allowed file list from your own edits only, then improve code quality and low-risk efficiency in that list while enforcing AGENTS.md rules.
| name | grill-me |
| description | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree resolving dependencies between decisions one by one.
Default to 25 total questions unless the user specifies a different question count. If the user gives a count, honor it.
Make the questions strong enough to cover the topic within the allowed count. Prioritize the highest-leverage unknowns first, combine low-value branches when needed, and scale breadth versus depth to fit the budget.
If a question can be answered by exploring the codebase, explore the codebase instead.
For each question, provide your recommended answer.
Ask exactly one question at a time.
