skills.rest
jcdendrite
jcdendriteCOMMUNITY
Explore all skills by this author →
GitHub

plan-it

Create structured implementation plans for multi-file work with review handoff.

4|1|Updated Mar 11, 2026
Search Tags:#planning#architecture#verification#git branching#codebase discovery#review handoff#multi-file change
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill plan-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-it
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/plan-it
Command: npx skills add https://github.com/jcdendrite/claude-config --skill plan-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns ambiguous requests into a structured, cross-file implementation plan so execution can proceed with fewer surprises and clearer acceptance criteria.

Core Features & Use Cases

  • Plan scaffolding with correct branching behavior: Creates or revises the harnessed plan file and manages branch planning versus plan-mode resume.
  • Evidence-driven codebase discovery: Uses grep/call-site population checks and subagent exploration to ground architectural decisions in actual patterns.
  • Guardrailed handoff to review: Surfaces clarifying questions before design, then hands the plan off to /plan-review for validation.
  • Optional project-specific layering: Loads any matching project rule layer to enforce repo conventions for this skill.

Quick Start

Ask for a plan by saying: "Create a plan to implement user authentication with GitHub OAuth, including which files to change and how to verify it end-to-end."

Frequently Asked Questions about plan-it

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

FAQPage Schema
How do I create an implementation plan for a multi-file codebase change?▼

An implementation plan for multi-file changes is generated by grounding architectural decisions in evidence-backed codebase discovery, structuring branching paths, and defining verification criteria before handing off to review.

What is the best way to plan cross-repository feature development?▼

Planning cross-repository work requires explicit clarification questions, evidence-backed discovery via grep and subagents, and a structured architecture with rationale, culminating in a review handoff to validate the cross-domain changes.

Do I need an implementation plan for single-file code tweaks?▼

An implementation plan is not needed for single-file tweaks. This Skill explicitly avoids planning when an existing plan exists or single-file tweaks make structured multi-file planning unnecessary.

How does codebase discovery work when planning architecture changes?▼

Codebase discovery works by using grep, call-site population checks, and subagent exploration to ground architectural decisions in actual codebase patterns, ensuring the implementation plan is evidence-driven before review handoff.

Can I enforce repository conventions during the planning process?▼

Yes, you can enforce repository conventions during the planning process through optional project-specific layering, which loads matching project rule layers to apply repo conventions directly to the implementation plan.

How do I hand off a development plan for review validation?▼

To hand off a development plan for review validation, the Skill produces a final /plan-review handoff with optional ExitPlanMode, ensuring the multi-file architecture is verified and ready for execution.

Related Skills

Explore More Software Engineering Skills→
islee23520islee23520
5

ulw-plan

Transform ambiguous engineering requests into decision-complete work plans.

Community
Advanced
sorafujitanisorafujitani
1

plan:dry-coding

Plan code implementations with structured steps and file templates.

Community
Advanced
faizanarshadfaizanarshad

rubberduck-codebase-atlas-pro

Compile a Codebase Atlas of repository architecture, entry points, and data flow.

Community
Advanced
robkamrobkam
12

developer-implementation

Implement approved ytnova tasks in C with minimal coherent edits.

Community
Advanced