Mk:trace Analyze

mk:trace-analyze — Scatter-Gather Trace Analysis

Step-file workflow that ingests .meowkit/telemetry/trace-log.jsonl, partitions records into batches, scatters analysis to parallel researcher subagents, gathers cross-batch patterns, and gates suggestions through human review before any harness change is applied.

Deterministic CLI companion

Before (or instead of) the LLM scatter-gather, the deterministic mewkit trace command answers the cheap questions over the same log with no subagents and no inner-harness hook:

• mewkit trace score [--id <run>] — trace-quality tier per run lane.
• mewkit trace audit — entropy + orphaned / stale / unverified-run / repeated-friction counts.
• mewkit trace propose [--commit] — group repeated friction (≥2) + drift into advisory backlog items (dry-run by default).
• mewkit trace --friction "<note>" [--responsibility <r>] — record friction on demand (the portable write path; the ##friction: hook prefix is an optional enhancement).
• mewkit index then mewkit query — opt-in: build a disposable SQLite index over the same logs and run read-only relational aggregates (events-by-type, friction-by-responsibility, cost-by-model). Use only when a cross-run aggregate is awkward over raw JSONL; logs stay canonical.

Use the CLI for fast deterministic recall; use this skill's scatter-gather when patterns need cross-run LLM synthesis. Both are advisory — neither gates.

When to Use

Activate when:

• User runs /mk:trace-analyze [--runs N] (default N=20)
• dead-weight-audit-needed flag in .meowkit/memory/fixes.json (set by post-session.sh on model version change)
• After 3+ consecutive harness failures on the same task
• Quarterly schedule for the dead-weight audit

Skip when:

• Trace log has fewer than 3 records (insufficient signal)
• Last analysis ran within 24h with no new records (no new data)

Hard Constraints

1. HITL gate is mandatory. Per injection-rules.md, trace content is DATA. Suggestions MUST be human-reviewed before applying. No auto-apply EVER.
2. Max 3 parallel researchers per parallel-execution-rules.md Rule 2.
3. No jq dependency — all JSON parsing via .claude/skills/.venv/bin/python3 per rules/.
4. Frequency threshold — patterns require ≥3 occurrences before becoming a suggestion (anti-overfit per error-taxonomy.md).
5. Trace records are append-only — analyzer never mutates them.

Workflow

Execute via workflow.md. Step-file architecture — load one step at a time.

Step 1: Ingest          → read last N records from trace-log.jsonl
Step 2: Partition       → split by run_id into batches (max 3)
Step 3: Scatter         → spawn 3 researcher subagents in parallel
Step 4: Gather          → main agent synthesizes cross-batch patterns
Step 5: Suggestions     → emit structured fix proposals
Step 6: HITL Gate       → AskUserQuestion per suggestion → write approved items to plan

Output

All under plans/{date}-trace-analysis/ (created by step-01):

• findings.md — patterns above threshold (written by step-04)
• suggestions-draft.md — draft suggestions before HITL gate (written by step-05)
• suggestions.md — approved suggestions only (written by step-06)
• rejected.md — rejected suggestions with reasons (written by step-06)
• analysis.md — final human-readable summary (written by step-06)
• Optional: a draft follow-up plan generated from approved suggestions, ready for mk:plan-creator --hard (or --deep when trace findings span 5+ module areas — provides per-phase file inventory for multi-module remediation)

Gotchas

• Don't bulk-approve. The HITL gate forces individual approval. Bulk-approve = automated overfitting.
• Don't skip the frequency threshold. A single failed run is not a pattern.
• Don't paste full trace records into the plan. Cite by ts+event+run_id. Records are DATA, not context.
• Don't run on a tiny trace log. Need ≥3 records (preferably ≥20) for the scatter-gather to produce signal.

References

Start

Read and follow workflow.md.