Plan

aiskillstore/plan

Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.

This is a copy. The original lives at comeonoliver/plan.

3k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

404

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/aiskillstore/marketplace --skill plan

What comes with it

9 822 bytes besides the instruction

references/principles.md

skill-report.json

The instruction itself

4 sections, as written by the author

Task Planning

Workflow

Gather Information: Explore codebase and list dependencies.
Draft Plan:
Objective: Goal of the task.
Approach: High-level strategy.
Steps: Sequential actions.
Verification: How to prove it works.
Clarify: Include at least 3 clarifying questions with proposed answers.
Approve: Wait for user "go ahead" (empty response = approval).
Implement: Execute only after approval.

Principles

Zero-Impact: Do not modify files during planning.
Iterative: Refine based on feedback.
Concise: Keep plans readable and progress tracked via TODOs.

References

Planning Principles

How to use it

Copy the folder

Take aiskillstore/plan from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.