mcpField
P
planning

planning

github.com/langchain-aiAgent workflows30.8k223 installsUpdated today
Repository

About planning

A skill for planning coding tasks before implementation. It guides agents through understanding requirements, exploring the codebase, identifying files, writing actionable TODOs, and assessing risks.

Key features

  1. 01Review task goals and criteria
  2. 02Explore project structure and tests
  3. 03Locate relevant code and files
  4. 04Create structured implementation TODOs
  5. 05Assess risks and edge cases

Use cases

  1. 01Planning a new feature implementation
  2. 02Breaking an issue into executable steps
  3. 03Identifying files affected by a code change
  4. 04Preparing tests and verification steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/langchain-ai/deepagents --skill planning

After installing, type/planningin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported