What problem does it solve? Designs and plans often contain unexamined assumptions about inputs, timezones, DST behavior, and locale handling that surface as bugs later. This Skill stress-tests a plan through structured questioning while capturing every settled decision as written documentation. ## Core Features & Use Cases - Assumption Probing: Asks one question at a time about inputs, sentinels, plain vs zoned values, DST gaps, non-existent days, and locale behavior, forcing concrete input-to-output examples. - Conflict Detection: Checks each answer against decisions of record in AGENTS.md and coding-standards calendar/zone semantics, flagging contradictions instead of silently accepting them. - Decision Recording: Writes settled decisions to the story's context/domination/issues/<ID>.md file or the relevant project-wide context file, keeping entries short with decision, reason, and source. - Use Case: Before implementing a new date arithmetic feature in a Temporal-based library, run this interview to pin down DST disambiguation behavior and record the ruling where future agents will find it. ## Quick Start Ask the assistant to grill you on your current design or plan and document the decisions as you answer.