What if we extracted literally EVERY behavior of dev.to into Markdown? (An AI Agent Experiment)
TL;DR I am running an experiment where I forked Forem, the OSS behind dev.to, and used AI agents to extract "every single behavior" as Markdown specification documents Agents autonomously analyzed file dependencies spanning Rails Controllers, React Components, and Workers, and successfully constructed a network of specifications with bidirectional links (ULIDs) I am building a new SDD (Spec-Driven Development) toolkit called specre to make this approach possible A question for you, the reader In a large codebase like Forem, can you immediately grasp where a specific feature (e.g., inviting a member to an Organization) has an impact? Can an AI understand that efficiently and accurately? Have you ever been frustrated when an AI failed to grasp context that you thought was perfectly clear? yoshiakist / specre Atomic, living specification cards for AI-agent-friendly development. Minimal, agnostic, and traceable. English | 日本語 specre Atomic, living specification cards for AI-agent-friendly
Continue reading on Dev.to
Opens in a new tab
.jpg&w=1200&q=75)



