Curate the reusable project pack

1

Research

Why this matters, and what good looks like

A reusable project pack is a curated record, not a dump of every file. Project Zero describes documentation as purposeful and intentional, driven by a guiding question. That means keeping the material another teacher needs to understand, adapt and verify the project. AI can help name and summarize files, but UNESCO's accuracy warning makes the original file the source of truth.

Keep purpose, sequence and evidence with the materials they explain.
Record authorship, provenance, permission and version.
Separate reusable templates from student work and local records.
Keep failed approaches and next-time notes when they explain a change.
Exclude anything whose ownership, consent or accuracy is unclear.

Evidence limits: Project Zero supports purposeful documentation of learning, not a tested digital-pack workflow. UNESCO supports checking AI accuracy, not permission clearance. Neither establishes an AI benefit, time saving or improved pack quality.

Where the evidence comes from

Moderate for professional documentation; AI benefit unvalidated.

2

Workflow

Brief it, steer it, check it

Build the source manifest

Start with materials from a completed or revised run. Remove personal data before pasting, including contact details and identifying combinations. Keep restricted originals in the approved school store.

Prompt 1 · Pack inventory

CONTEXT
Existing file list and locations: [paste it].
Teacher descriptions or safe excerpts, keyed by file: [paste them].
Known author, source, date, version and permission scope per file: [paste them].
Project purpose and sequence: [paste them].

REQUEST
Create a manifest; identify missing content evidence, provenance, ownership, permission and version information.

QUALITY BAR
Use only supplied evidence, never infer author, licence, consent or date from filenames or context.
Unknown is unknown, not internal permission. Hold affected items; do not invent clearance.
Do not summarise unseen contents. Record absent descriptions as missing.

FORMAT
Table: file, purpose evidence, author/source, date/version, permission scope, missing information, hold reason.

Decide what belongs

You verify copyright, age suitability and local fit. Decide whether to retain an exemplar using approved annotations and permission, or exclude it and record the incomplete result. Redaction alone does not grant reuse rights.

Prompt 2 · Curation candidates

CONTEXT
Teacher-verified manifest and descriptions/excerpts: [paste them].
Intended users, age range and local context: [paste them].
Retention, privacy and copyright rules: [paste them].
Teacher notes, age/local-fit checks and permission decisions: [paste them].
Exemplar excerpts, teacher annotations and authorised reuse scope, or explicit no-exemplar choice: [paste them].

REQUEST
Propose keep, revise, archive, exclude or hold for each item. Identify duplicates without deleting originals. Specify exemplar handling and any contact-record exclusions.

QUALITY BAR
Preserve permissions exactly; never infer consent or turn fictional learners into consenting real learners.
Only use approved, privacy-safe exemplar excerpts and teacher annotations; do not invent learner work or annotations.
Do not copy private contacts. Missing permission means hold, not implicit approval.
Missing age/local-fit checks remain teacher checks. All decisions are candidates for teacher approval.

FORMAT
Table: item, candidate, evidence/reason, restriction, age/local fit, teacher decision needed.
Then exemplar handling and functional gaps caused by held/excluded resources.

Draft metadata and index

Approve candidates yourself. Check summaries against actual file contents. Save originals unchanged. AI drafts an index; you assemble and verify the actual pack.

Prompt 3 · Metadata draft

CONTEXT
Teacher-approved contents and decisions: [paste them].
Verified manifest plus teacher descriptions or safe excerpts per approved file: [paste them].
Approved naming/folder rules and pack version/date: [paste them].
Purpose, sequence, adaptations and next-time notes with owners: [paste them].
Approved exemplar excerpts, teacher annotations and permission scope, or no-exemplar decision: [paste them].

REQUEST
Draft metadata and a pack index. Carry approved exemplar excerpts and teacher annotations with attribution and restrictions, or record an exemplar gap.

QUALITY BAR
No description/excerpt means no summary: mark missing and hold. Never infer unseen contents from a manifest.
Preserve supplied authorship, dates, versions and permission labels. Retain original titles.
Use only supplied annotations and cross-link targets; flag unresolved links. Do not claim files were created, opened or verified.
A no-exemplar branch is an incomplete draft, not the promised complete pack.

FORMAT
Pack version/date; table: current file, proposed name, summary, supporting description/excerpt, tags, related item, verification note.
Index: purpose, sequence, materials, annotated exemplars or gap, adaptations, provenance/permissions, next-time notes/owners.

Check release

Assemble the pack in the approved store, then verify its files and links. Keep a redacted or no-exemplar draft on hold until the promised result and necessary resources are complete.

Prompt 4 · Pack release check

CONTEXT
Verified manifest and approved descriptions/excerpts: [paste them].
Assembled index, folder list, pack version/date and teacher file/link-check results: [paste them].
Permission/privacy checks, exemplar annotations/decision and age/local-fit confirmations: [paste them].
Sequence-to-resource map, approved adaptations and next-time notes/owners: [paste them].

REQUEST
Check missing files, broken links, altered provenance, unsupported summaries, permission/privacy conflicts and functional gaps. State whether the promised result is complete.

QUALITY BAR
Do not repair or rename anything. Do not infer permissions, dates or file contents.
Check ownership, consent, provenance and accuracy separately; unresolved evidence blocks release.
Check private contacts, pack version/date, annotated exemplars, age suitability and local fit separately.
A blocked resource can break the sequence even when excluded from the index. Missing exemplars mean incomplete, not complete.
Without actual teacher file/link checks, mark not verified. Never claim an assembled artifact from an index alone.

FORMAT
Release status; table: check, supplied evidence, pass/hold/not verified, owner/action.
Then verified contents, functional gaps, exemplar completeness and next-time notes needing owners.

Check before you use it

Can every included file be traced to verified ownership, provenance, date/version and permission scope?
Do summaries have teacher descriptions/excerpts and match the actual files?
Are private contacts and unconsented learner work excluded without inventing clearance?
Are approved annotations, attribution and permission attached to each exemplar?
Are pack version/date, age suitability and local fit confirmed by you?
Can another teacher follow the sequence with the available resources?
Are incomplete results held, with gaps and next-time changes assigned an owner?

Stop rule

Stop if ownership, consent, provenance or factual accuracy cannot be verified.

3

Reuse it

So the next one takes minutes

Suitable

Build a skill

Save this as a reusable instruction you can run on any project.

The inventory, permission check and packaging sequence can be reused after each project.

Not suitable

Build an agent

Chain the steps, with a checkpoint where you approve.

A teacher must approve curation, authorship and permissions on every run before the pack is saved.