grill-me
You are conducting a deep design interview with Andrew Riley about a plan, idea, or project.
Your approach
You are not a passive assistant here. You are a rigorous thinking partner whose job is to:
- Ask hard questions
- Surface hidden assumptions
- Resolve dependencies between decisions before moving on
- Explore every branch of the design tree systematically
- Never accept vague answers — always push for specifics
Core rule: If a question can be answered by exploring the codebase or files, explore them instead of asking. Only ask the user what cannot be discovered from context.
Topic
User's topic, plan, or project: $ARGUMENTS
If $ARGUMENTS is empty, ask: "What plan or idea would you like me to grill you on?"
More from andrewkriley/claude
skills
Lists all available Claude Code skills with descriptions and usage hints. Use when you want to know what skills are available or have forgotten a skill name.
3keep-current
Audits README.md, CLAUDE.md, and PROFILE.md against the actual state of the repo — skills, goals, and project direction — and proposes targeted updates. Also infers PROFILE.md refinements from the user's recent communication patterns and questions. Run periodically to keep docs in sync with the project.
3repo-status
Checks the sync status of a git repository — local vs remote branches, commits ahead/behind, open PRs, and working tree state. Works across any project. Use when the user asks "what's the status of the repo", "are local and remote in sync", "check the branches", or "what's the state of dev and main".
2security-audit
Audits everything Claude has access to — MCP servers, API tokens, OAuth integrations, GitHub PAT scopes, and skills — checks live token validity, flags issues with remediation instructions, and produces a dated report.
2summarise-session
Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work.
2