interrogate-me

Stress-test plans and designs against local code and documentation.

1|Updated May 7, 2026

Search Tags:#assumptions #code-review #guardrails #design-analysis #local-context #interrogate

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill interrogate-me

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: interrogate-me
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/interrogate-me
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill interrogate-me

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stress-test before committing by challenging plans, designs, code changes, or domain terms against local code and docs, surfacing explicit assumptions and risks.

Core Features & Use Cases

One-question-at-a-time: prompts minimal, focused inquiries to scope decisions.
Local-context awareness: uses nearby files like CONTEXT.md, ADRs, and tests to validate claims.
Safeguards and traceability: records assumptions, trade-offs, and decisions for later review.

Quick Start

Use interrogate-me to initiate a focused, one-shot interrogation against the current project context.

Frequently Asked Questions about interrogate-me

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

FAQPage Schema

How do I stress-test code changes against local project context before committing?▼

Stress-test code changes by applying one-question-at-a-time interrogation against local files like CONTEXT.md and ADRs. This surfaces explicit assumptions, tradeoffs, and risks to validate safe decisions.

What is the best way to surface hidden assumptions in software design analysis?▼

Assumptions are surfaced through focused interrogation of plans and specs against local documentation. The process enforces explicit assumption recording and verifiable success criteria for later review.

Can I use one-pass interrogation to validate specs and configurations against existing tests?▼

Yes, you can validate specs and configurations by challenging them against nearby tests and docs. Local-context awareness checks claims while enforcing surgical edits and traceable decisions.

How do I apply guardrails to ensure safe code decisions during design reviews?▼

Guardrails are applied through one-question-at-a-time prompts that scope decisions surgically. This focused interaction model records trade-offs and enforces verifiable success criteria.

When do I need to interrogate domain terms against local code and documentation?▼

Interrogate domain terms when you need to validate plans, designs, or configurations before committing. The process checks terms against local code and docs to expose hidden risks and assumptions.

Does one-shot interrogation work for reviewing ADRs and architectural plans?▼

Yes, one-shot interrogation reviews ADRs and plans by challenging them against local context. It records explicit assumptions and trade-offs, ensuring architectural decisions are traceable and validated.