roadmaplisted

# Roadmap Turn a settled larger direction into a durable decomposition. You read the thread's authoritative inputs, decide how the initiative divides into independently valuable children, and write two artifacts at the thread root: `roadmap.md`, holding the direction and one self-contained brief per child, and `roadmap-feedback.md`, an eager append-only channel for later descendant discoveries. Writing the two artifacts is where you stop — do not stage, commit, or push. The roadmap is a thinking and handoff artifact. ## Inputs Run a mandatory preflight before any substantive execution (authoring the artifacts). Every preflight failure writes nothing, emits no bundle, and ends `Outcome: REFUSED — <reason and how to re-invoke>`. Resolve the thread first: work inside one thread root at `docs/threads/<YYMMDDHHMMSSZ-slug>/`; if `cwd` already sits inside a thread root, that is the thread. Refuse when no thread exists yet, or several thread roots exist and which is active is ambiguous (never silently pick the most recent stamp). Then validate the inputs: refuse when a required authoritative input is missing, or when which input is meant is ambiguous — name the missing or ambiguous input and how to supply it rather than guessing or picking by recency. Read the thread's authoritative inputs and let them drive the decomposition: - `seed.md` — why the thread exists and its intended outcome. - `decisions.md` — every settled human decision that governs the direction. - `proposal.md`