| name | family-communication |
| description | Write clear, warm, family-facing communication for K-12: class newsletters, parent/guardian letters and emails, conference talking points, and progress-report narrative comments. Use this whenever a teacher or administrator needs to communicate home — phrasings like 'write a newsletter about…', 'a letter to parents explaining…', 'an email to a family about…', 'talking points for conferences', or 'comments for report cards'. It writes in plain, jargon-free, translation-friendly language at an accessible reading level, keeps a respectful strengths-based tone, and is careful to protect student privacy. Make sure to use this whenever the audience is families/guardians rather than students or staff. CRITICAL: use placeholder names only and never include real student data or sensitive details; for individual messages, keep specifics general and flag for the teacher to personalize. Do NOT use it for staff/PD communication (professional-learning) or instructional materials (lesson-planner). |
family-communication
Writes family-facing communication that is clear, warm, and privacy-safe.
Privacy first (SECURITY_AND_SAFETY.md). Use placeholder names and never include real
student data, grades, behavior details, or health/SpEd information. For a message about an
individual child, keep specifics general and mark where the teacher must personalize — the teacher
adds real details directly, not through this skill.
1. Follow the pipeline (references/method.md)
Within Generation: Analysis → (light Standards Alignment) → Differentiation → Generation.
- Analysis — identify the artifact (
references/artifact-types.md), audience (all families vs.
one family), purpose, and tone. Log assumptions.
- Standards alignment (light) — where it helps families understand learning, translate the
relevant standard into plain language (no codes/jargon in the family-facing text).
- Accessibility & inclusion — plain language, ~grade 6-8 readability by default
(
shared/quality/readability-age.md), define any necessary terms, translation-friendly phrasing,
respectful strengths-based tone, culturally inclusive.
- Generation — draft from the template; keep it concise and skimmable; include a clear call to
action / contact line.
2. Validate, then gate
Run the universal + communication checks (shared/quality/verification-checklists.md) — the Safety
gate (no real PII) and Accessibility gate (readability, tone) are key. 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 and a note on where the
teacher should personalize. Placeholders only.
Artifact types: references/artifact-types.md. Template: assets/templates/newsletter-template.md.
