krypton-planning
From the author
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.
Install
npx skills add jturntdev/krypton --skill krypton-planning -a claude-code
Installs to .claude/skills/krypton-planning/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 79
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- plan-modeCodeAlive-AI/ai-driven-developmentUse this skill when the user asks to plan, design, scope, estimate, or implement a feature, bug fix, refactor, migration, integration, API change, UI change, or other project modification. Enforces a planning gate before editing code — investigate project context, analyze the task, surface ambiguities, contradictions, risks, dependencies, and blockers, ask focused questions, produce an evidence-based step-by-step plan, and implement only after explicit user approval. Not for trivial one-line edits, pure questions about the codebase, or changes the user has already reviewed and approved for direct implementation.Planning★ 166
- krypton-executionjturntdev/kryptonUse when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence. Use for main-agent execution with explorer, plan-reviewer, reviewer, maintainer, or verifier gates.Legal★ 132
- refactor-plangithub/awesome-copilotCreate a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes.Planning★ 40.4K
- architectOutlineDriven/outline-driven-developmentUse when non-trivial code needs a design, codebase design or architecture needs improving, or one module needs targeted interface narrowing, seams, or testability. Not for diagrams, deploy, or irreversible changes.Planning★ 54
- using-planJanYork/llm-wiki-cliUse when an Agent needs to create, resume, advance, block, revise, complete, or abandon a durable current execution plan in LWC.Planning★ 68
- feature-planningmhattingpete/claude-skills-marketplaceBreak down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.Planning★ 688
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in