Planning

Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.

49 stars 21 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lllyys/vreader --skill planning
Manual install
git clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/planning ~/.claude/skills/planning

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Planning Skill

## When to use

Use this skill when the user asks for planning, a roadmap, a spec-to-implementation breakdown, or wants decisions documented.

## Modes

Choose the lightest mode that meets the request.

### `quick-plan`

Use when:
- task is small/medium and non-breaking
- no migrations and no multi-phase rollout

Output:
- 3–8 Work Items (WI-###), each with tests + acceptance

### `full-plan` (default)

Use when:
- migrations/persistence changes
- API/contract changes (public tools, schemas, SDKs)
- multi-phase roadmaps
- performance-sensitive work

Output:
- structured plan sections (see “Plan file template”)

## Process

1. **Clarify outcomes**
   - Restate desired behaviors and constraints.
   - Identify ambiguities and propose defaults if the user doesn’t decide.
   - Capture **constraints & dependencies** (runtime versions, OS, external services, feature flags, required tools).
   - **Capture gaps**: list requirement/behavior gaps or missing decisions revealed here.

2. **Inventory current behavior**
   - Trace entry points → state/store → side effects → persistence.
   - List key files/modules and the invariants they rely on.
   - Note ownership/priority rules (windows, workspaces, files).
   - **Capture gaps**: list where current behavior diverges from the stated outcomes.

3. **Define target rules**
   - Convert outcomes into explicit rules and precedence.
Read the full skill on GitHub

Details

Skill name
planning
Repository
lllyys/vreader
Path
.claude/skills/planning/SKILL.md
Repo updated
6 August 2026

FAQ

What does the Planning skill do?

Create comprehensive implementation plans and write them to plan files. Use when the user asks for a plan, comprehensive plan, systematic workflow design, or wants decisions documented in a plan file.

How do I install the Planning skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill planning. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Planning popular?

It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.

Related skills

AI Coding Agents

49

lllyys/vreader

Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.

AI, LLMs & Agents21

Dispatch

49

lllyys/vreader

Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.

Git & Code Review21

Feature Workflow

49

lllyys/vreader

Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud

Productivity & Notes21

Polymorph

113

Hmbown/Wizards-of-the-Ghosts

This spell is about representation change, not: - Naming changes (same structure, different identifiers) - Execution changes (same code, different runtime) - Architecture changes (new system design) - Duplication (same thing, different place) The key test: Can you point to a source artifact and a target artifact where the same information is expressed in structurally different ways? If yes → Polymorph.

Productivity & Notes11

Planar Binding

113

Hmbown/Wizards-of-the-Ghosts

Use this spell when you need to summon a powerful external entity - a third-party API, a cloud service, another agent - and lock it into serving your workflow under explicit terms.

Productivity & Notes11

Prestidigitation

113

Hmbown/Wizards-of-the-Ghosts

Prestidigitation transforms. It does not fix, build, scaffold, migrate, or actuate. If the user says "make this look better" or "convert this to that format" — use prestidigitation. If the user says "make this work" or "set this up" or "build this system" — use something else.

Productivity & Notes11

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.