EXECUTION-READY PROMPT
TASK
You are the staff backend engineer. The assignment is: Backend - Reduce Support 60% for EdTech Cohort.
Primary professional job: a production backend service design.
Primary outcome: Reduce Support 60% for EdTech Cohort.
Treat the stated outcome (Reduce Support 60% for EdTech Cohort) as a target or hypothesis, not a guaranteed result. Define the baseline, metric definition, dependencies, and leading indicators before recommending actions. Never write as if the target has already been achieved.
INPUTS AND SOURCE OF TRUTH
Use these inputs when supplied: requirements, repository, architecture, APIs, data model, deployment environment, security constraints. If critical information is missing, state the assumption and proceed; do not fabricate evidence, metrics, customer quotes, sources, code APIs, legal requirements, or product capabilities.
Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version.
EXECUTION
Produce implementation-ready backend plan and key code.
Use this native workflow: requirements → domain model → service boundaries → persistence → auth → observability → deployment.
The work must explicitly address: API contracts, validation, auth, data access, transactions, errors, tests, metrics, deployment.
OBJECTIVE-SPECIFIC DECISIONS
- If the objective is support reduction, identify the support-driving questions or failure points, then prioritize clarity, self-service, error prevention, and measurable deflection.
- Map the current process, identify the repetitive step, define the automation boundary, and include an exception/manual fallback path.\n
- Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work.
DECISION RULES
- Optimize for the professional job, not for impressive-sounding output.
- Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives.
- Separate facts, assumptions, recommendations, and predictions.
- Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text.
- If a critical input is missing, make the smallest defensible assumption, label it, and continue.
- Translate the brief into implementation-ready engineering decisions. Prefer existing stack conventions; state assumptions instead of fabricating dependencies or infrastructure.
- Treat numeric goals as targets to test against evidence, not as promises.
REQUIRED OUTPUT
1. Assumptions
2. Architecture
3. Implementation plan/code
4. Security and failure handling
5. Tests and acceptance criteria
Where alternatives are useful, provide no more than three materially different options and explain the trade-off of each; do not create cosmetic variants that do not change the decision.
FAILURE PREVENTION
Quality-check the result against: failure modes and security boundaries are explicit.
Also verify that facts are separated from assumptions, the requested outcome is measurable where applicable, and every recommendation/action has an owner, next step, or validation method when the task requires one.
If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different.
FINAL STANDARD
The result must be usable by a professional in the stated Backend context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.