roadmap

name	roadmap
description	The company-building roadmap: staged milestones from idea to scale. Use for "where am I", "what's next for the company", "show the roadmap", "what should the business do next", marking milestones done, or planning the next company stage. Today's task list is DAILY; this is the months-long path.

Roadmap: The Company-Building Path

Founders know how to work hard; they rarely know what order company-building goes in. The roadmap is the staged path from idea to a functioning company, kept in memory/roadmap.md, checked off on evidence, never on vibes.

The file

memory/roadmap.md is created from memory/_templates/roadmap.md (during onboarding, or the first time this skill runs). It holds stages in order: Idea → Setup → Identity → Build → Go-to-market → Launch → Scale → Mature. Each stage is a checklist of steps. Each step carries:

• a status: locked (prerequisite not met), available (can start now), in-progress, or done
• an evidence line: what proves it is done (a file, a metric row, a decision entry)
• an owner class: which request class executes it (BUILD, GROW, SELL, DESIGN, LEGAL, STACK, FINANCE…)

Status rules (all MUST)

1. A step is marked done ONLY when its evidence exists and you just re-read it. Point to the evidence in the same line: "done (see memory/decisions.md 2026-07-02)". Never check off on the founder's word alone without noting that as the evidence.
2. A locked step becomes available the moment its prerequisites are all done. Say so when it happens: unlocks are motivating.
3. Steps are editable. Founders skip steps legitimately (already incorporated, no visual brand needed). Skipping gets a one-line reason in place of evidence, status done (skipped: reason). The roadmap serves the founder, not the other way around.

"Where am I?" / "show the roadmap"

1. Read memory/roadmap.md. If it doesn't exist, offer to create it now from the template, shaped to memory/venture.md and the starter template's roadmap emphasis, with already-evidenced steps pre-marked done.
2. Report: current stage, steps done vs total per stage (Build 3/5), the next 3 available steps with their owner class and a one-line why-this-matters, and anything in-progress that has stalled (no matching open loop or no activity in 14 days).
3. End with ONE recommended next step and the reason. A roadmap reading that doesn't end in a next action is decoration.

"Start the next step" / launching a step

1. Mark the step in-progress and add it to memory/open-loops.md in ruthless format (concrete next action, owner, due date).
2. Route the work to the step's owner class and follow that skill. The step is context, not a substitute for the skill's own workflow.
3. Irreversible or paid steps (incorporation filings, domain purchase, going live on payments) still follow §3.3: confirm first, log [external] after.

The weekly scan (called from the daily skill's weekly review)

1. For every in-progress step: check whether its evidence now exists. Yes → mark done, announce in one line. No, and no open loop tracks it → flag it as stalled.
2. Recompute unlocks: any locked step whose prerequisites are now done becomes available. Announce new unlocks.
3. Surface the next available step alongside the weekly ONE thing. If the founder's priorities and the roadmap disagree, say so once, plainly; the founder decides.

Bounds

• The roadmap never auto-executes steps. It routes; the founder green-lights.
• Stage skipping is allowed but gets one honest pushback if the skipped stage is load-bearing (launching with no identity stage: fine; scaling with no launch: worth one sentence).
• This file is founder data. shotgun-upgrade never touches memory/roadmap.md.

Memory hooks

• Step marked done → one line in memory/changelog.md.
• Stage completed → one line in memory/journal.md; celebrate in one line, then point at the next stage.
• Roadmap restructured (steps added/removed) → note the why in memory/decisions.md if it reflects a strategy change.