krypton-planninglisted
Install: claude install-skill jturntdev/krypton
# Krypton Planning
Krypton Planning turns a request into an implementation plan that names the outcome, truth owner, contract, cutover, and acceptance evidence before anyone writes code.
## Core Rule
Do not treat a task list as a plan. A Krypton plan is ready only when it answers:
```text
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.
## Workflow
1. Write the outcome contract:
```text
Plan title:
Intent:
Current behavior:
Expected outcome:
Target-perspective output:
Truth owner:
Contract boundary:
Cutover:
Displaced path:
Value density:
Acceptance evidence:
Evidence lane:
Kill criteria:
Non-goals:
Risk if wrong:
```
2. Map the architecture slice before tasks:
```text
Files to create:
Files to modify:
Files to avoid:
Source of truth:
Read path:
Write path:
Contract boundary:
Integration points:
Migration/cutover:
Displaced path:
Acceptance evidence gate:
```
For broad or unclear repositories, dispatch a read-only explorer if the harness supports agents. Ask one bounded question, such as "map the source of truth, read/write path, unsafe files, and evidence gate." The execution session should use this map instead