Inspiration

Inspiration

The inspiration came from two places one external, one deeply personal.

Externally, it was spec-driven development itself. When I read about the methodology planning before building, having AI interview you instead of the other way around, maintaining context across sessions I had a light bulb moment. What if this process could be applied to a person instead of a product?

Personally, I've always been someone who wanted the full picture before taking action. I thought having the complete blueprint was the only path to success. But as I've grown, I've come to understand that you're rarely going to have the full picture. Sometimes all you have is a feeling with no evidence of whether it will work or not. The real question is: will you stay true to it anyway?

If I was wrestling with that the search for clarity, the paralysis before the first step then other people were too. And I realized: you don't need everything. You just need one clear path. That's enough to move. That momentum builds self-trust. That self-trust builds conviction. And conviction is what carries you toward your goals, your purpose, your next season.

LifeSpec was born from that insight, the greatest thing we can ever ship and develop is ourselves!

What it does

LifeSpec guides users through 9 branching voice-first questions and synthesizes their answers into a living Personal Identity Document six sections: Who You Are, Where You Are, What's In The Way, What You're Here For, Your Next Steps, and Your Declaration. The document can be downloaded as a PDF and shared via a unique URL.

How we built it

Built using spec-driven development with Claude Code 11 checklist items, 3 checkpoints, autonomous build mode. Stack: Next.js, TypeScript, Tailwind CSS, Claude API (Anthropic), OpenAI TTS, Supabase, Vercel, and Resend.

Challenges we ran into

Getting API keys configured, orchestrating voice input with TTS audio and Claude API responses in real time, and learning that context both from the producer and user side is everything when building something meant to feel deeply personal.

Accomplishments that we're proud of

Here's both answers:

Accomplishments I'm proud of:

Accomplishments I'm proud of

Seeing something that lived only in my mind become something I could actually interact with. That alone was worth everything.

I'm proud of learning to build with intention to think in systems, to understand operations, to know what to deploy and when. To think about all the facets of what it means to create something real, not just imagine it. Most people have ideas. Far fewer sit down and build them. I did that today.

I'm also proud of going through the full spec-driven process scope, requirements, technical spec, build checklist, working app and understanding why each step matters. That's a workflow I'll carry into everything I build from here.

What we learned

That there's a difference between having the vision of how you want someone to feel and understanding the logistics of how they actually experience it. I had the user outcome in mind from the beginning but building forced me to think through every detail of the interface, the flow, the voice, the moment of reveal. Planning before building made all the difference.

What's next for LifeSpec

The document is just the beginning. What's next is persistence daily check-ins that track how your identity evolves over time. A returning user should be able to see who they were six months ago and who they're becoming now.

Next is also voice selection letting the accountability mode shape not just the questions but the tone, warmth, and energy of the voice itself. Gentle. Direct. Accountable. Each one a different experience.

And eventually LifeSpec as an onboarding layer for everything. Before you build a business, before you take a new job, before you make a major life decision you run a LifeSpec session. Because clarity about who you are is the foundation for every good decision you'll ever make.

Built With

  • claude-api
  • next.js
  • openai-tts
  • supabase
  • tailwind-css
  • typescript
  • vercel
Share this project:

Updates

Submission history