New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Krypton Planning

by jturntdev in jturntdev/krypton

A skill your agent uses when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding.

MITAuto-check passedAgent Workflows

Install Krypton Planning

skills CLI
$ npx skills add jturntdev/krypton --skill krypton-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jturntdev/krypton krypton-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jturntdev/krypton.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/krypton-planning .claude/skills/krypton-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
krypton-planning
GitHub stars
132
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
263 words
Files
3
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding.

  • Works in 2 steps: Write the outcome contract → Map the architecture slice before tasks
  • A user has a feature request
  • SKILL.md covers Core Rule, Workflow, GOAL.md Shape and EVIDENCE.md Shape
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Krypton Planning is an agent skill from jturntdev/krypton. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `agents/openai.yaml` and `plan-reviewer-prompt.md`).

It sits in Agent Workflows, covering Planning. It works with GitHub Actions. The repository describes itself as: Goal-based planning and proof gate for AI coding agents. The licence is MIT.

When your agent uses it

  • A user has a feature request
  • Architecture change
  • Product goal and needs an implementation plan before coding

Example prompts

  • “/krypton-planning”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Write the outcome contract
  2. Map the architecture slice before tasks

What it can do on your machine

Read from SKILL.md and the folder at commit 0b95d97. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Krypton Planning loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 263 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jturntdev/krypton at commit 0b95d97, republished under its MIT licence (© jturntdev). 263 words, ~1,060 tokens.

Download SKILL.mdSave it as .claude/skills/krypton-planning/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
krypton-planning
description
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.

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:
  1. 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 of rediscovering the same slice.

  1. Save a goal package unless the user gives another location:
text
docs/goals/<goal-slug>/PLAN.md
docs/goals/<goal-slug>/GOAL.md
docs/goals/<goal-slug>/EVIDENCE.md

PLAN.md contains the full plan. GOAL.md is a short execution prompt that points to the plan instead of copying it. EVIDENCE.md starts empty and is filled during execution with the real proof captured from the target perspective.

  1. Start PLAN.md with this header shape:
markdown
# [Outcome Title] Implementation Plan

**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:** ...
**Architecture Slice:** ...
**Plan Review Gate:** Requires PRE review before execution.

  1. Break work into small tasks. Each task names exact files, allowed scope, expected output, verification command, acceptance evidence, and whether it can run in parallel.

  2. Run a PRE plan review when possible. Use plan-reviewer-prompt.md as the individual prompt template. Do not execute until blocker findings are fixed or explicitly accepted by the user.

GOAL.md Shape

Use this compact handoff. This is the /goal prompt or next-session prompt the operator should paste into Codex or Claude:

markdown
# Goal: [Outcome Title]

Use Krypton Execution to execute `docs/goals/<goal-slug>/PLAN.md`.

Core rules:
- Treat PLAN.md as the source plan.
- Preserve intent, ownership, contract, cutover, evidence, and kill criteria.
- Do not add a new dominant path without deleting, redirecting, demoting, or shimming the displaced path.
- Capture acceptance evidence from the target perspective and record it in EVIDENCE.md.
- Say "implemented but unproven" if that evidence cannot be captured.

EVIDENCE.md Shape

Create this file with the goal package and update it during execution:

markdown
# [Outcome Title] Evidence

## Acceptance Evidence

Record the real artifact that proves the outcome from the target perspective.

## Verification

Record the focused check that passed, including the command and relevant output.

## Review Notes

Record reviewer, maintainer, or verifier findings that changed the result.

© jturntdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/krypton-planning of jturntdev/krypton.

  • SKILL.md
  • agents/openai.yaml
  • plan-reviewer-prompt.md

Open the folder on GitHubat commit 0b95d97

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jturntdev/krypton, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Krypton Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Krypton Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Krypton Planning this skilljturntdev/krypton1321 repos~1.1kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec71k1 repos~4.5kAutomated safety check: PassMIT
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Improvefossasia/eventyay-interpretation1.6k10 repos~3.7kAutomated safety check: WarnMIT
Implementation Plan Creatortailcallhq/forgecode7.6k1 repos~1.1kAutomated safety check: PassApache-2.0
Plan Previewu-ichi/reviewable-html-workbench2981 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    71k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed

  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed

  • Improve

    fossasia/eventyay-interpretation

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.

    1.6k GitHub starsUsed in 10 repos~3.7k tokens
    Agent WorkflowsAuto-check: warnings

  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Agent WorkflowsAuto-check passed

  • Plan Preview

    u-ichi/reviewable-html-workbench

    Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check passed

  • PRP Loop: Autonomous Pipeline

    Wirasm/prp

    Runs a detached, resumable loop that plans, implements, opens a PR, reviews and fixes a feature across headless CLI sessions until the review is clean.

    2.3k GitHub stars~863 tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

More from jturntdev/krypton

  • Krypton Execution

    jturntdev/krypton

    A skill your agent uses when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence.

    132 GitHub starsUsed in 1 repo~841 tokens
    Auto-check passed

  • Krypton Vps Codex App

    jturntdev/krypton

    Set up, harden, audit, or explain a Linux VPS as a Codex App SSH host for Krypton-style agent workflows.

    132 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check: warnings

Works with

Categories

Questions about Krypton Planning

What does Krypton Planning do?

A skill your agent uses when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding. Krypton Planning is an agent skill from jturntdev/krypton. Use when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding.

When should I use Krypton Planning?

Krypton Planning fits situations like: A user has a feature request; architecture change; product goal and needs an implementation plan before coding.

How do I install Krypton Planning in Claude Code?

Run `npx skills add jturntdev/krypton --skill krypton-planning -a claude-code`. Or copy the skill folder (skills/krypton-planning in jturntdev/krypton) into .claude/skills/krypton-planning in your project. Claude Code loads it when a task matches its description.

How do I install Krypton Planning in Codex?

Run `npx skills add jturntdev/krypton --skill krypton-planning -a codex`. Or copy the skill folder (skills/krypton-planning in jturntdev/krypton) into .agents/skills/krypton-planning in your project. Codex loads it when a task matches its description.

Can I use Krypton Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jturntdev/krypton --skill krypton-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/krypton-planning, .gemini/skills/krypton-planning, .github/skills/krypton-planning and .opencode/skills/krypton-planning in your project.

What does Krypton Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Krypton Planning is instructions for the agent only.

Does Krypton Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Krypton Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Krypton Planning use?

Krypton Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Krypton Planning use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Krypton Planning?

Skills that share tags, products or a category with Krypton Planning: OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Paseo Committee (getpaseo/paseo, 20k stars), Improve (fossasia/eventyay-interpretation, 1.6k stars) and Implementation Plan Creator (tailcallhq/forgecode, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Krypton Planning?

jturntdev (a GitHub user) maintains it in jturntdev/krypton, which has 132 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on July 24, 2026.

Source: jturntdev/krypton on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.