# Planning

> Produce a clear, actionable implementation plan before any code is written, then — once the user approves it — file it as a GitHub issue and hand it to the build pipeline. Use this skill WHENEVER the user asks to plan, scope, design, or \"figure out how to approach\" anything — a new project, a feature, a refactor, a performance push, a bug fix, or a technical investigation. Trigger it even when the user doesn't say the word \"plan\" but is clearly asking how something should be built or fixed (e.g. \"how would we add X\", \"what's the best way to tackle Y\", \"I need to fix this bug\"). Planning is investigation and design only — it never writes or runs implementation code. It gathers context efficiently, proposes an approach, iterates with the user to approval, then records the approved plan as a GitHub issue.

## Facts
- Page: https://tashan.sh/capability/skill-eblouin-development-planning
- tashan id: skill:eblouin-development/planning
- Source: https://github.com/eblouin-development/eblouin-plugins
- Type: skill
- Category: other
- tashan score: 50.0 / 100
- Adoption: 14.0
- Upkeep: 98.0
- Freshness: 95.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- Official: no

## Install

```sh
cp -r planning ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-09 by tashan (https://tashan.sh) from public evidence. Scorer s5.