Process-guided AI development for Phoenix
Keep your architecture. Let AI do the typing.
CodeMySpec wraps LLMs in strict workflows, Phoenix contexts, and one design doc per file. You stay in charge of the system. The model just fills in the blanks.
LLMs invent architecture
Give an LLM a vague brief and it happily makes up its own layers inside your app. It compiles. It passes tests. And it quietly ignores your Phoenix contexts.
The manual process works
With Markdown, Git, and a good model you can keep things under control: one design doc per file, strict context boundaries, tests first. It's just a lot to juggle by hand.
CodeMySpec automates the boring parts
CodeMySpec turns that manual workflow into a workspace. Stories, contexts, designs, tests, and sessions all live in one place, with AI running inside the guardrails. The AI generates code. You review architecture. The process catches bugs before they compound.
How It Works
CodeMySpec replaces unstructured AI prompting with a six-phase development process. Each phase produces artifacts that the next phase verifies against. Nothing ships without passing through the full loop.
Stories & Requirements
The Product Manager MCP interviews you about what you're building and generates user stories with testable acceptance criteria. Each criterion becomes a contract: if the acceptance criteria pass, the feature is done.
Architecture & Design
The Architect MCP maps stories to Phoenix contexts with validated dependencies. Each context gets a design document that defines its schemas, repositories, and services. The dependency graph catches circular references before a single line of code is written.
BDD Specs, Tests & Code
AI generates BDD scenarios from acceptance criteria, writes tests from specs, and implements code that passes them. The QA agent then tests each story against the running application with browser automation, filing structured issues for anything that doesn't match.
Proven with MetricFlow
We built a full-stack Phoenix analytics platform using this method — OAuth integrations with Google Analytics, QuickBooks, and three other platforms, multi-tenant accounts, correlation analysis, and AI chat insights. Zero human-written code. Here's what happened.
Built by a Phoenix Developer
CodeMySpec is built by John Davenport — 15 years in enterprise systems, 2 years deep in LLM-assisted development. Every feature went through the same six-phase method. The methodology isn't theoretical. It's how this product was built.
The stack is Elixir, Phoenix, and LiveView with MCP servers for AI agent orchestration. BDD specs use Gherkin scenarios that run against the live application. The architecture enforces bounded contexts with validated dependency graphs — the same patterns that Phoenix contexts were designed for.
Read the founder story or check the blog for technical deep dives.