The prompt
Score 10 of 10, Excellent
Use it when You need to get competent at a tool or skill in a few weeks with practice tasks and checkpoints.
- {{skill}}
- {{goal}}
- {{current_level}}
- {{time_available}}
- {{resources}}
Full prompt and why it works
Prompt
Skill or tool to learn: {{skill}} What I need to be able to do with it, and by when: {{goal}} Where I am now: {{current_level}} Time I can give it: {{time_available}} What I have access to (company training, software, a colleague who knows it, budget): {{resources}} Task: Make a learning plan that gets me from where I am to the goal above in the time I have, so that I can do real work with this skill, not just recognize it. Format: 1. What competent looks like: three to five "I can..." statements, each something I could show a colleague, for example "I can build our monthly report from raw data without looking up the steps." 2. Week-by-week plan, as a table with the columns Week, Focus, Practice task, Checkpoint, Hours. Practice tasks should use my real work wherever possible. Each checkpoint is something observable I can do by the end of the week, not "understand X". 3. Final test: one realistic task that proves I have reached the goal. 4. Getting feedback: who or what can tell me I am doing it right, and when to ask. 5. Beginner traps: three common mistakes people make when learning this, and how to avoid each. 6. Resources: the kind of material to use at each stage. Requirements: - The total hours in the table must fit within the time I gave. If the goal cannot be reached in that time, say so at the top and propose a smaller goal that can. - Spend about two thirds of the time doing and one third reading or watching, because skills are built by practice. - Point to the tool's official documentation, help center or built-in tutorials where they exist. Name a specific course, book or website only if you are confident it exists and is current, and mark it "(verify)"; otherwise describe the kind of resource to look for. Do not invent links. - Keep it under 600 words plus the table, in plain language. The plan should feel demanding but doable alongside my normal work, with each week building on the last. If my current level or goal is too vague to plan from, assume the most common version, state the assumption in one line at the top, and plan from there.
Variables
- {{skill}}
- For example "Power BI", "running workshops" or "basic SQL".
- {{goal}}
- What you need to do with it, and the date, for example "build our weekly sales dashboard by the end of next month".
- {{current_level}}
- What you can already do, for example "comfortable with Excel formulas, never used pivot tables".
- {{time_available}}
- For example "4 weeks, 3 hours a week".
- {{resources}}
- What you can use, for example a company training license, a test account or a colleague. Write "none" if there is nothing.
Why it works
- What good looks like. Competence is defined as things you can show someone, and every week ends with an observable checkpoint, so you know whether the plan is working.
- Length. The hours must fit the time you have, and if the goal cannot be reached it proposes a smaller one instead of an impossible schedule.
- What to avoid. Courses and websites are named only when the model is confident they exist, and marked for checking, so you do not chase invented links.