planning

planning is a skill for Claude Code from konglong87/methodology-skills. It costs 29 tokens per session (9,357 once invoked), scanned A, original, MIT.

A method for turning a defined request into an implementation plan. It breaks the work into independent parts, checks dependencies and risks, and reviews the plan before execution.

In plain words
What is it for?
Use it to plan multi-step development work after the requirements and solution are clear, including deciding what must happen first and how each part will be delivered.
Why use it?
It makes complex work easier to start and helps expose missing requirements, ordering problems, and likely failure points before changes are made.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to plan multi-step development work after the requirements and solution are clear, including deciding what must happen first and how each part will be delivered.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/konglong87/methodology-skills/planning
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add konglong87/methodology-skills --skill planning
Clone the repo
git clone --depth 1 https://github.com/konglong87/methodology-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/konglong87/methodology-skills/planning/github.svg)](https://agentmods.dev/skills/konglong87/methodology-skills/planning)
Your own site
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/planning"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/planning"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.09357
Opus 5 $0.00015 $0.04679
Sonnet 5 $0.00006 $0.01871
Haiku 4.5 $0.00003 $0.00936

Measured 9d ago against content hash b3d69bf96855, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/planning/SKILL.md · 1,388 lines

How it starts

The opening of the file, as written. The whole thing — 1,388 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Planning - 实施规划与步骤分解

前置协议

强制触发规则

触发时机:prompt-enhancer 完成需求细化后(强制)

触发条件

  • ✅ 已有明确的需求和方案
  • ✅ 需要实施规划和步骤分解
  • ✅ 复杂任务(需要多个步骤完成)

例外情况

  • 简单任务(单步即可完成)
  • 用户明确表示"直接开始"

依赖检查

前置依赖:prompt-enhancer

检查内容

  • 检查工件文件:memory/artifacts/prompt-enhancer/
  • 确认已有明确的需求和选定方案
  • 如果无前置工件,需先执行 prompt-enhancer

与 goal-oriented 的协作

触发来源:goal-oriented skill 强制调用

触发流程:

goal-oriented 创建目标
    ↓
调用 prompt-enhancer(需求细化)
    ↓
生成需求方案工件
    ↓
调用 planning(实施规划)
    ↓
读取需求方案工件 → 生成实施计划 → plan-review
    ↓
生成实施计划工件
    ↓
传递给 execution 阶段
    ↓
任务完成后 → experience-manager 经验沉淀

工件接收:

  • goal-oriented 会写入工件到 memory/artifacts/prompt-enhancer/
  • planning 自动检测并读取最新工件

工件传递机制

输入工件(来自 prompt-enhancer)

工件路径: memory/artifacts/prompt-enhancer/result-{timestamp}.json

工件格式:

{
  "skill": "prompt-enhancer",
  "version": "2.0.0",
  "requirement": {
    "original": "用户原始需求",
    "refined": {
      "type": "功能开发|重构|优化",
      "core_features": ["功能1", "功能2"],
      "target_users": "目标用户",
      "platform": "平台",
      "tech_stack": ["技术1", "技术2"],
      "success_criteria": ["标准1", "标准2"],
      "timeline": "时间线"
    }
  },
  "solution": {
    "selected": "选定方案",
    "reasons": ["理由1", "理由2"],
    "alternatives": [
      {
        "name": "备选方案1",
        "pros": ["优势"],
        "cons": ["劣势"]
      }
    ]
  }
}

读取方式:

# 自动检测最新的 prompt-enhancer 工件
PROMPT_ENHANCER_ARTIFACT=$(ls -t memory/artifacts/prompt-enhancer/*.json | grep -v latest.json | head -1)

if [ -n "$PROMPT_ENHANCER_ARTIFACT" ]; then
  echo "✅ Found prompt-enhancer artifact: $PROMPT_ENHANCER_ARTIFACT"
  # Read artifact content using Read tool
else
  echo "❌ No prompt-enhancer artifact found"
  echo "⚠️ Must execute prompt-enhancer before planning"
fi

输出工件(传递给后续技能)

工件路径: memory/artifacts/planning/result-{timestamp}.json

工件格式: 见 "步骤8:生成工件"

传递机制:

  • 创建工件文件
  • 创建 latest.json 符号链接
  • 后续技能可自动检测 latest.json

Read the full file on GitHub · 1,388 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 1,388 lines · 29 tokens per session scan A b3d69bf96855

Subscribe to this mod's changes

planning is a skill published in the GitHub repository konglong87/methodology-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 9,357 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

importing-a-codebase

Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).

JetBrains/thinkrail · 69 tokens

starting-a-new-project

Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.

JetBrains/thinkrail · 61 tokens

todos

This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…

JetBrains/thinkrail · 127 tokens

writing-workflow-skills

Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

JetBrains/thinkrail · 60 tokens

brainstorming

Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.

JetBrains/thinkrail · 65 tokens

reviewing-changes

Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.

JetBrains/thinkrail · 59 tokens