The Unified Document: Writing for Humans and Agents at the Same Time
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.
Read article
Introduction
Software engineer,
builder, and
Elixir enthusiast.
Recent Articles
Shared Context: What RFCs Assume and Agents Need to Hear
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.
Read article
Where the Prompt Goes Beyond the RFC: Feedback Loops
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.
Read article
Acceptance Criteria: When the Agent Knows It's Done
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.
Read article
Interfaces and Contracts: How Agents Respect Boundaries
Without explicit contracts, each agent invents its own interface. The result? Systems that work alone but break together.
Read article
Work
-
- Company
- EasyMate AI
- Role
- Software Engineer
- Date
-
- Company
- Iago Cavalcante Consultoria
- Role
- Software Engineer
- Date
-
- Company
- Zarv Inc.
- Role
- Software Engineer
- Date
-
- Company
- Truelogic
- Role
- Software Engineer
- Date
-
- Company
- IdopterLabs
- Role
- Software Engineer
- Date