school-administration

name

school-administration

description

Create school- and district-level administrative tools for K-12 leaders: classroom walkthrough instruments, initiative implementation plans, and progress-monitoring / data systems. Use this whenever a principal, assistant principal, or district leader needs leadership tools — phrasings like 'a walkthrough form for our focus on…', 'an implementation plan for rolling out…', 'how do we monitor whether…is working', or 'a school-wide plan for…'. It builds focused walkthrough look-fors tied to a clear initiative, structures rollouts with phases / roles / milestones, and defines what data will show progress. Make sure to use this whenever the scope is school- or system-level implementation and monitoring. Do NOT use it for non-evaluative teacher coaching/PD (professional-learning) or for individual classroom lessons (lesson-planner) — this skill operates at the school/system level.

school-administration

Builds leadership tools for implementing and monitoring initiatives at the school/system level.

Note on people data. Aggregate, implementation-level focus. Use placeholders; never include real student or staff PII. Walkthrough tools here support implementation monitoring — if a tool will be used in formal personnel evaluation, that is governed by district policy and human judgment.

1. Follow the pipeline (references/method.md)

Within Generation: Analysis → (alignment to the initiative/standards) → Differentiation → Generation.

1. Analysis — identify the artifact (references/artifact-types.md), the initiative/focus, the scope (school vs. district), and the audience. Log assumptions.
2. Alignment — tie tools to the initiative's concrete, observable indicators (and to instructional standards where relevant).
3. Implementation thinking — phases, roles/responsibilities, milestones, supports, and the data that shows progress (lead + lag indicators).
4. Generation — draft from the template: focused look-fors / phased plan / monitoring measures, kept practical and summarizable for decision-making.

2. Validate, then gate

Run the universal + admin checks (shared/quality/verification-checklists.md); self-score against references/quality-gates.md, then hand to quality-review.

3. Always emit the metadata block

Per protocol-layer/metadata-schema.md, with human_review_required: true. Placeholders / aggregates only.

Artifact types: references/artifact-types.md. Template: assets/templates/walkthrough-tool-template.md.