core

PRISM framework loader

This Skill loads PRISM — the canonical operating framework for structured, multi-session, multi-vendor LLM-orchestrated audit and research. The framework is decomposed into a lean always-loaded core plus on-demand bundles; load the core first, fetch a bundle only when the work in front of you needs it.

When triggered

1. Read PRISM_core.md in full before acting — it is the operating core (operating model and architecture, the Execution Envelope / Self-check / Output triple contract, the prompt-package engine, the context-pressure framework including the M5 bands and the in-core recovery floor, the §{section.lens-schema-what-orchestration-consumes} lens schema, Monitors M1–M12, Standing Principles, filename conventions, the atomic-prompt template, the operator-hint catalog, the engagement-closure gate, and the phase → bundle manifest). Phase-scoped mechanics (Setup, currency, continuity, corpus-access) are on-demand bundles — see step 5.
2. Run the SP-13 substrate self-check (Standing Principle SP-13, in the core's section 10.1.3): declare your model identity and confirm you are Claude, Opus-class / flagship tier (a capability floor — version-agnostic, latest by default). Halt and ask the operator on mismatch or cannot-determine.
3. Run M1 (Missing Inputs) and M2 (Version Drift): verify the canonical attachments are present (Master, subject brief, and a Prompt Strategy if separate) and that the Master version matches what the last What's next predicted. Halt at HIGH severity on a missing required artifact or a version mismatch.
4. Proceed per the Master's What's next artifact, or per the operator's declared next action.
5. Load the phase bundle for the role you occupy. The core is lean; phase-, seam-, and condition-scoped mechanics are fetched on demand per the core's phase → bundle manifest (section 3.7.6). Run the visible self-check and fetch:
   • Setup / P0 (no Master yet, or the operator initiates an engagement) → reference/setup.md (probes, three-layer readiness, Setup-artifact procedures).
   • Update session / the session-open currency check → reference/currency.md.
   • Resume with a missing or abnormal handoff, or M5 band 🟠/🔴 → reference/continuity.md (the in-core recovery floor stays resident; the full migration / recovery procedure is in the bundle).
   • A pass classified corpus-access → reference/corpus-access.md. Each gutted area carries a fail-loud in-core stub — operating without the required bundle is detectable, not a silent gap.