Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →magebyte-zero/need-explorer
Clarify intent, scope, constraints, and success criteria before artifact creation.
Passed 7 of 15 test cases with the skill, and 8 of 15 without it.
and 4 more in the full report
5 fixed5 passed either way6 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
The state command for DP-1 has just been recorded successfully for the change directory `changes/stripe-webhooks`. What is the immediate next step in the process?
| Checked | Without skill | With skill |
|---|---|---|
| Hands off the task to spec-writer. | Missed | Passed |
The instructions your model reads when the skill loads.
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Turn a rough idea into a stable change definition before writing artifacts.
Agree on: problem, scope, non-goals, success criteria, whether to split before specification.
Before asking questions, understand what exists and what constraints are in place.
Ask a single clear question, wait for the answer, digest, then ask the next. Never ask 3+ questions at once. Each answer informs the next question.
Present 2-3 options when reasonable answers are finite. This reduces cognitive load and surfaces unconsidered choices.
For each approach: what it is, upside, downside, best-for. Then recommend one and explain why. Never present a single path — always name at least one alternative.
Restate what you heard: "Here's what I'm hearing: [problem, scope, non-goals, success criteria]. Does this match?" Incorporate corrections and re-validate.
After user confirms the summary:
SSF state set <change-dir> dp_1_result "confirmed: <one-line summary>"
SSF state set <change-dir> dp_1_timestamp now
test cases passed, vs 8 / 15 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.