Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/plan-interrogate
Stress-test a plan by walking its decision tree one question at a time.
Passed 16 of 21 test cases with the skill, and 11 of 21 without it.
and 8 more in the full report
7 fixed10 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here is a draft proposal to add an asynchronous background job queue for processing large file exports. Please interrogate this proposal before we jump into development. Identify all dependent choices and work through open questions sequentially—ask me just one question at a time paired with your proposed answer and short justification. Check existing project docs and commits so you skip questions already resolved by the codebase. Finally, provide the complete ledger of finalized choices that I can copy straight into the design document, strictly without conversational summaries.
| Checked | Without skill | With skill |
|---|---|---|
| The response restates the background job queue plan in one paragraph. | Missed | Passed |
| The response requests confirmation from the user on the restatement before posing questions or interrogating decisions. | Missed | Passed |
The instructions your model reads when the skill loads.
Drive a plan from sketch to commitment by resolving every open decision before any code is written.
user (the user answered), inferred (the
codebase or an existing constraint settled it).inferred: <path>.Decision - Choice - Source (user | inferred: <path>).The interrogation produces three artifacts, not just answers. Offer to write each; do not force it.
test cases passed, vs 11 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.