plan

Develop structured implementation plans for code changes through codebase exploration and critical review.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/metalspawn/claude-ops --skill plan-metalspawn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/metalspawn/claude-ops/tree/main/skills/plan
Command: npx skills add https://github.com/metalspawn/claude-ops --skill plan-metalspawn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of planning complex code changes by providing a structured approach to understanding the codebase, clarifying requirements, and creating a robust implementation plan.

Core Features & Use Cases

  • Codebase Exploration: Gathers context about affected files, dependencies, and existing patterns.
  • Requirement Clarification: Identifies and helps resolve ambiguities in task requirements before planning begins.
  • Structured Planning: Generates a detailed plan with steps, verification criteria, and risk assessments.
  • Critical Review: Incorporates feedback from a dedicated reviewer to identify flaws and gaps.
  • Use Case: Planning a new feature that involves modifying multiple services and database schemas.

Quick Start

Use the plan skill to develop a structured implementation plan for adding user authentication.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan for complex multi-file code changes?

To create an implementation plan for multi-file code changes, you need structured codebase exploration, requirement clarification, and critical review to map out steps, verification criteria, and risk assessments before coding begins.

What is the best way to plan new software features involving architectural decisions?

Planning new software features with architectural decisions requires resolving ambiguous requirements first, then generating a detailed plan with steps and risk assessments validated through a dedicated critical review process.

How do I map out code dependencies before modifying existing software patterns?

Mapping out code dependencies before modifying existing software patterns requires codebase exploration to gather context about affected files, dependencies, and current architectural patterns to ensure a validated plan.

When should I use a structured planning process for software development tasks?

You should use a structured planning process for software development tasks when facing non-trivial work, such as multi-file changes, architectural decisions, new features, or ambiguous requirements that need clarification before implementation.

Can I validate my implementation plan to identify flaws and gaps before coding?

You can validate an implementation plan to identify flaws and gaps by incorporating feedback from a dedicated reviewer agent, ensuring the plan is comprehensive and critically assessed before development starts.