arXiv CS
open access
The EPIC Framework for Spec-Driven Development
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 (
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Practical Implementation Report on Introducing Spec-Driven Development Using AI Agents in Software Development PBL#622599
- The EPIC Framework for Spec-Driven Development#1216909
- AutoCompact: Learning When to Compact Context in Long-Horizon Coding Agents#1157511
- Acquiring and Verifying Repository Norms for Coding Agents#1217132
- Acquiring and Verifying Repository Norms for Coding Agents#1210358
Record · ID 1210360
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive