Skip to main content
ClaudeWave
Skill1.2k repo starsupdated yesterday

iep-goal-support

Draft SMART IEP goals, accommodations, and present-levels statements that are measurable and compliant in spirit. Use when asked to write an IEP goal, draft special-education goals, list accommodations, or write a present-levels (PLAAFP) statement. Produces measurable annual goals with baselines, criteria, and measurement methods, plus matched accommodations. A drafting aid for educators — not legal advice; the IEP team and local requirements govern.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/iep-goal-support && cp -r /tmp/iep-goal-support/plugins/pm-education/skills/iep-goal-support ~/.claude/skills/iep-goal-support
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# IEP Goal Support Skill

IEP goals only help a student if they're measurable: a baseline, a target, a timeframe, and how progress is checked. This skill drafts SMART goals and matched accommodations educators can bring to the team. **This is a drafting aid, not legal advice — the IEP team, the student's data, and local/IDEA requirements govern the final document.**

## Working from a brief

Given a student profile and area of need, **draft full goals anyway**, using clearly-labelled illustrative baselines *(replace with the student's real data)*. Never invent specific diagnoses; work from the need described. Always keep the disclaimer.

## Required Inputs

Ask for (if not already provided):
- **Area of need** (reading fluency, math, writing, behaviour/SEL, communication, motor, executive function)
- **Present level** — what the student can do now (baseline data if available)
- **Grade/age** and any relevant context
- **Timeframe** (typically annual) and how progress is measured

## Output Format

### Present levels (PLAAFP) statement
A concise, strengths-first paragraph: what the student can currently do, the baseline data, and how the need affects access to the general curriculum.

### Annual goal(s) — SMART
For each: *"By [date], given [condition], [student] will [observable behaviour] to [criterion], as measured by [method] across [n] occasions."*
- Baseline → Target → Criterion (e.g. accuracy %, words/min, trials)
- **Measurement method** (probes, work samples, observation, charts) and **frequency**

### Short-term objectives / benchmarks (optional)
2–4 steps that ladder up to the annual goal.

### Accommodations & supports
Matched to the need (e.g. extended time, text-to-speech, chunked tasks, movement breaks) — distinguish **accommodations** (access) from **modifications** (changed expectations).

### Progress-monitoring plan
What data is collected, how often, and what counts as on-track vs needs-revision.

## Quality Checks

- [ ] Every goal is measurable: baseline, condition, observable behaviour, criterion, measurement method, timeframe
- [ ] Goals tie directly to the present-levels statement
- [ ] Accommodations are matched to the stated need and distinguished from modifications
- [ ] Illustrative baselines are clearly flagged *(replace with real data)*
- [ ] Retains the "drafting aid, not legal advice; team/IDEA governs" note

## Anti-Patterns

- Vague goals ("will improve reading") with no criterion or measurement
- Inventing a diagnosis or specific data not provided
- Confusing accommodations with modifications
- Presenting drafts as final/compliant without team review
ai-ethics-reviewSkill

Conduct 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.

ai-product-canvasSkill

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.

design-handoff-briefSkill

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.

experiment-designerSkill

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.

multi-source-signal-synthesiserSkill

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.

data-analysis-standardSkill

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.

product-health-analysisSkill

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.

retention-analysisSkill

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.