Epic framework guides clear coding agent instructions to reduce bugs
The EPIC Framework for Spec-Driven Development
Software Engineering
Summary
Sometimes when people write instructions for coding agents—software that writes code for them—small word choices cause confusion and mistakes. The authors studied many open-source projects to find what makes good instructions and created the EPIC framework with 40 best practices that help developers write clear and complete specs. Using EPIC helps teams make fewer bugs and attract more contributors. It guides developers to be very clear so coding agents don’t make wrong guesses.
What this means in practice
- •For software development teams: Improve task and plan writing clarity for coding agents to reduce bugs and attract more contributors in collaborative projects.
- •For software project managers: Use a structured checklist from EPIC to ensure software specifications are clear and sufficient before agent coding begins, preventing costly rework.
Authors
Bruno Claudino, Ruizhe Xing, Yuanhao Zuo, Tyler Menezes, Anita Sarma, Kostadin Damevski, Zixuan Feng
Abstract
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.