Learn

Create a practical learning plan

Turn a broad skill into small outcomes, practice, and evidence of progress

5 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Skill to learnStarting pointTime and deadlineReal use case

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Design a practical learning plan for this skill:
[skill]

Starting point:
[starting]

Available time and deadline:
[time]

Real use case:
[use]

Prioritize the smallest set of concepts needed to perform the real task. Build the plan around practice, feedback, and progressively harder deliverables. For each stage provide:
- Observable learning outcome
- Short explanation or resource type needed
- Practice task
- Completion evidence
- Common mistake to check

Include a baseline task for day one and a final task that demonstrates the skill without AI doing the core thinking for me.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Skill to learn: Write basic SQL queries for customer-support investigations.
Starting point: I can filter and summarize spreadsheet data, understand rows and columns, and know what an order ID is. I have never written SQL or used a database console.
Time and deadline: 30 minutes on weekdays for four weeks.
Real use case: Use a read-only analytics database at work to investigate support tickets, such as finding an order and checking its status history. I will have access to the approved schema documentation and a colleague who can review one query each Friday.

Example output

Baseline — Day 1

Using a safe practice dataset, write down how you would find one order and its status history without SQL. Evidence: the fields, filters, and expected rows you think are needed. This exposes gaps without letting AI solve the investigation.

Stage 1 — Read and filter one table

Outcome: Write SELECT, FROM, WHERE, ORDER BY, and LIMIT queries. Resource: A short syntax guide plus the approved schema documentation. Practice: Retrieve one order, then filter a status table by order ID. Evidence: Saved queries and result screenshots. Check: Missing LIMIT, wrong column, or incorrectly quoted values.

Stage 2 — Combine related data

Outcome: Explain keys and use one JOIN to connect an order with status records. Resource: A visual explanation of primary and foreign keys and one reviewed example. Practice: Join the relevant documented tables and sort events chronologically. Evidence: Query, results, and a sentence explaining why each row appears. Check: Duplicate rows or an incorrect join key.

Stage 3 — Investigate defensively

Outcome: Handle NULL values and verify that a query answers the ticket question. Resource: Examples of NULL checks and simple aggregates. Practice: Investigate two anonymized cases and note what the data cannot establish. Evidence: A brief investigation log and one query for Friday review. Check: Treating missing data as proof or changing data in a read-only task.

Final task

Independently investigate a suitable support ticket: define the question, choose documented tables, write and test the query, verify suspicious results, and summarize findings plus limitations. AI may explain syntax or critique the finished query, but you choose the evidence and conclusion.