▸ 00 · the_harness_platform ●v0.9 · early_access _

Run your entire software business from your terminal.

CodeMySpec is a platform of harnesses for the technical founder shipping a real product. Build it. Market it. Support it. Each harness is a Claude Code plugin that turns one of those jobs from chat-window vibes into a system with a cadence. Use one. Use all of them. Add the next when the bottleneck moves.

▸ Install a harness Talk to John →

~/codemyspec · technical founder/day

// 09:14 · plan the day

▸/daily-plan

→ 3 activities · awareness loop

// 10:32 · build the product

▸mix spex --continuous

→ spec · test · code · all green

// 14:08 · market the product

▸/marketing-strategy --review

→ bottleneck holds · keep shipping

// 16:45 · feedback

▸/marketing-stack --validate

→ 17/17 healthy

▸

01// the_frame

You don't have a team.
You have to BE the team.

Technical founders aren't running a smaller version of a software company. You're running every department of one. The product team. The marketing team. The support team. The ops team. Each of those is a real job inside real companies — staffed by engineers who specialized, marketers who specialized, supporters who specialized. You get to be all of them this week.

The mistake is trying to do all of it the way a team would, in your head, alone — chat windows, scattered notes, four AI tools that each forget what you told them yesterday. The fix isn't another SaaS subscription or another to-do list. It's the harness — the discipline a real team uses to make sure work compounds instead of evaporates. CodeMySpec gives you that harness, one domain at a time.

02// the_platform

Two harnesses today.
More as we need them.

Built in the open by a technical founder who's using each harness as he ships it. CodeMySpec the product was built with /codemyspec — Phoenix-native today, broader stack support next. Its marketing runs on /marketmyspec. The next harness ships when the bottleneck moves.

/codemyspec

// engineering harness

Build the product.

▸ Production

Specs as the source of truth. Requirements graph. Six subagents. BDD scenarios in standard ExUnit. Browser QA against the running app. Phoenix-native today — contexts as AI boundaries, OTP-aware, let-it-crash respected — broader stack support next. The harness that built this product.

→ See CodeMySpec

/marketmyspec

// marketing harness

Market the product.

▸ Early Access

8-step strategy interview with research agents. A /daily-plan that picks today's three activities. 17 infrastructure recipes. Adapts to any business — granite countertops to B2B SaaS to Phoenix indie. The harness marketing this product right now.

→ See MarketMySpec

/portmyspec

// support harness

Support the product.

○ Planned

Coming when the bottleneck moves. Built when 25 customers need it; not before. No date promised, no waitlist — it'll be here when it earns its place.

→ Coming next

03// who_its_for

Built for the founder doing every job.

If you're a technical founder shipping software and there's nobody else in the building, you're our beachhead. If you run an Elixir agency delivering across multiple clients, the same harnesses become shared artifacts your team and your clients can both inspect — specs in the repo, MCP across the team.

▸ Primary

Solo technical founder

1 person· 4+ jobs· already inside Claude Code

Reads code. Ships product. Knows the codebase is starting to slip under AI-generated volume. Wants a marketing system without hiring a CMO. Wants the work to compound instead of evaporating every Monday.

"I want to run a software business by myself. The LLM does the labor. I do the thinking."

Start with one harness →

▸ Secondary

Elixir agency

5-30 people· 3-10 client projects· CTO sets the AI policy

Phoenix contexts as shared boundaries. Specs as artifacts the engineer hands the client. MCP servers exposing the same source of truth to every Claude Code session on the team. Onboarding is high-touch today by design.

"I need a defensible answer when a client asks how we prevent AI from ruining the codebase."

Talk to John →

04// proof

Real founder. Real apps.
Real recursion.

featured · open-sourcing soon

MetricFlow

Multi-context Phoenix app. Phoenix contexts, Ecto schemas, OTP supervision, ExUnit. Google Ads, GA, Facebook, QuickBooks integrations. Built end to end with /codemyspec. The codebase is the case study.

40

commits

13d

end-to-end

5

integrations

▸ github.com/Code-My-Spec/metricflow

production · uat

Fuellytics

Production client app built with the CodeMySpec methodology. In UAT March 2026. Real customers, real uptime.

▸ Case study

recursive · self-hosted

codemyspec.com itself

This site, the product pages, the methodology page, the daily Reddit comments — all output of the harness platform marketing this site. The marketing harness is marketing the marketing harness.

▸ See the repo

JD

Built by John Davenport — six years on r/elixir, working Phoenix engineer, taught himself entrepreneurship from the internet. Building the engineering harness he needs to ship. Building the marketing harness he needs to find users. Open. In real time.

05// pricing

Free during early access.

early access · 2026

$0/ month

Each harness is free during early access. Server-side platform features will be priced per-seat once we hit 1.0. You bring your own model provider and keys — we never charge a markup on your tokens. Same arrangement on every harness.

✓ Unlimited specs, daily plans, BDD scenarios
✓ All harnesses · all skills · all recipes
✓ BYO model · BYO keys · no token markup
✓ Specs and artifacts live in your repo · no lock-in
✓ Works with Claude Code today

06// objections

Questions founders actually ask.

Q.01Is this a CodeMySpec thing or a different product? +

CodeMySpec is the company and the first product — the engineering harness. MarketMySpec is the second product — the marketing harness, now living at its own domain (marketmyspec.com). Both run under one platform: same Claude Code plugin model, same BYO-model commitment, same recursive proof. Future harnesses follow the same pattern.

Q.02I'm a technical founder, not a software business owner. Does this still work? +

That's exactly who we built it for. The harnesses give one person the discipline a real team would have without making you hire one. Technical founder is the primary audience — the person who can read the specs, ship the product, and is now also the marketer, the support team, and the on-call engineer.

Q.03I run an Elixir agency. Does this fit our delivery model? +

Yes — specs as deliverables, MCP servers exposing one source of truth to every engineer's Claude Code, Phoenix contexts as shared boundaries across client projects. CTO-led adoption, one project at a time. Onboarding is high-touch today by design — book time with John.

Q.04Why two products instead of one? +

Different bottlenecks. Engineering and marketing are completely separate concerns; mashing them into one product would help neither. Same brand, same harness pattern, separate scope. You can install just the one you need.

Q.05Is this open source? +

Specs are markdown in your repo. Generated tests are standard ExUnit — no proprietary test runner, no DSL you have to learn. The Claude Code plugin code is open and inspectable. The platform service that backs team-features and persistence is closed-source, paid post-1.0.

Q.06What if you build something better tomorrow? +

You own the artifacts. Specs, tests, marketing files, daily plans — all live in your repo as markdown. No lock-in. The platform brings continuity across them; you can always walk.

Q.07What stack do I need to use this? +

The engineering harness is Phoenix-native today, by design. Phoenix contexts are already the right AI boundary — generic AI tools blow through them, generate Ruby syntax in Elixir files, regress to Phoenix 1.6 templates in 1.7 codebases, and add defensive code that fights let-it-crash. CodeMySpec respects how Phoenix is actually built. Other stack support on the roadmap. The marketing harness is stack-agnostic — it's about your business, not your codebase.

Q.08How much time per week? +

5-10 hours/week to keep both harnesses running well. Heavier the first month — strategy interviews, infrastructure wiring, the spec round-trip dialed in. Lighter after that. Three activities a day from /daily-plan is the cap; the harness fights you if you try to do more.