roadmap

Build a Markdown decision roadmap from weekly raw entries.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/KKenny0/Lode --skill roadmap-kkenny0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/KKenny0/Lode/tree/main/skills/roadmap
Command: npx skills add https://github.com/KKenny0/Lode --skill roadmap-kkenny0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Synthesizes accumulated raw entries into a narrative decision roadmap that explains why decisions were made and how they evolved.

Core Features & Use Cases

  • Builds decision threads from weekly raw entries and outputs a human-friendly roadmap organized by threads rather than time.
  • Connects decisions with evidence, abandoned alternatives, and open questions for traceability and future reassessment.
  • Uses the Decision Replay index to ground narratives in source entries and produce reproducible outputs.

Quick Start

Ask Lode to generate the decision roadmap from your vault to see the narrative of key project decisions.

Frequently Asked Questions about roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a narrative decision roadmap from raw project entries?

A narrative decision roadmap synthesizes accumulated raw entries to explain how and why project decisions evolved. It connects decisions with evidence and abandoned alternatives, organizing the output by threads rather than time for traceability and future reassessment.

How does decision replay work for understanding abandoned options in a project?

Decision replay uses a deterministic index built from weekly raw entries to connect past decisions with evidence and abandoned alternatives. This grounds the narrative in source entries, allowing you to revisit abandoned options and reassess past choices.

Can I use YAML files to structure raw entries for decision traceability?

Yes, the Skill uses YAML dependencies to process raw entries and build a Decision Replay Index. This ensures the resulting Markdown roadmap maintains full traceability back to the original source evidence and weekly inputs.

What is the best way to document how project decisions evolved across threads?

The best way is to synthesize raw entries into a thread-based narrative roadmap. This connects decisions with evidence and open questions, providing a reproducible Markdown document that explains the evolution of project choices.

Does the decision roadmap organize project history by timeline or by decision threads?

The decision roadmap organizes project history by decision threads rather than by timeline. This structure connects related decisions, evidence, and abandoned alternatives together, making it easier to understand how specific project choices evolved.