Interrogate plans with forcing questions

Stress-test plans and designs by asking forcing questions sequentially one branch at a time

When validating a plan or design requires relentless question-driven stress-testing rather than passive review.

• · plan, design, or architecture to stress-test
• · decision tree (implicit or explicit)

• · series of forcing questions in sequential order
• · recommended answers (where codebase provides evidence)
• · decision log with answers

• · 3 stdlib Python tools (decision-tree extractor, question generator, session-state tracker)
• · 3 reference docs: forcing-question patterns + decision-tree completeness + when to stop grilling
• · cs-grill-master persona agent
• · /cs:grill-me slash command
• · codebase explorer (resolve answers where possible)

• · plan is articulated enough to ask questions about
• · user willing to answer one question at a time

• · Questions diverge into tangents, user loses focus
• · Recommended answers based on shallow codebase grep miss domain context
• · Grill stops too early or continues after decision is made

• · 3 stdlib Python tools (tree extractor, question generator, session tracker)
• · 3 deep references (forcing-question patterns + tree completeness + stopping rules)
• · cs-grill-master persona + /cs:grill-me command
• · Derived from Matt Pocock MIT grill-me skill (interview discipline preserved)
• · Codebase explorer resolves answers where evidence exists