Show HN: SpecDeck – Bring coding agent decisions back into the spec
Writing good specs is hard. You don’t know everything upfront and it’s impossible to write every little detail in the spec. Much of my job as a developer has been to treat specs as intent, and fill out the blanks in the code and use the code reviews as a way to question those decisions. But as coding agents have started to produce much more code, the decisions that actually affect the product are getting harder to find. So I created SpecDeck. It helps everyone on the team write specs and hand th
阅读原始来源
来源记录
指标快照
points · 2 votes
2026-10-31 03:15:04.458Z
cumulative since publication
研究分析
变化记录
来源描述：Writing good specs is hard. You don’t know everything upfront and it’s impossible to write every little detail in the spec. Much of my job as a developer has been to treat specs as intent, and fill out the blanks in the code and use the code reviews as a way to question those decisions. But as coding agents have started to produce much more code, the decisions that actually affect the product are getting harder to find. So I created SpecDeck. It helps everyone on the team write specs and hand th
版本与成本证据
来源票数: 2 votes (2026年10月31日 UTC; cumulative since publication)；前次同口径记录为 2（2026年10月30日 UTC），两个观测值不等于需求增长。 可供比较的近期同类记录：“Show HN: Cinnamon – a household AI agent with shared context and memories” (Show HN, 2026年11月6日)；“Show HN: I asked HN about AI agentic setups, here are 750 of the comments mapped” (Show HN, 2026年11月6日)。主题相近仅用于导航，未核验其是否属于同一需求或独立证据。
适用与受影响对象
先明确变化影响的现有工作流，再判断是否升级。发布热度不证明效果提升；接口、价格或可用性变化也可能增加迁移工作。
缺失的比较信息
待补齐：新旧行为、受影响套餐与地区、生效时间、兼容性、回退路径及同一工作量下的成本。
采用与迁移验证
保存发布或政策原文，对新旧方案运行同一个任务并比较结果与完整账单；若涉及停服，先核验截止时间再安排迁移。