Skip to content
LIVERun 001 capturing

planned / v1.0.0

School Communication Copilot

A school communication workspace for bilingual notices, scheduling, acknowledgements, reminders, circulars, targeting, and history.

Open exact prompt

Overview

Evaluate a model's ability to implement School Communication Copilot as a bounded, evidence-backed product challenge.

Capabilities tested

  • scheduling
  • multilingual
  • workflows

Required outcome

A school communication workspace for bilingual notices, scheduling, acknowledgements, reminders, circulars, targeting, and history.

Requirements

functional

  • A school communication workspace for bilingual notices, scheduling, acknowledgements, reminders, circulars, targeting, and history.

ux

  • Responsive, readable interface
  • Keyboard-accessible core controls

technical

  • Production build succeeds
  • No secrets or private data in the artifact

Constraints

Allowed

  • Local sample data
  • Established framework utilities

Forbidden

  • Automated model execution
  • Unreviewed private data
  • Unsupported production claims

Acceptance criteria

  • The primary workflow is complete and observable
  • Core controls change real local state
  • Failure or empty states are visible
  • The narrow viewport remains usable

Evidence required

  • Production build output
  • Desktop and mobile screenshots
  • Core-flow recording
  • Known-bug list

Exact prompt

prompts/challenges/school-communication-copilot.md
# BuildArena Challenge

Role: Senior product engineer.

Project: School Communication Copilot v1.0.0

Objective: Evaluate a model's ability to implement School Communication Copilot as a bounded, evidence-backed product challenge.

Required outcome: A school communication workspace for bilingual notices, scheduling, acknowledgements, reminders, circulars, targeting, and history.

Functional requirements:
- A school communication workspace for bilingual notices, scheduling, acknowledgements, reminders, circulars, targeting, and history.

UX requirements:
- Responsive, readable interface
- Keyboard-accessible core controls

Technical requirements:
- Production build succeeds
- No secrets or private data in the artifact

Constraints:
- Allowed: Local sample data; Established framework utilities
- Forbidden: Automated model execution; Unreviewed private data; Unsupported production claims

Build order: Inspect the environment; establish the smallest vertical slice; verify the central workflow; add secondary requirements; run production validation.

Evidence to return: Commands, test results, screenshots, core-flow recording, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.

Claims prohibited without proof: complete, production-ready, fully working, bug-free, accessible, responsive, performant.