looper

{
  "name": "looper",
  "description": "Looper — a system's design contract in both directions: forward-author the product world from a raw idea, or reverse-engineer it from existing code and failure memory. `/psl` turns one experiential / semantically-fuzzy requirement (plus optional materials) into a complete Product Specification Language document — six derivation-ordered layers (Vision / Mental Model / Domain Model that must overturn the naive schema / State Machine / Workflow split into Σ facts + φ disambiguation criteria, never Step 1-2-3 / behavioral Acceptance in ask-X-get-Y form) — under a three-provenance honesty discipline (surface engine world knowledge / elicit private load-bearing slots one topic at a time with recommended lettered answers / seam everything unanswerable into Open Questions, never default-fill), a dual-track entry gate (deterministic requirements get told 'PRD suffices' instead of a fabricated world), and a hard delivery contract (never refuses for lack of info), mechanically pre-gated by verify_psl.py (rejects missing layers, named-step Workflow, non-behavioral Acceptance, absent Open Questions). `/dos-extract` deductively recovers a Design Ontology Spec (DOS): a 13-section, two-layer dos.yaml (a core model of ≤7 objects / relationships / constitutional rules / bounded contexts / agent guidelines, plus a complete `vocabulary` — every other term the team says, with kind / owner / synonyms / rejected names — whose coverage verify_dos.py --terms measures against the counted roster) + decisions.md audit trail, applying four classification judgments (object vs UI vs impl vs rule; same-object-vs-two; constitution vs policy; single vs multi context) that a naive noun-scan skips, with a mechanical pre-gate (verify_dos.py rejects UI/impl-suffixed names, undeclared relationship refs, >7 objects, a missing vocabulary layer, unplaced roster terms, empty open_questions) plus a human sign-off seam. `/invariant-extract` abductively recovers ONE Territory's □-class resident invariants from the failures it paid for (a violation is the most reliable signal an invariant exists) and deductively from code execution points, emitting a named-field invariant card (statement / strength / aspect / channel / provenance / on_violation) gated by verify_card.py (rejects no-provenance entries, auto-installed hard invariants, ◊ smuggled onto the card) — hard invariants are propose-only, entering only by human signature. psl and dos-extract are reverse twins (idea→world vs code→world) sharing one domain vocabulary; invariant-extract draws a single block's resident law from its scars and consumes dos-extract's dos.yaml. All static_only tier (structurally gated; effectiveness on held-out tasks unverified).",
  "version": "0.4.0",
  "author": {
    "name": "XRenSiu",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/XRenSiu/claude-code-forge/tree/main/plugins/looper",
  "repository": "https://github.com/XRenSiu/claude-code-forge",
  "license": "MIT",
  "keywords": [
    "psl",
    "product-specification-language",
    "product-world",
    "world-model",
    "behavioral-acceptance",
    "dos-extract",
    "invariant-extract",
    "design-ontology-spec",
    "ontology-extraction",
    "ubiquitous-language",
    "domain-model",
    "invariant-extraction",
    "abduction",
    "deduction",
    "reverse-engineering",
    "contract-extraction",
    "kaos",
    "bounded-context",
    "constitution-vs-policy",
    "static-only"
  ]
}