| name | ctx-prompt-audit |
| description | Audit prompting patterns. Use periodically to help users improve prompt quality and reduce clarification cycles. |
Analyze recent session transcripts to identify prompts that led to
unnecessary clarification back-and-forth.
Before Auditing
- Check for session data: look in the journal directory for
transcripts to analyze
- Need at least 3 sessions: fewer than that gives too small a
sample; tell the user to try again later
- Confirm scope: if the user specifies sessions or a date
range, use that; otherwise default to the 5 most recent
When to Use
- Periodically to help users improve their prompting
- When the user asks for feedback on their prompting style
- After noticing many clarification cycles in recent sessions
- After a session with unusually high back-and-forth
When NOT to Use
- Immediately after a user's first session (not enough data)
- When the user is frustrated; coaching lands poorly when someone
is already annoyed
- Unsolicited; only run when the user invokes it or explicitly
asks for feedback
Usage Examples
/ctx-prompt-audit
/ctx-prompt-audit --sessions 10
/ctx-prompt-audit 2026-01-24
Data Sources
Session transcripts are stored in the journal:
| Source | Format |
|---|
| Journal directory | Exported session journals (richer) |
Journal entries contain full turn-by-turn conversation and are
the best source for pattern detection.
Process
- Gather transcripts: read 3-5 recent sessions from the
journal
- : isolate the human turns
