Draft a school improvement plan
Drafts a school or department improvement plan from supplied data, with a few priorities, root causes, actions, owners, milestones, resources and how impact will be evaluated.
Improvement plans fail by doing too much: a dozen priorities, actions that are really activities ("hold a training day"), no owner, and success measured by whether the activity happened. Effective plans pick two or three priorities that the evidence supports, diagnose the cause before choosing an action, choose a few well-evidenced approaches, implement them deeply with staff development and time, and track leading indicators (changes in classroom practice, attendance at interventions) during the year as well as lagging outcomes (results) at the end. Data in schools is noisy: small groups swing wildly from year to year and one year's dip is not a trend.
Draft an improvement planOnly if [YEAR] is given: for .
Only if [PRIORITIES] is given:
- What the data says: summarise the 4 to 6 most important findings, each with the figure, the comparison (previous years, similar schools, national or district figures if supplied) and how confident you are given group size and trend. Mark which findings are reliable patterns and which may be noise.
- Priorities: choose no more than three. If leadership priorities were given, keep them and check them against the data; say respectfully if the data points elsewhere. For each priority state the problem, the likely root causes (with what evidence would confirm each), and the intended outcome by the end of the period.
- Action plan: for each priority, 3 to 5 actions that address a root cause, each with an owner (by role, not name unless given), a start date and milestones, the staff development needed, and the leading indicator that shows it is working. Prefer fewer actions done well; note well-evidenced approaches where relevant (for example explicit vocabulary instruction, structured feedback, attendance follow-up) without inventing statistics about their effect.
- Resources: time, money, staffing and training needs, and what will stop or be reduced to make room.
- Monitoring and evaluation: a schedule of checks (half-termly or quarterly) with leading and lagging indicators, the data source, who reviews it, and the decision rule if an indicator is off track.
- Risks: the top risks to delivery (staff turnover, workload, competing initiatives) with mitigations.
- Data caveats: what the data cannot tell you and what extra evidence to gather (lesson visits, student and staff voice, work scrutiny).
- Use only the data supplied. Do not invent figures, national averages or inspection judgements. If a comparison would help but is missing, name it under data caveats.
- Treat small groups with care: with fewer than about 10 students in a group, describe numbers, not percentages, and avoid conclusions.
- Owners are roles; never assign blame to individuals or name staff in a negative context.
- Keep the plan to what a school can realistically do in the period; flag workload implications.
- If the data is too thin to set priorities (for example, only one figure), say what else is needed and draft a provisional plan clearly marked as such.
What the data says
Table: Finding | Figure and comparison | Confidence (pattern / possible noise).
Priorities
A ### per priority: problem, root causes with confirming evidence, intended outcome.
Action plan
Per priority, a table: Action | Root cause addressed | Owner (role) | Start | Milestones | Staff development | Leading indicator.
Resources
Bullets, including what stops.
Monitoring and evaluation
Table: When | Indicator (leading or lagging) | Source | Reviewed by | If off track.
Risks
Table: Risk | Mitigation.
Data caveats
Bullets.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Learning and education
- category
- Teaching
- level
- Expert
- made for
- Teacher / tutor, People manager, Executive / leader
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install draft-school-improvement-plan --target claude-codeThis entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.
pairs well with
All of TeachingAnalyse a class's assessment results
Analyses a class's scores by item and standard to find the weakest skills, likely misconceptions, suspect items and reteaching groups. Use after marking a test or quiz.
analyze-class-assessment-resultsDesign a student feedback survey
Designs a short student feedback survey for a teacher or course, with unbiased questions, a plan for reading the results and a script for responding to the class. Use mid-term or at course end.
design-student-voice-surveyPlan a training evaluation
Builds an evaluation plan for a training programme across reaction, learning, behaviour and results, with survey items, assessments, success measures and a data timeline.
evaluate-training-effectivenessInstructional coach
Coaches teachers as a collegial instructional coach who asks before advising, describes rather than judges, and grounds one high-leverage next step in evidence-informed practice.
instructional-coachAdapt a lesson for a deaf pupil
Adapts a lesson for a deaf or hearing-impaired pupil with seating, lighting, radio aid use, captions, visual vocabulary, pre-teaching, check-ins and rules for group talk.
adapt-lesson-for-hearing-impaired-pupilAdapt a text to several reading levels
Rewrites a passage at several reading levels while keeping the key content and target vocabulary, with a glossary and comprehension questions for each version. For teachers with mixed-ability classes.
adapt-text-reading-level