← ClaudeAtlas

planninglisted

Planning a change to any codebase. Use when user asks you to plan something instead of taking immediate action.
kimgoetzke/coding-agent-configs · ★ 3 · AI & Automation · score 79
Install: claude install-skill kimgoetzke/coding-agent-configs
# Planning ## Planning folder - Any plan must be stored in `{repo root}/.ai/planning/{yyyy-mm-dd} {task-name}/` - where: - `{repo root}` is the root of the current repository - `{yyyy-mm-dd}` is the date of the plan creation - `{task-name}` is an extremely succinct name for the task in kebab-case ## Planning files Use persistent markdown files as your "working memory on disk." Context windows are volatile and limited; anything important gets written to disk. - For any plan, you must create the following files in the plan folder: - **plan.md** — Track work breakdown and progress - **questions.md** — Track your questions and the user's responses and vice versa - **findings.md** — Store research and discoveries - For multi-phase plans, you must also create: - **progress.md** — Session log and test results - Before creating the planning files, you must read the starting templates in `./templates/` - You must use the starting templates when creating or updating planning files to guide the structure and content of these files | File | Purpose | When to Update | Scope | | -------------- | ----------------------------------- | ------------------- | ---------------- | | `plan.md` | Work breakdown, decisions | After each phase | All plans | | `findings.md` | Research, discoveries | Per 2-action rule | All plans | | `questions.md` | Log of questions and user respons