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
阅读原始来源
来源记录
指标快照
points · 1 votes
2026-11-07 16:45:26.663Z
cumulative since publication
研究分析
变化记录
来源描述：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
版本与成本证据
来源票数: 1 votes (2026年11月7日 UTC; cumulative since publication)
适用与受影响对象
先明确变化影响的现有工作流，再判断是否升级。发布热度不证明效果提升；接口、价格或可用性变化也可能增加迁移工作。
缺失的比较信息
待补齐：新旧行为、受影响套餐与地区、生效时间、兼容性、回退路径及同一工作量下的成本。
采用与迁移验证
保存发布或政策原文，对新旧方案运行同一个任务并比较结果与完整账单；若涉及停服，先核验截止时间再安排迁移。