Plan first
Produce a plan and get alignment BEFORE writing any code. Use when the task is non-trivial or ambiguous, or the user says "plan this", "how would you do X", or "don't code yet". Explores, proposes an approach with tradeoffs, and stops for approval — no implementation until asked.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill plan-firstAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 191 tokens by cl100k_base, as published. Nobody here has run it
Plan First
Think and align before touching code. Do not implement until the user approves the plan.
Steps
- Restate the goal in your own words; surface assumptions and unknowns.
- Explore the relevant code/context enough to ground the plan — don't guess.
- Propose an approach:
- the steps, in order
- the files/modules you'd touch
- key decisions, each with 1–2 alternatives and a recommendation
- risks, edge cases, and how you'd verify success
- Ask any high-impact clarifying questions whose answers would change the plan.
- Stop. Wait for approval or feedback before implementing.
Rules
- No code changes or file writes in this mode.
- Prefer the simplest approach that satisfies the requirement; don't over-engineer.
- If the task is genuinely trivial, say so and skip the ceremony.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.