Resources

Prompts Used

Hydrate planning docs

Take all of the research in research/* and apply it to our *.md docs

Expand roadmap steps

/do-parallel for each step in roadmap.md, write it in steps/{name}.md. use the research in research/*

Confidence check

Read through the roadmap and the steps, respond with a confidence score 1-100 of whether or not you think we will succeed, then list things that will make us more confident

Files Created

None

#0042026-02-07

Hydrating the Roadmap

The Goal

This note is about detailed planning and gut checking. Two questions:

  1. Can we get a detailed roadmap?
  2. Are we confident we can accomplish it?

Step 1: Hydrate the Planning Docs

With research complete in research/*, apply it back to the planning documents:

Take all of the research in research/* and apply it to our *.md docs

This updates vision.md, architecture.md, and roadmap.md with validated approaches, concrete numbers, and working code patterns.

Step 2: Expand Roadmap Steps

Each step in the roadmap needs detailed implementation guidance. I used /do-parallel to expand all steps simultaneously:

/do-parallel for each step in roadmap.md, write it in steps/{name}.md. use the research in research/*

This creates a detailed implementation guide for each step, incorporating the research findings. The steps/ directory becomes a collection of actionable implementation documents.

Step 3: Confidence Check

With the detailed roadmap and expanded steps, ask for a gut check:

Read through the roadmap and the steps, respond with a confidence score 1-100 of whether or not you think we will succeed, then list things that will make us more confident

Methodology: The Confidence Check

There are many ways to do this confidence check:

  • Ask for gaps — What needs more specification?
  • Ask for unknowns — What needs more research?
  • Ask for spikes — Do we need smaller experiments to validate assumptions?
  • Ask for risks — What could go wrong?
  • Ask for dependencies — What are we waiting on?

In this example, I kept it simple — just hunted for a confidence score and a list of things that would increase confidence. When the score came back high, I accepted it and moved on. This is risky. AI is often overconfident. A proper confidence check using the approaches above would surface more issues.

What I Did

I ran the confidence check, got a high score, noted the suggestions for improvement, and moved on. The suggestions went into backlog items and future research topics.

Next Steps

Start building.