The Future of Specification: When the RFC Is the Code
The line between specification and implementation is disappearing. The developer who writes the best specification will ship faster than the one who types the fastest code.
The line between specification and implementation is disappearing. The developer who writes the best specification will ship faster than the one who types the fastest code.
A single document that works as an RFC for engineers and as a prompt for agents. It's not a compromise - it's the better version of both.
RFCs assume the reader knows the project. Agents know nothing. Externalizing implicit context is the difference between perfect code in the wrong architecture and code that actually fits.
RFCs are static documents. Prompts are interactive conversations. When you combine the discipline of one with the flexibility of the other, that's where the magic happens.
Without clear acceptance criteria, the agent doesn't know when to stop. The result is gold-plating or incomplete delivery - the same problems humans have, amplified.