eavicarme.com
Building in public

Roadmap

This isn't a wishlist — it's pulled from the same lightweight task files that track every real change in this repo, planned and built with Claude Code's 6-agent team. Idea means genuinely unstarted, Planned means there's a clear next step, Building means it's actually in flight, Shipped means it's live — no fudging between them.

Why this exists

The road behind this page

  1. Stop 01

    The idea

    It started as just that — an idea. Not another static resume, but a portfolio that actually shows how I think and build, not just what I've done.

  2. Stop 02

    Claude, the orchestrator

    Instead of building this alone, I set up a 6-agent Claude Code team right in this repo's CLAUDE.md and let it drive the actual implementation — architecture, backend, frontend, design, database, DevOps, each with its own lane.

    Meet the 6-agent team
  3. Stop 03

    Shipping v1

    Getting a real, working version live mattered more than getting it perfect — it's proof for recruiters that this isn't vaporware, and it's proof for me that the workflow actually works before I lean on it harder.

  4. Stop 04

    Where it's headed

    A fully working portfolio that's also a genuine playground — plus real two-way communication, starting with a contact form, so a visitor isn't stuck just... reading.

  5. Stop 05

    What's next

    A tool anyone can use to generate their own JSON and set it as a live response payload on my API — so the "mock API" idea becomes something people can actually configure themselves, not just a fixed demo endpoint.

The board below tracks this at a granular level.