lesson-plan
Build a complete, standards-aligned lesson plan with clear objectives, a timed activity sequence, differentiation, and assessment. Use when asked to write a lesson plan, plan a class or lesson, design a teaching session, or structure instruction for a topic. Produces a ready-to-teach plan with measurable objectives, a minute-by-minute flow, materials, checks for understanding, and differentiation for varied learners.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/lesson-plan && cp -r /tmp/lesson-plan/plugins/pm-education/skills/lesson-plan ~/.claude/skills/lesson-planSKILL.md
# Lesson Plan Skill
A great lesson plan makes the goal measurable, the time accountable, and learning visible. This skill produces one a teacher can walk into class and run — with built-in differentiation and checks for understanding.
## Working from a brief
Given a topic and grade level, **produce the full plan anyway** — infer reasonable objectives and standards and mark them *(adapt to your standards)*. Never leave "[insert activity]"; supply concrete, age-appropriate activities.
## Required Inputs
Ask for (if not already provided):
- **Topic / subject** and **grade or age level**
- **Lesson length** (e.g. 45 min) and **format** (in-person, remote, hybrid)
- **Standards / curriculum** to align to (optional — note if to be adapted)
- **Class context** (size, range of abilities, language needs)
## Output Format
### Lesson overview
- **Topic · Grade · Duration**
- **Standards alignment:** [framework + codes, or "adapt to your standards"]
### Learning objectives
2–4 objectives in measurable, student-facing form: *"By the end, students will be able to [observable verb]…"* (use Bloom's-level verbs; avoid "understand/know").
### Materials & prep
Bulleted list of what's needed and any setup.
### Lesson flow (timed)
| Time | Phase | What happens |
|---|---|---|
| 0–5 | Hook / warm-up | Engage and surface prior knowledge |
| 5–15 | Direct instruction | Teach the core idea |
| 15–30 | Guided / group practice | Students apply with support |
| 30–40 | Independent practice | Students work solo |
| 40–45 | Close / exit ticket | Consolidate + check understanding |
(Adjust the splits to the real duration.)
### Checks for understanding
2–3 quick formative checks woven through (cold call, thumbs, mini-whiteboard, exit ticket question).
### Differentiation
- **Support** (struggling / ELL / IEP): scaffolds, sentence frames, visual aids
- **Extension** (advanced): a stretch task or deeper question
### Assessment
How you'll know the objective was met (the exit ticket question or task), with success criteria.
### Homework / follow-up (optional)
A short, purposeful task that reinforces the objective.
## Quality Checks
- [ ] Objectives are measurable and student-facing (observable verbs, not "understand")
- [ ] The timed flow sums to the lesson length
- [ ] Includes at least two checks for understanding
- [ ] Differentiation covers both support and extension
- [ ] Assessment maps directly back to the objectives
## Anti-Patterns
- Objectives that can't be observed or measured ("students will appreciate…")
- A flow that's all teacher talk with no student practice
- No formative checks until a final test
- One-size-fits-all with no differentiationConduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.