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. ## Workflow ### Step 0: Resolve Config and Scope Resolve the vault path using the standard Tracework config resolution. The bundled decision graph helper performs that resolution while building the derived index: ```bash python <this-skill>/scripts/decision_graph.py build --cwd "$PWD" ``` If the helper cannot resolve config, resolve manually: 1. Check `.tracework/config.yaml` in project root 2. Check `~/.tracework/config.yaml` 3. If neither config exists, ask the user to run `/tracework:cold-start-interview` or configure `knowledge_vault` Determine scope from the user's request: - **Default**: current project, all available weeks - **Cross-project**: if the user explicitly asks, read all `{slug}.json` files - **Date range**: if the user specifies (e.g. "from April", "last month"), filter accordingly ### Step 1: Gather