Skill

plan:guidelines

Provides guidelines for high-quality implementation plans: structure with context/changes/verification/risks, scope matching requests, pre-reads, and rejection analysis.

developer-tools

code-quality

Install

npx claudepluginhub bendrucker/claude --plugin plan

Tool Access

This skill uses the workspace's default tool permissions.

Preview

@references/guidelines.md

SKILL.md

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

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars10

Parent Repo Forks1

Last CommitFeb 8, 2026

Actions

View Source View Plugin View on GitHub View README

Planning Guidelines

@references/guidelines.md

Extended Guidance

Reading Before Planning

Before proposing any changes:

Read the files you intend to modify
Understand the existing patterns and conventions
Identify related code that might be affected
Check for existing tests that cover the area

Plan Structure

A good plan includes:

Context: What problem are we solving? What's the current state?
Changes: Specific files and modifications, with line references
Dependencies: What must happen in order? What can be parallelized?
Verification: How do we confirm success? What tests to run?
Risks: What could go wrong? How do we recover?

Scope Management

Plans should match the request exactly:

If asked to fix a bug, don't refactor surrounding code
If asked to add a feature, don't add "nice to have" extras
If asked to refactor, don't fix unrelated issues you notice
Document out-of-scope observations separately if important

When Plans Get Rejected

Common reasons for plan rejection:

Too vague (no specific file/line references)
Too broad (scope creep beyond the request)
Missing verification steps
Ignoring existing patterns in the codebase
Proposing changes to unread code