evidence-package-for-education

Evidence Package for Education

Overview

Maintains an evidence ledger that maps each requirement or standard to the artifacts that satisfy it, with owner, date, freshness, and status. Each run refreshes evidence, re-tests gaps, and assembles a reviewable package version.

When to Use

• Preparing for accreditation, program review, or a grant report
• The user asks which requirements are covered, thin, or unevidenced
• The evidence ledger needs refreshing before a submission deadline

When NOT to Use

• Writing only the narrative self-study prose with no evidence mapping
• Reviewing agents, plugins, or connectors — use governance-review-for-education
• Any request involving identifiable student records

Shared Skill Contract

This skill follows the institution's shared contract for every run:

1. Intent check — confirm outcome, audience, timeframe, and format before working.
2. Source plan — show the sources selected, their date ranges, access gaps, and freshness.
3. Clarification gate — ask only for missing information that would change the result.
4. Staged execution — keep discovery, synthesis, creation, review, and finalization separate.
5. Reviewable output — separate facts, interpretation, recommendations, assumptions, and open questions.
6. Human approval — require confirmation before sending, publishing, or changing any record.
7. Reusable state — carry accepted decisions forward without silently reusing stale assumptions.
8. Quality check — run the checks below before presenting final output.
9. Telemetry — log workflow signals only; never sensitive content.
10. Failure behavior — explain missing access, unsupported sources, uncertainty, and partial completion.

Preconditions (all must clear before any search)

These three are gates, not suggestions. If any is unresolved, stop and ask. Do not begin searching to "get started" while one is open — evidence gathered before these clear cannot be trusted into the ledger.