Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/krypton-planning
Use when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding. Use especially when wrong ownership, duplicate paths, stale contracts, weak evidence, or unclear cutover would make plausible agent work dangerous.
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 20 more in the full report
12 fixed7 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What specific sections must be included in `EVIDENCE.md` to record target verification artifacts once execution is underway?
| Checked | Without skill | With skill |
|---|---|---|
| Includes a section for Acceptance Evidence. | Missed | Passed |
| Includes a section for Verification commands and outputs. | Passed | Passed |
| Includes a section for Review Notes. | Missed | Passed |
The instructions your model reads when the skill loads.
Krypton Planning turns a request into a goal package that names the outcome, truth owner, contract, cutover, and acceptance evidence before anyone writes code.
Do not treat a task list as a plan. A Krypton plan is ready only when it answers:
What outcome are we serving?
What current behavior is being replaced, redirected, deleted, or demoted?
Who owns the truth?
What contract crosses the boundary?
What is the smallest high-value slice?
What proves the result from the target person's perspective?
What kill criteria stop duplicate paths from living forever?
If ownership, cutover, contract, or evidence is fuzzy, stop and map before planning.
Plan title:
Intent:
Current behavior:
Expected outcome:
Target-perspective output:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Value density:
Evidence gate:
Acceptance evidence:
Evidence lane:
Kill criteria:
Non-goals:
test cases passed, vs 9 / 22 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.