{"slug": "codemyspec-lovable-for-engineers-who-care-about-the-code", "title": "CodeMySpec – Lovable for engineers who care about the code", "summary": "CodeMySpec has launched a full-lifecycle AI development platform for Phoenix applications that integrates requirements, specs, architecture, code, tests, and verification into a single dependency graph. The tool addresses a documented pattern where AI-assisted codebases show 60% less refactoring but 48% more duplication and a three-month velocity cliff, by providing a structured harness around AI coding agents. The platform is free during early access and requires users to bring their own model provider and API keys.", "body_md": "### Full-lifecycle platform, not a point tool.\n\nRequirements → specs → architecture → code → tests → verification. One graph, one system. Every other tool owns a single phase and assumes you'll glue the rest together yourself.\n\n01// the_harness\n\nEnd-to-end specs, code, tests, and verification, Phoenix-native. CodeMySpec is the harness around your AI coding agent, so the code you ship still makes sense in two years.\n\n02// the_frame\n\nThe hard part is what happens next. Codebases built with AI assistance are showing 60% less refactoring, 48% more duplication, a three-month wall where velocity drops off a cliff.\n\nEfficient technical debt machines. The problem isn't the model. It's the missing harness: no specs, no architecture, no verification, no lifecycle. Prompting is praying.\n*That's the gap CodeMySpec fills.*\n\n03// how_it_works\n\nCodeMySpec tracks every artifact your Phoenix app needs (specs, tests, implementations, BDD scenarios, QA results) on a single dependency graph. Call\n```\nget_next_requirement\n```\n\n. Do one thing. The graph moves forward.\n\nStory interview. The Product Manager agent asks what you want and writes it as markdown with acceptance criteria.\n\nMap stories to Phoenix contexts. Validate the graph. No cycles, no cross-context leaks.\n\nspec-writer drafts component specs. test-writer generates ExUnit from assertions. TDD, the way you know it.\n\ncode-writer writes to pass the tests. Continuous mode walks the graph until it satisfies every requirement.\n\nUser-facing behavior captured as BDD scenarios in the Spex DSL, generated from acceptance criteria.\n\nQA agent opens a real browser via Vibium, drives the app, takes screenshots, files issues when reality diverges.\n\nIt's the harness OpenAI spent six months building for Codex, productized for teams that don't have OpenAI's infrastructure team.\n\n04// differentiators\n\nRequirements → specs → architecture → code → tests → verification. One graph, one system. Every other tool owns a single phase and assumes you'll glue the rest together yourself.\n\nSpecs are plain markdown. Tests are standard ExUnit. The plugin works with Claude Code today and whatever agent wins next year. You pay Anthropic or OpenAI directly. CodeMySpec doesn't arbitrage your token spend.\n\nGeneric AI tools blow through Phoenix contexts. They generate Ruby syntax in Elixir files, regress 1.7 codebases to 1.6 templates, and write defensive code that fights let-it-crash. CodeMySpec treats contexts, LiveView, Ecto, and OTP as first-class primitives, and respects how Phoenix is built.\n\nEvery spec produces acceptance criteria and generated tests. The QA agent drives the live app with a real browser, not a mock. You know the feature works before you ship it, not after the alert fires.\n\n*\"The agent is commodity. The harness is the differentiator.\"*\nCodeMySpec is the harness, ready to use, purpose-built for Phoenix.\n\n05// the_money_shot\n\nUnit tests pass. BDD specs pass. Then the QA agent opens a real browser, clicks through the flow a user would take, and finds the bug anyway. That's the loop no other AI coding tool has.\n\n06// proof\n\nMulti-context Phoenix app with Google Ads, Google Analytics, Facebook, and QuickBooks integrations. Built end to end with CodeMySpec. The codebase itself is the case study.\n\nProduction client app built with CodeMySpec methodology. In UAT March 2026. Real customers, real uptime.\n\nThe requirement graph you use is the requirement graph the product tracks itself against. The recursion is the proof.\n\n07// objections\n\n08// pricing\n\nCodeMySpec is free during early access. We'll price server-side platform features per-seat once we hit 1.0.\n\nYou bring your own model provider and keys. We never charge a markup on your tokens.\n\n09// install\n\nTwo commands. No signup gate. See the harness for yourself.\n\nWe can't find the internet\n\nAttempting to reconnect\n\nSomething went wrong!\n\nAttempting to reconnect", "url": "https://wpnews.pro/news/codemyspec-lovable-for-engineers-who-care-about-the-code", "canonical_source": "https://codemyspec.com/products/code-my-spec", "published_at": "2026-05-26 11:06:10+00:00", "updated_at": "2026-05-26 11:38:50.856847+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "ai-products", "ai-startups", "ai-infrastructure"], "entities": ["CodeMySpec", "Phoenix"], "alternates": {"html": "https://wpnews.pro/news/codemyspec-lovable-for-engineers-who-care-about-the-code", "markdown": "https://wpnews.pro/news/codemyspec-lovable-for-engineers-who-care-about-the-code.md", "text": "https://wpnews.pro/news/codemyspec-lovable-for-engineers-who-care-about-the-code.txt", "jsonld": "https://wpnews.pro/news/codemyspec-lovable-for-engineers-who-care-about-the-code.jsonld"}}