发表机构
Virginia Commonwealth University; Oregon State University; CodeDay（弗吉尼亚联邦大学; 俄勒冈州立大学; CodeDay）
机构由 AI 辅助整理，请以论文原文为准。AI 中文总结
针对规范驱动开发中规范质量难以评估的问题，提出EPIC框架，含10个维度40项实践，依据ISO标准分析114个仓库得出，能帮助开发者提前填补规范空白。
AI 中文摘要
我们访谈的一位从业者表示，他们的团队在给编码智能体下达指令时会写“必须”而不是“应该”，因为智能体可能会将“应该”视为可选项。措辞上的细微选择很重要，因为智能体常常会用自身的假设来填补指令中的空白。规范驱动开发（SDD）要求开发者在智能体编写代码之前先编写规范、计划和任务。SDD框架为这些工件提供了模板，但这些模板并不能帮助开发者判断他们是否写得足够充分或足够清晰。我们研究了优秀的SDD规范应包含哪些内容。我们依据ISO/IEC/IEEE 29148标准对114个开源SDD仓库的工件进行了评分，并从得分最高的仓库中提炼出实践方法。由此产生的框架EPIC包含10个质量维度下的40项实践，指导开发者在面向编码智能体的规范、计划和任务中明确表达期望与决策。大多数SDD从业者（N=15）认可了每一项实践。规范质量排名前三分之一的仓库在缺陷修复上花费了11.8%的提交，而排名后三分之一的仓库这一比例为20.4%；前者贡献者数量的中位数是后者的4倍。开发者可以使用EPIC在智能体行动之前发现并填补规范中的空白。
英文摘要
One practitioner we interviewed said their team writes "must" instead of "should" when instructing a coding agent, because the agent may treat "should" as optional. Small wording choices matter because agents often fill gaps in their instructions with their own assumptions. Spec-driven development (SDD) asks developers to write a specification, plan, and tasks before the agent writes code. SDD frameworks provide templates for these artifacts, but the templates do not help developers judge whether they have written enough or clearly enough. We studied what good SDD specifications contain. We scored the artifacts of 114 open-source SDD repositories against ISO/IEC/IEEE 29148 and derived practices from the highest-scoring ones. The resulting framework, EPIC, has 40 practices in 10 quality dimensions that guide developers in making expectations and decisions explicit in specifications, plans, and tasks for coding agents. The majority of SDD practitioners (N=15) endorsed every practice. Repositories in the top third of specification quality spent 11.8% of their commits on bug fixes, compared with 20.4% in the bottom third, and had a median of 4x as many contributors. Developers can use EPIC to find and fill the gaps in a specification before the agent does.
