Use when you want to understand why you got a particular response, when something feels off and you need to diagnose the system's logic, when you're curious what influenced specific advice or framing, or when you want to learn how the Judgment Engine makes decisions. Provides transparency into reasoning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/judgment-engine-virelan:judgment-tracebackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A skill for understanding why the system produced its last output—the decisions, postures, and files that shaped it.
A skill for understanding why the system produced its last output—the decisions, postures, and files that shaped it.
Judgment Traceback provides transparency into the system's reasoning:
Restate what you asked or what triggered the previous response.
What mode, skill, or posture was active?
What context was loaded?
What choices did the system make?
What would change the output?
### Input Echo
[What you asked or what triggered the response]
### Active Configuration
**Mode/Skill**: [What was running]
**Posture**: [If any role was active]
**Context files**: [What was loaded]
### Decision Trace
**Approach chosen**: [What the system did]
**Why this approach**:
- [Reasoning factor 1]
- [Reasoning factor 2]
**Alternatives considered**:
- [Option A] - Discarded because [reason]
- [Option B] - Discarded because [reason]
**Key constraints**:
- [What limited the choices]
**Assumptions made**:
- [What the system assumed]
### Counterfactuals
**Would change if**:
- [Different mode]
- [Additional context]
- [Different phrasing]
**To get different output, try**:
- [Specific suggestion]
- [Another approach]
Your input: "This feels too easy"
Active: Default Interaction Posture
Context: Core Posture (fluency masks fragility)
Decision: Suggested Max posture
Why: "Too easy" triggered fluency warning.
System interpreted as potential fragility masked
by smooth language. Max's challenging stance
appropriate for testing what survives pressure.
Could change if:
- You specified "this solution is simple and robust"
- You asked for Herald (amplifying existing clarity)
Your input: "Review this draft"
Active: Default Interaction Posture
Context: Core Posture only
Decision: Provided inline feedback
Why: No explicit Workshop invocation. "Review"
interpreted as wanting direct feedback rather
than structured Workshop process with authorship
protection and multi-stage revision.
Would invoke Workshop if:
- "Workshop this draft"
- "Help me strengthen this without ghostwriting"
- Clear signal of wanting protected authorship
Judgment Traceback can be run on itself:
"Why did Traceback give me that specific output?"
This reveals the system's self-awareness and helps you understand how transparency itself is structured.
"Run Traceback - why did you suggest that mode?"
"Judgment Traceback on your last response."
"I want to understand why you framed it that way."
"Traceback mode - what influenced that recommendation?"
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub rjroy/wyrd-gateway --plugin judgment-engine-virelan