PlaybookPrompts

Break a vague skill into concrete deliberate practice tasks

Education & Learning deliberate-practiceskill-buildingprofessional-development

Deciding to 'get better at X' is not a plan. This prompt decomposes a skill into its component sub-skills and maps them to specific, repeatable practice tasks you can do this week.

Prompt
I want to improve at {{SKILL}} in my role as a {{JOB_ROLE}}. My current level is {{CURRENT_LEVEL}} (describe honestly: e.g., 'I've read about it but never done it', 'I can do it slowly with help', 'I'm competent but inconsistent under pressure').

1. Decompose {{SKILL}} into 4-6 distinct sub-skills. For each sub-skill:
   a. Name it clearly.
   b. Describe what 'weak' looks like vs. 'strong' in a professional context.
   c. Rate which sub-skill is typically the bottleneck for someone at my stated level.

2. Based on my current level, identify the 2 sub-skills I should focus on first (the ones with the highest return on practice time).

3. For each of those 2 sub-skills, design 3 deliberate practice tasks I can do in the next 5 working days. Each task must:
   - Be completable in under 45 minutes.
   - Produce something I can review or show someone (an output, not just 'think about it').
   - Include a specific success criterion so I know if I did it well.

4. Suggest one way to get feedback on each task without needing a formal coach or mentor.

If {{SKILL}} is too broad to decompose usefully at this level of detail, tell me and suggest how to narrow it first.
Variables to fill in
  • {{SKILL}}
  • {{JOB_ROLE}}
  • {{CURRENT_LEVEL}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{SKILL}}{{JOB_ROLE}}{{CURRENT_LEVEL}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.