Index of every page on this site: llms.txt
All skills
langchain-ai avatar

/planning

@3748a9e
by LangChainlangchain-ai/deepagents31k stars
4,447
Run it yourself

Break down a coding task into a structured implementation plan with clear steps, file identification, and risk assessment.

Use this Skill: https://skilld.dev/gh/langchain-ai/deepagents/planning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈33 tokens for metadata: the name and description. ≈369 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈133 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Planning Skill

Use this skill when starting a new coding task to create a thorough implementation plan.

Steps

1. Understand the Task

  • Read the issue/task description completely
  • Identify the expected outcome and acceptance criteria
  • Note any constraints or requirements mentioned

2. Explore the Codebase

  • Find the repository root and read the project structure
  • Identify the tech stack (language, framework, test runner)
  • Read README, CONTRIBUTING, or similar docs if they exist
  • Find existing tests to understand testing patterns

3. Identify Relevant Files

  • Use grep to find code related to the task
  • Read the most relevant files (entry points, related modules)
  • Identify which files need to be modified vs. created
  • Check for existing patterns you should follow

4. Write the Plan

Use write_todos to create a structured plan:

write_todos([
    "1. <specific change in specific file>",
    "2. <next specific change>",
    "3. Write tests for <feature>",
    "4. Run test suite and fix failures",
    "5. Review all changes"
])

5. Assess Risks

  • Are there breaking changes?
  • Are there edge cases to handle?
  • Does this affect other parts of the codebase?
  • Flag anything uncertain for review

Guidelines

  • Plans should have 3-10 concrete steps
  • Each step should be specific enough to execute without further planning
  • Include test writing and test running as explicit steps
  • End with a review/verification step

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured framework for task planning and code exploration without any identified security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 3748a9e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 hours ago.

Activeupdated 8 months ago

README badge

README badge for langchain-ai/deepagents/planning