← ClaudeAtlas

querylisted

Query Tracework's decision replay index for why a project chose a path, what alternatives were rejected, what should be revisited, what impact a decision had, or any natural-language question about project history. Use this skill for "/tracework:query", "why did we choose this?", "为什么当时这么选", "有没有被拒绝过的方案", "revisit this decision", "auth 迁移做到哪了", "我们讨论过 rate limiting 吗", or when a coding agent needs cited decision evidence before changing architecture, contracts, prompts, schemas, or product direction.
KKenny0/Tracework · ★ 2 · AI & Automation · score 65
Install: claude install-skill KKenny0/Tracework
# Decision Replay Query This skill answers targeted project-history questions from Tracework's local decision memory. It is a thin wrapper around the deterministic decision replay helper: the script narrows evidence, and the host agent writes the final answer. Use `query` when the current task touches an existing decision, architecture boundary, rejected option, long-running risk, or product tradeoff. Use `recall` for session-start orientation; use `query` for a specific follow-up question. Git-only report fallback is not decision evidence here. If the raw record does not support the question, return the evidence gap and suggest targeted capture after the user clarifies the decision. ## Effective Facts Use the bundled helper's effective facts, correction_history, states and diagnostics. `--as-of` selects an explicit knowledge cutoff; `--end` bounds lifecycle state by work date. Query/Roadmap also accept `--start`. Do not restore retracted facts or close questions from similar wording. Accepted risks remain separate from mitigated risks. Missing captured_at limits exact as-of replay. Old reports are not rewritten; refresh a requested report through its writer. ## Scope - Intra-project by default. - Raw entries remain the source of truth. - `{vault}/raw/decisions/{project-slug}.json` is a derived retrieval index. - The helper may rebuild an in-memory index from raw entries when no saved index exists, but this skill does not write new memory. - Do not use git history, ex