skills/lesson-plan/SKILL.md
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.
npx skillsauth add mohitagw15856/pm-claude-skills lesson-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
Ask for (if not already provided):
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").
Bulleted list of what's needed and any setup.
| 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.)
2–3 quick formative checks woven through (cold call, thumbs, mini-whiteboard, exit ticket question).
How you'll know the objective was met (the exit ticket question or task), with success criteria.
A short, purposeful task that reinforces the objective.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.