Copy: the steps to plan a project, if you have none yet · with /grill-me · 5 steps, about 15 min1. In the Code tab, open your projects folder and send: Create a folder called [project-name] here. 2. Open that new folder with the folder button, then + New. 3. Switch the mode to Plan, then send: /grill-me I want to build [your project in one sentence], for [who uses it]. 4. Answer the questions until Grill Me writes the plan (10–15 minutes). 5. Switch Plan off, then send: Save the plan as PLAN.md in the project folder. Don't build anything yet.

Download prompt · saves /coach in your skillsDownload the file at https://adapttoai-walkthrough-assets.pages.dev/skills/coach-at-work/SKILL.md and save it exactly as it is, without retyping or summarising it, as .claude/skills/coach/SKILL.md inside my home folder. Create the folders if they're missing, and replace the file if it's already there. Then tell me in one line whether it worked.

Prompt B · Claude maps the project itself, then two subagentsLook at this project and tell me in five short lines: what it's for, what's built, what's next, what blocks it, and what would make it more useful for my team. No technical words. Then work only as a coordinator, and open two threads. Thread 1, researcher: if something blocks the project, read the official documentation of the system involved and find how to connect it, read-only. If you need the exact version of the system (for example Sage), tell me how to find it. If nothing blocks the project, find how it could run on its own or get its data automatically. Thread 2, files: if the project is waiting for data, make a small made-up file in the same shape as that system's export, mark it "Example data", and make the tool run on it. If nothing blocks the project, write a one-page "how to use it" for a colleague. When both are done, tell me in plain words: what you found, what works now, and, if someone else has to unblock me, the exact message to send them (IT, a colleague or my manager). Never ask me to paste a password or key here.

Prompt A · you did the Before Lesson 4 lessons · paste your summary in itHere is where my project is, from my Before Lesson 4 summary: [paste your summary: Project, Built so far, Missing from the plan, Stuck on, Help I'd like] Start from it, don't redo it. Check it against the project and tell me in one line if anything has changed. Then work only as a coordinator, and open two threads. Thread 1, researcher: if something blocks the project, read the official documentation of the system involved and find how to connect it, read-only. If you need the exact version of the system (for example Sage), tell me how to find it. If nothing blocks the project, find how it could run on its own or get its data automatically. Thread 2, files: if the project is waiting for data, make a small made-up file in the same shape as that system's export, mark it "Example data", and make the tool run on it. If nothing blocks the project, write a one-page "how to use it" for a colleague. When both are done, tell me in plain words: what you found, what works now, and, if someone else has to unblock me, the exact message to send them (IT, a colleague or my manager). Never ask me to paste a password or key here.

Prompt B · you didn't do them · Claude maps the project itselfLook at this project and tell me in five short lines: what it's for, what's built, what's next, what blocks it, and what would make it more useful for my team. No technical words. Then work only as a coordinator, and open two threads. Thread 1, researcher: if something blocks the project, read the official documentation of the system involved and find how to connect it, read-only. If you need the exact version of the system (for example Sage), tell me how to find it. If nothing blocks the project, find how it could run on its own or get its data automatically. Thread 2, files: if the project is waiting for data, make a small made-up file in the same shape as that system's export, mark it "Example data", and make the tool run on it. If nothing blocks the project, write a one-page "how to use it" for a colleague. When both are done, tell me in plain words: what you found, what works now, and, if someone else has to unblock me, the exact message to send them (IT, a colleague or my manager). Never ask me to paste a password or key here.

Get it ready · saves a first version, leaves out keys and real dataI want to put this project on GitHub. First get it ready, in this project's folder only, and save a first version of everything that's here. Leave out any .env file, anything with passwords or keys, and any real data export: they stay only on this computer. Explain what you did in two lines.

Put it on GitHub · private repository, first pushThis project only exists on my computer. Put it on GitHub: create a private repository and do the first push. Before anything goes up, check that nothing secret goes with it: no .env file, no passwords, no keys, no raw data exports. Explain what you're doing as you go.