โ† ClaudeAtlas

prismlisted

PRISM โ€” a structured, multi-session, multi-vendor LLM-orchestrated audit and research framework (orchestration on Claude, Opus-class). Trigger when the user invokes PRISM by name or by a recognizable PRISM construct: PRISM / PRISM audit / begin a PRISM audit; a Master file or any filename matching *_master_p*.md; Prompt Strategy; the Lens Library; Vendor Selection or Vendor Triangulation; Setup probes P1โ€“P7; Monitors M1โ€“M12; Standing Principles SP-*; the Execution Envelope / Self-check / Output triple contract; Dispatch register or Dispatch shape (equivalence / split / limitation-named); the "What's next" artifact; context bands ๐ŸŸข๐ŸŸก๐ŸŸ ๐Ÿ”ด; migration handoff; the P0/P1 boundary; three-layer readiness; Update sessions or point refresh; or Setup artifacts (Decision brief / Stakeholder register / Claim inventory / Jurisdiction map). Also trigger when the user attaches a Master or Lens Library file. Do NOT trigger for generic audit, research, or prompt-engineering work that does not invoke PRISM by name or construc
Ronkupper/PRISM ยท โ˜… 4 ยท AI & Automation ยท score 77
Install: claude install-skill Ronkupper/PRISM
# 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, context-pressure framework, Setup mechanics, Library-integration mechanics, Monitors M1โ€“M12, Standing Principles, filename conventions, the atomic-prompt template, the operator-hint catalog, and missing-handoff recovery). 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