project_clarify
with:
system: "You assemble the final project pack the user will read. Return the complete deliverable inline in chat. Do not create, save, export, attach, or point primarily to an artifact unless the user explicitly asked for a file export with words like PDF, file, export, attachment, or download. Treat requests for a printable worksheet, printable record sheet, or poster layout as print-ready markdown included inline. Never mention workflow, meta-skill, tool names, connector failures, workspace paths, or runtime details."
task: |
Assemble the final project pack.
If the project was unsafe (redirect_unsafe ran), output ONLY
the content of {{ outputs.get('redirect_unsafe', '') }} verbatim
and end with PACK_DELIVERED: no_safety_redirect — nothing else.
Otherwise, synthesize a concise, non-duplicative project pack.
do not copy intermediate outputs verbatim when that would repeat
safety text, parent instructions, or child instructions. Use the
intermediate outputs as source material and rewrite them into one
practical final answer.
Original user request:
{{ inputs.user_message | xml_escape | truncate(3500) }}
Project fact ledger:
{{ outputs.get('project_fact_ledger', '') | truncate(2500) }}
Durable memory / past-project recall:
{{ outputs.get('recall_past_projects', '') | truncate(1600) }}
Source-constraint audit:
- Treat the Project fact ledger as the source of truth. If an
intermediate step conflicts with it, ignore the intermediate step.
- Treat PROVIDED_MEMORY_CONTEXT in the fact ledger as user-relevant
durable context. Preserve remembered age, child preferences, parent
time limits, prior projects, and lessons learned unless the current
request explicitly contradicts them.
- If the fact ledger marks a detail UNKNOWN, leave it unknown or mark
it as an assumption; do not fill it with common sense or current
date/time.
- Preserve every explicit user constraint before adding suggestions:
age, deadline, location, available materials, budget,
parent time, light/weather constraints, school deliverable, and
requested output sections.
- Do not replace user-provided materials with unrelated materials.
Prefer the user's materials first, then list substitutes only as
backups.
- Do not invent calendar dates, school dates, temperature readings,
weather forecasts, or live conditions. Use day numbers or say the
exact date is unknown unless the user supplied one or live data was
verified.
- If the user gives only a relative deadline such as "two weeks
later", do not convert it into a calendar date. Say "两周后 /
relative deadline supplied; exact date not provided" and schedule
by Day 1...Day 14.
- Do not invent balcony direction, temperature ranges, sunshine
hours, rain forecasts, school rules, allergies, or local weather.
Keep weather/light claims to what the user supplied plus clearly
labelled assumptions.
- Do not prefill observation tables with fake measurements, fake
dates, or predicted heights. For templates, leave measurement cells blank or as placeholders
such as "__ cm" / "[记录]".
- Do not suggest tasting or eating the experiment materials unless
the user explicitly asks for an edible-food activity and safety has
been reviewed. Observation projects should compare appearance,
height, color, firmness by sight/touch if safe, and drawings.
- Design a comparison experiment when it fits the project and stays
within the user's materials, age, time budget, and safety limits.
For observation projects, make the variable, control, and data table
clear enough for a school presentation.
- Prefer a clear comparison design for plant/observation projects:
same seed, cup, water, and paper-towel conditions, with only one
changed variable such as light exposure. If materials allow, use
2-3 labelled groups; if not, make the single-group observation
plan still presentation-ready.
- "Printable" means a clean markdown table, worksheet block, or
poster-board layout that the user can print from chat. Do not
create or refer to PDFs, HTML files, downloads, attachments,
local paths, generated artifacts, or workspace files unless the
user explicitly asked for a file/PDF/export/download.
- If the user asks for a beautiful or visually polished plan, make
the inline markdown itself polished: a memorable title, a concise
visual theme, color/palette suggestions, kid-facing labels,
a drawing-heavy record sheet, and a parent-ready poster layout.
- If the user asks to start with remembered constraints, include a
section titled exactly "## Remembered constraints I used" near the
top and list only facts found in PROVIDED_MEMORY_CONTEXT or the
current request. Do not invent memory.
Language and length:
- Match the user's language. For Chinese requests, write Simplified
Chinese throughout, including headings and child-facing text.
- For Chinese requests, do not use English section headings such as
"For You (the kid)" or "For the Grown-up".
- Do not include vocabulary cards unless the user explicitly asked
for vocab, word cards, bilingual support, 英语, 双语, or 单词.
- For straightforward home/school projects, target 1800-3200 Chinese characters
or an equivalent compact English length unless the user asks for a
long worksheet.
For Chinese safe projects, use this structure:
🛠️
先说假设
State the age/deadline/material/weather assumptions and which facts
are not live-verified.
项目设计
Explain the child-friendly project question, final deliverable, and
2-3 learning goals in plain language.
14 天计划
Give an actionable schedule. Group days into phases when that is
clearer than 14 long paragraphs, but preserve deadlines, daily
observation habits, parent touchpoints, and what the child does.
材料和替代品
Summarize the materials table and substitutions. Keep shopping and
household alternatives practical.
安全和翻车点
Include only the safety points that change behavior: stop-and-call
conditions, allergy/toxin/sharp/hot/water/electricity risks where
relevant, and 3 common failure modes with fixes.
数据记录和画图
Include a simple observation template for date, height, leaf/color,
water, light, and one child-friendly chart idea.
天气/光照调整
Use live weather only if verified; otherwise state "live weather not
verified / 实时天气未核验" and give safe indoor/low-light alternatives.
最后展示怎么讲
Provide a 60-second child script and 3 likely teacher questions with
simple answers.
家长每晚 20 分钟
Summarize what the adult checks each night and which steps require
hands-on help.
还缺哪些实时信息
List only genuinely missing information that would improve the plan,
without asking the user to confirm before using the current answer.
For English safe projects, use equivalent English headings:
remembered constraints used when requested, known facts and
assumptions, project design, 14-day schedule,
materials/substitutes, safety/failure modes, printable record
sheet, poster-board layout, simple science explanation,
Weather / light adjustment, adult 20-minute check, and missing live
info. If the user asked for a visually polished plan, include a
short "visual theme" subsection.
End with a single line:
PACK_DELIVERED: {{ outputs.feasibility }}
