Plan a feature before Claude writes code
For anyone building with Claude Code who has watched it charge off in the wrong direction: get a one-page plan first, approve it, then build in small checked steps. Claude reads the relevant code, writes the goal, what done looks like, the files to touch, numbered steps each with a check, and the risks and questions, then stops for your yes. It builds one step at a time, runs typecheck and tests after each, ticks the plan, and tells you what changed from it.
- Activity
- New: be the first to try it
Will this work for me?
- Effort
- Needs about 10 minutes of setupOur guess from what the kit says it needs.
- Works in
- Claude Code, claude.ai and the desktop app
- You need
Excel account: setup steps
- What it is
- This kit works with your own Excel account.
- Where to get it
- Sign in to Excel, or make a free account if it offers one.
Safety label
- Who made it
How this works
- It is a skill: written instructions Claude reads when your request matches what the skill is for. You do not call it by name; just ask for the task.
- While it works, it reads and changes files in the places it lists, nowhere else.
- Nothing runs until you choose to use it, and you can remove it any time.
What it can access
What this kit says it will touch, the same list you see before you add it. These are its Permissions: What a kit is allowed to touch on your computer or accounts, such as reading a folder or using the internet. You see them before you add it.. In Claude Code they become rules, so Claude stops anything not on the list.
Reads
Reads files in ./**
Writes
Writes files in ./docs/plans/**
Writes
Writes files in ./out/plans/**