Course-aligned practice for D31-D36 Context Template Seed. This page uses the previous and next artifacts to keep the practice connected.
Part 2 | D31-D36 Context Template Seed | normal
Turn the seed fields from D31 into a stable task template structure with sections a coworker can reuse.
A teammate says: “Can we turn yesterday’s context seed into a task template the team can reuse?”
It sounds like making a cleaner form. The trap is that a task template must carry goal, context, inputs, review, and output use — not just blank boxes.
“Template: task, details, output.”
The weak version contains generic template, no goal field, no review rule, no context inheritance.
What decision or work outcome does this support?
Which reusable background travels in?
Who checks before use?
Use this rule before filling the build table. The goal is a reusable context asset, not another one-off prompt.
What decision or work outcome does this support?
Which reusable background travels in?
Who checks before use?
A sales-operations analyst wants a reusable template for renewal-risk updates. The team needs a stable section order before anyone fills details.
Turn the seed fields from D31 into a stable task template structure with sections a coworker can reuse.
Collecting useful fields but arranging them randomly, so the next person cannot tell what to fill first.
A teammate sends scattered instructions: “summarize the issue and make it useful.” The reusable template separates task goal, provided material, audience, output form, review owner, and stop condition so the next request is not rebuilt from scratch.
Which section prevents the most rework?
Received: D31 context_template_seed.md
Hands off: D33 task_goal_fields.md
Redline: Do not export a template structure without task, input, output, review, and constraint sections.
Before building the artifact, decide what the template should make easier to review.
This is not a generic sample. It is filled for Day 32: Task Template Structure.
| No. | Template section | Section purpose | Example value | Required or optional | Review rule | Evidence used | Readiness |
|---|---|---|---|---|---|---|---|
1 | Evidence packet | Store renewal date, account notes, risk reason | CRM renewal note + last support ticket | Required | Sales ops owner checks evidence freshness | CRM export 2026-05 sample | Ready for D33 |
Output is routed to the right reviewer before it is shared.
Manager update request with no owner
Review owner + decision use
Core path: complete three rows. Deep path: complete three rows. Blank required fields create export warnings.
| No. | Template section | Section purpose | Example value | Required or optional | Review rule | Evidence used | Readiness |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 |
Optional but recommended: Use this pass to find the context/template field that would fail reuse, confuse a teammate, or hide a review need before export.
Weak row: Template has task/details/output only.
Repair move: Add goal, inherited context, input rule, review owner, and output use.
Better row: Task template: support reply draft; context: approved policy source; review: support lead before customer send.
Choose the field you would be comfortable carrying into the next day.
Choose the field most likely to fail reuse or need review.
Sentence starter: The weak row is weak because ___. I will repair it by adding ___ before using AI.
This file is today’s work receipt. It should show which context/template field can be reused tomorrow, not just that you filled a table.
What this artifact proves: This file proves you can structure a reusable task template from a context seed.
Weak export: Template has task/details/output only.
Good export: Task template: support reply draft; context: approved policy source; review: support lead before customer send.
Click Generate Markdown to create task_template_structure.md.
Continue with a day-specific practice example.