Skill

Planning

Use when explicitly instructed to create an plan (feature, bug fix, or refactor). Not for automatic use—only when directly requested.

From ls

Install

Run in your terminal

npx claudepluginhub landonschropp/agent-toolkit --plugin ls

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGlobGrepEnterPlanModeSkill

Supporting Assets

View in Repository

assets/bug-fix.md.liquid

assets/feature.md.liquid

assets/refactor.md.liquid

scripts/create-feature-branch.sh

scripts/generate-plan-template.ts

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Stars1

Forks0

Last CommitFeb 11, 2026

Actions

View Source View Plugin View on GitHub View README

Workflow

If the scope of the plan is not clear from the arguments or previous context, ask the user: "Please describe the plan or provide a Linear issue ID, Linear issue URL, or Sentry issue URL (for bug-fix)." If the user responds with a Linear issue, fetch its details using the Linear MCP server. If the user provides a Sentry issue URL (bug-fix only), store it for use in the plan template.

Determine the feature branch. If the user has provided a Linear issue, the branch specified in the issue will be the feature branch. If the current branch is the default branch (main/master), ask the user: "What feature branch would you like to use?" Otherwise, ask the user: "Would you like to use {current_branch} as the feature branch?"

If the current branch is the feature branch, move on to step 4. Otherwise, ask the user: "Would you like to use {current_branch} as the base branch?". Then call scripts/create-feature-branch.sh with the feature branch and the base branch.

Create a plan file using scripts/generate-plan-template.ts. This will generate a pre-populated plan for you to fill out. Read the resulting file.

Fill out each section of the plan one at a time. Follow the instructions in the template for each section.

CRITICAL: DO NOT edit a Claude plan file in .claude/plans. Only edit the plan template file that was generated.
If this is a new branch with no existing work, remove the Context section entirely. If resuming work on an existing branch, summarize what has already been done by running git log and git diff to see commits and changes.
For the Scope and Plan sections, research the plan and its implementation. Ask the user clarifying questions if needed to understand the task and what's required to implement it.
Do not modify sections that contain the comment "Copy this section exactly as written, without modification", but do delete the comment.

ultrathink

Planning

Workflow

If the scope of the plan is not clear from the arguments or previous context, ask the user: "Please describe the plan or provide a Linear issue ID, Linear issue URL, or Sentry issue URL (for bug-fix)." If the user responds with a Linear issue, fetch its details using the Linear MCP server. If the user provides a Sentry issue URL (bug-fix only), store it for use in the plan template.
Determine the feature branch. If the user has provided a Linear issue, the branch specified in the issue will be the feature branch. If the current branch is the default branch (main/master), ask the user: "What feature branch would you like to use?" Otherwise, ask the user: "Would you like to use {current_branch} as the feature branch?"
If the current branch is the feature branch, move on to step 4. Otherwise, ask the user: "Would you like to use {current_branch} as the base branch?". Then call scripts/create-feature-branch.sh with the feature branch and the base branch.
Create a plan file using scripts/generate-plan-template.ts. This will generate a pre-populated plan for you to fill out. Read the resulting file.
Fill out each section of the plan one at a time. Follow the instructions in the template for each section.
- CRITICAL: DO NOT edit a Claude plan file in .claude/plans. Only edit the plan template file that was generated.
- If this is a new branch with no existing work, remove the Context section entirely. If resuming work on an existing branch, summarize what has already been done by running git log and git diff to see commits and changes.
- For the Scope and Plan sections, research the plan and its implementation. Ask the user clarifying questions if needed to understand the task and what's required to implement it.
- Do not modify sections that contain the comment "Copy this section exactly as written, without modification", but do delete the comment.

ultrathink