Show HN: Vondet – A planning board Claude keeps, so you don't have to
Hi HN, Vondet is a planning board, but you don't write on it. Claude writes to Vondet via an MCP connection. As I worked on my product with Claude, my Markdown files gradually piled up. There were files like “beta plan”, “v1 plan”, and “development plan v0.5.” I asked Claude to tidy them up. It created a new file “next-milestone plan v0.1” Haha. I spent too much time trying to remember what I planned. So I built a tool to keep plans and decisions in one place. It's ready for Claude to refer to i
Read original source
Source record
Recorded metrics
points · 1 votes
2026-11-07 16:45:26.663Z
cumulative since publication
Research analysis
What changed
Source account: Hi HN, Vondet is a planning board, but you don't write on it. Claude writes to Vondet via an MCP connection. As I worked on my product with Claude, my Markdown files gradually piled up. There were files like “beta plan”, “v1 plan”, and “development plan v0.5.” I asked Claude to tidy them up. It created a new file “next-milestone plan v0.1” Haha. I spent too much time trying to remember what I planned. So I built a tool to keep plans and decisions in one place. It's ready for Claude to refer to i
Version & cost evidence
Source votes: 1 votes (Nov 7, 2026 UTC; cumulative since publication)
Who is affected
Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.
Missing comparison points
Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.
Migration check
Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.