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.
npx skills add jturntdev/krypton --skill krypton-planning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Krypton Planning Krypton Planning turns a request into a goal package 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: Evidence gate: 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: Displac
- Core Rule
- Workflow
- GOAL.md Shape
- EVIDENCE.md Shape
What does the krypton-planning skill do?
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.
How do I install it?
Run `npx skills add jturntdev/krypton --skill krypton-planning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jturntdev/krypton, a repository with 124 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.