Lab brief — complete before drafting

Replace every bracketed field. Claude must stop rather than guess if a required field remains incomplete.

Identity and placement

• Working title: [required]
• Primary module slug: [required; exact canonical slug, for example conversational-privacy]
• Related module slugs: [required; use [] when none]
• Related track slugs: [required; exact canonical slugs]
• Level / intended audience: [required]
• Owner / credit name: [required]
• Target package status: Draft

Learning design

• Learner outcome: [required; observable verb]
• Why this matters: [required]
• Core concept or skill: [required]
• Distinctive role: [required; explain how this differs from nearby labs and whether it is a core-skill drill or an applied use case]
• Activity format: [required; individual, pair, group]
• Starting scenario or inputs: [required; fictional, synthetic, volunteered, or safely redacted]
• Learner artifact: [required]
• Known nearby labs to avoid duplicating: [required]

Boundaries and evidence

• Tools and account limits: [required; write no tool required when appropriate]
• Safety, privacy, ethics, or accessibility boundary: [required]
• Claims, sources, or subject-expertise limits: [required; write none supplied only when no factual claim is needed]
• Review needs: [required; for example learning design, accessibility, privacy, safety, subject expertise, pilot]
• Reusable materials to create: [required; list or none]
• Static app approval: [required; write not approved unless a separate decision is supplied]

Acceptance criteria

• [required] A learner can complete the activity without an oral explanation.
• [required] The output makes the intended learning visible.
• [required] The package names its limits and human-review gaps honestly.
• [add assignment-specific criteria]

---

Source: contributor-packs/claude-code-lab-drafter/LAB-BRIEF.md