Community recipe
Turn an approved daily lesson into a guest-teacher handoff
An approved lesson depends on knowledge held by the regular teacher, leaving a substitute unsure where materials are, how the period should run or what to do when the planned activity is unavailable.
One dated handoff draft with a clear sequence, material locations, bounded fallback choices and unresolved information marked for the teacher.
What you need: Source-named agent: Claude Code / Claude Cowork. Suggested inputs: Approved day plan; Practical classroom notes; Approved fallback and escalation references. Use a sanitized plan copy and a separate draft destination with no automatic distribution. Have the teacher inspect the rendered document and resolve placeholders before it becomes an operational packet. Workflow costs and current compatibility remain unverified.
Teacher approves the day's scope, practical logistics and recipient. Keep student-specific accommodation records in approved school systems; require approval before sharing.
Community recipe. BotCurrent has not independently tested this workflow.
Setup and access
Proposed inputs
- Name
Approved day plan
- Owner
Regular teacher
- Minimum scope
One date, subject, lesson sequence and approved learning goals.
- Quality check
Check timetable exceptions and confirm this is the final planned version.
- Name
Practical classroom notes
- Owner
Teacher or administrator
- Minimum scope
Verified material locations, ordinary routines and non-secret access instructions.
- Quality check
Do not include passwords, named learners or individual health/accommodation records.
- Name
Approved fallback and escalation references
- Owner
School
- Minimum scope
Current contact route, where to find official safety instructions and allowed backup activities.
- Quality check
Verify the reference is current; missing emergency details must remain a gap for staff.
Access and setup — proposed or unknown
- Proposed minimum
Use a sanitized plan copy and a separate draft destination with no automatic distribution.
Have the teacher inspect the rendered document and resolve placeholders before it becomes an operational packet.
- Compatibility unknowns
Unknown: generator installation, template rendering, real PII-filter coverage and host/model configuration.
- External actions requiring approval
Sharing school-confidential materials, adding recipients, changing the approved plan or publishing to a school system.
Detailed steps and output format
At a glance
- Suggested result
- One dated handoff draft with a clear sequence, material locations, bounded fallback choices and unresolved information marked for the teacher.Suggested; untested.
- Tool
- Claude Code / Claude CoworkSource-named; check current access.
- Suggested inputs
- Approved day plan; Practical classroom notes; Approved fallback and escalation referencesProposed; access notes below.
- Human review
- Teacher approves the day's scope, practical logistics and recipient. Keep student-specific accommodation records in approved school systems; require approval before sharing.Suggested boundaries; source approvals below.
- Setup notes
- Use a sanitized plan copy and a separate draft destination with no automatic distribution. Have the teacher inspect the rendered document and resolve placeholders before it…Guide notes; proposed setup untested.
Read full note
Use a sanitized plan copy and a separate draft destination with no automatic distribution. Have the teacher inspect the rendered document and resolve placeholders before it becomes an operational packet.
- Cost
- Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
- Content depth
- Source-linked example · suggestions untestedDepth does not establish successful execution.
Function and scope
Education, Administration · Single task
Editorial classification; no execution or compatibility test is implied.
No tool mapping reviewed for this task.
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
An approved lesson depends on knowledge held by the regular teacher, leaving a substitute unsure where materials are, how the period should run or what to do when the planned activity is unavailable.
Suggested task · untested
Prepare a practical replacement-teacher packet from approved teaching content and verified classroom logistics.
What you could produce
One dated handoff draft with a clear sequence, material locations, bounded fallback choices and unresolved information marked for the teacher.
Where these suggestions come from
- Core problem: Our suggestion; no result reported by the source
- Agent job: Our suggestion; no result reported by the source
- Expected output: Our suggestion; no result reported by the source
- Relevant job roles: Our suggestion; no result reported by the source
- Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits
Describes the proposed purpose and review output; measured benefit and successful delivery are not established.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Before you try it · suggestions untested
Original editorial decision guidance and synthetic first check; not the creator's procedure and not executed. Operational source claims are reused only through source_evidence_reference.
Read the attributed source evidence and original caveats below ↓
Why use this
A complete learning objective does not tell a replacement adult which cupboard holds the handouts or how to report unfinished work. Those small omissions can derail an otherwise suitable activity.
The packet should reduce the need for improvised decisions while preserving the regular teacher's intent. It must not fill knowledge gaps with invented school procedures or sensitive learner details.
Why an agent / simpler alternative
- Useful judgment
Turn compact planning notes into explicit operational instructions and identify where a stranger would lack necessary context.
- Simpler alternative
Maintain a reusable substitute binder with the school's approved routines, adding the day's materials manually.
- Unsuitable when
It requires decisions about individual students, special-education placement, emergency response beyond approved school procedures, or access to gradebooks.
Expected deliverable and review checks
- Proposed artifact
A dated one-day handoff with a materials checklist, schedule, approved backup, missing-information list and return note.
- Critical checks
Date, subject, period duration and materials match the approved source plan.
A substitute can find each required item from the instructions or see an explicit unresolved location.
No new learning objective, emergency protocol or individualized learner judgment is invented.
All fictional placeholders and unresolved contacts are removed or visibly held; the correct staff reviewer approves distribution.
- Missing output evidence
No finished packet was rendered or used by a substitute; safeguards were not tested.
First check — proposed, unexecuted
- Status
proposed_unexecuted
- Synthetic fixture
A fictional adult workshop's approved day plan assumes a projector, but the teacher note says it is unavailable. One handout location is missing and an example contact is marked fictional.
- Acceptance checks
The draft uses only a teacher-approved non-projector fallback or asks for one.
The missing location and fictional contact remain blocking review items rather than invented facts.
The learning goal stays unchanged and no participant records are requested.
- Stop conditions
A required school procedure is missing, a placeholder would be published or personal learner data appears.
Tasks: Learning & educationPlanning & operationsWriting & content
Useful for: EducatorAdministrative assistant
Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.Failure handling, costs and limits
Failure signals and proposed responses
- Signal
The packet describes the wrong date or class period.
- Why it matters
Otherwise sensible instructions may refer to unavailable resources or unfinished prerequisites.
- Proposed response
Reconfirm the target day against the timetable before regenerating any file.
- Signal
Missing logistics are replaced with plausible room numbers.
- Why it matters
A substitute may waste time or follow an invalid escalation route.
- Proposed response
Leave a prominent teacher-to-complete item and block operational release.
- Signal
The source plan contains identifiable learner details.
- Why it matters
A general handoff can expose information beyond its intended audience.
- Proposed response
Stop and request an appropriately sanitized source through the school's approved process.
Effort and cost — unknown
- Setup work
Maintain reliable classroom logistics and an approved substitute template.
- Ongoing review
Check the daily content, materials, exceptions and handoff recipient.
- Unknowns
Unknown: model cost, teacher review time, template reliability and classroom usefulness.
Limits
The teacher retains responsibility for suitability and distribution. A privacy scanner or clean document cannot establish institutional compliance.
Full source evidence
Community recipe · Tool workflows
Original task title: Turn an approved daily lesson into a guest-teacher handoff
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.
Original source
https://github.com/revjake1/lesson-plan-magic/blob/main/plugin/skills/classroom-artifacts/SKILL.md ↗Attributed to: Jake Hallman / revjake1
Supporting source context
Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.
- Original action type
- tool_action
- What the source reports
- Resolves the requested day and subject, reads its existing plan context, delegates artifact text to a Haiku subagent and passes structured content through a generator to create a substitute-plan DOCX.
- Source outcome limits
- Draft handoff for teacher review; no completed review, individualized student judgments or emergency-policy invention.
- Evidence attribution caveat
- This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
- Source approval description
- The recipe excludes student names and PII, rejects invented learning goals and asks how to proceed if the day's plan is absent. No sending gate is specified.
- Named tools
- Claude Code/Cowork; Haiku role (exact model version unknown); plan sidecars; Python DOCX generator.
- Model or version
- Unknown
- Publication date
- Unknown
- Source last checked
- 2026-10-14
- Demonstrated in Canada
- Unknown
- Canadian availability
- Unknown
- Proposed Canadian adaptation
- Use local timetable and the school's current approved procedures; no US privacy-law claim is transferred to Canada.
- Recommended approval boundaries
- Teacher approves the day's scope, practical logistics and recipient. Keep student-specific accommodation records in approved school systems; require approval before sharing.