knowledge-mcp: Skill for Claude Code

CREATE-A-TICKET — what must be true before a ticket exists

THE RESEARCH GATE (absolute, blocking)

NO TICKET IS CREATED until, in order:

1. A RESEARCHER PASS answered: every open question the ticket would carry, the high-level design (which existing seams and idioms the work binds to), and — for a defect — the root cause OBSERVED at the mechanism level (in source or reproduction). A mechanism nobody observed enters the ticket labeled "unproven" or the ticket ships symptom-only; your own inference gets the same bar as any inbound claim. A live investigation already running on the same mechanism IS the researcher pass — the ticket waits for it.
2. A PRIOR-DECISION SWEEP over every touch point the ticket names, checking the proposed design against each recorded decision.
3. CONFLICTS ROUTED to the user as TICKET-GAPS before the ticket freezes — a design/decision disagreement is never resolved silently in either direction.
4. THE DECISION RECORD UPDATED with the user's ruling in the same breath as the ticket — a ticket contradicting a standing decision record is a landmine.
5. FOR DEFECT TICKETS: A ROOT-CAUSE CHECK MINTED FIRST — a check capturing the root-cause class exists in the checks graph, authored to the storing bar (fired on a bad fixture, silent on a good one; ast_pattern where mechanical, llm_only where it needs judgment — llm_only is exclusive with fixtures). A root cause that genuinely cannot be a check is surfaced to the user WITH the ticket as an explicit exception — never self-exempted.

The one exception: a symptom-only ticket for an ACTIVE INCIDENT may be created immediately to carry mitigation state — its mechanism section says UNKNOWN, the researcher pass amends it before any implementation dispatch, and the root-cause check is minted with that amendment.

The tell you are about to violate the gate: a ticket description carrying your own unverified mechanism as fact, an open question left for the planner, or a design no researcher checked against the decision graph.