roadmaplisted

# Decision Roadmap Generator Reads accumulated raw entries from the knowledge vault and synthesizes them into a narrative decision roadmap — a document organized by decision threads rather than time periods. Each thread tells the story of a key decision: what triggered it, what was explored, what was chosen, what was abandoned, whether those abandonments still make sense, and which decisions were revised or superseded. Unlike weekly/monthly reports (organized by calendar period) or git history (organized by code changes), the decision roadmap is organized by **decision threads** — chains of related entries that reveal how a project's thinking evolved. ## 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. ## Workflow ### Step 0: Resolve Config and Scope Default scope is the current project across all available weeks. Start once: ```bash python <this-skill>/scripts/decision_graph.py roadmap --cwd "$PWD" --limit-threads 20 ``` This resolves config and loads/rebuilds the derived index as needed. Use the pack's thread decisions, source_entry_refs an