Discovery Sprint
Technical + product assessment, a prioritized roadmap, and one working spike on the highest-risk unknown.
Available for new Project
Software, shipped
honestly.
How I engage
Three formats, one bar for shipped.
Fractional CTO / Tech Lead
Shipped features, unblocked engineers, and a technical direction your team owns after I’m out.
Build Partner (AI-first)
A concrete deliverable shipped together — MVP, migration, or rewrite — with AI collaboration baked in.
How it works
A five-stage loop
for zero-rewrite shipping.
1
Discovery
One paragraph in. Constraints, users, stakes. If we can’t name the frozen-logic call, we’re not ready to spec.
2
Spec
specs/<slug>/spec.md lands first. What we’re building, what we’re not, and the shape of “done”.
3
Plan
plan.md sequences the risky bits early. Every task numbered, blocked-by set, DEVLOG format decided.
4
Build
Opus for architecture, Sonnet for features, Haiku for volume. DEVLOG appended after every work block.
5
Ship
QA loop, memory/qa-iteration-N.md, retrospective, tag a release. The next feature restarts at Discovery.
Benefits
Send a one-paragraph problem —
here’s what you get back.
Spec-first, always
Every feature lands in specs/<slug>/ as spec + plan + tasks before a single production line. No guessing, no rewrites — the disagreement happens on paper.
Honest metrics, not vibes
Case studies come with commit hashes, DEVLOG entries, and named bugs. If a number is not verifiable, it doesn't get shipped in the copy.
Frozen logic, held-line taste
Claude does the typing. The pivots, the frozen-logic calls, and the moment we stop and think — those stay mine. That's why the code feels considered.
Experience
The three most recent
chapters.
- 2026 — now
Solo studio · AI-collaborative software
Shipping five production case studies with Claude as pair. Every build ships spec + plan + DEVLOG. ShipLoop discipline as the operating system.
- 2025 — 2026
First Claude-collaborative production builds
Noble booking SaaS, Angel Trucking pipeline, Fieldmark PDF-to-checklist. Learned the frozen-logic discipline the hard way — refactored what I would have shipped.
- 2024 — 2025
Prompt patterns · internal automation
Built early Opus/Sonnet/Haiku routing rigs and volume automation for small teams. First contact with the “spec before code” instinct.
Voices
Pilots and stakeholders on
what shipping honestly looks like.
MAR 12, 2026
Denis M.
Owner, Noble barbershop pilot
Ruslan wrote a spec on Monday, showed a booking flow on Wednesday. By Friday it took real cards. I never saw someone move that clean.
JAN 08, 2026
T. Hall
Language coach, Lexora beta
The audio pipeline runs so cleanly that my students think there’s a person on the other end. 61 unit tests kept a small team feeling large.
FEB 04, 2026
Angel P.
Founder, Angel Trucking
Five-stage plan before a single production line — that discipline is why we ship without rewrites. Every sprint lands on the date he gave.
DEC 19, 2025
K. Osipov
Community manager, smm-factory pilot
Eight agents replaced a two-person social team and cost forty cents a week. Approvals stayed in Slack — nothing shipped without a human tap.
JAN 27, 2026
M. Kravchuk
Field ops, PDF-to-checklist pilot
Rejected on Monday, resubmitted Tuesday, live Wednesday. He owned every note from Apple review and turned it into a stronger app.
SEP 21, 2026
Claude Opus
Collaboration partner
Working with Ruslan means the spec arrives before the code, and the DEVLOG arrives before the next session. That’s the whole trick.