software engineer at a major real estate tech company in 2019 and later joined a startup, gaining broad experience in backend development. I joined Mercari in 2022, where I have led the development and operation of crypto currency trading services. Mercoin / Backend Engineer
coding becomes common, I wondered if clear specs alone could let AI build the code. • So I tried spec-driven development on a real project. • In this talk, I’ll share what worked, what didn’t, and what I learned about how engineers and AI can work together.
generated code that worked according to specs • ❌ However, generated code wasn’t necessarily ‘good’ code ◦ Good code = Readable, maintainable, well-designed • Needed heavy refactoring before use 📊 76% of developers refactor at least half of AI-generated code before using it. Source: State of AI 2025 Survey https://2025.stateofai.dev/en-US/usage/#ai_generated_code_refact
AI lacks critical context • Domain rules and business context • The “why” behind each feature • Organizational tacit knowledge • Technical trade-offs → I needed to provide this missing knowledge and context myself
GitHub Spec Kit: specify → plan → task →implement • Switched from abstract to step-by-step prompts with examples • Asked AI to explain its reasoning before coding
To guide AI, engineers must first design clearly in their minds. • Explaining specs to AI requires deep product and domain understanding. • AI makes us faster, but doesn't inherently make us better in the long term.
coding cost → more code → more complexity. • As AI evolves, two abilities become more important than ever: ◦ System design ◦ Business and domain knowledge — communicating context to guide AI
our role is more essential than ever. • The more AI advances, the higher the level of judgment we need. • There’s still so much to build — and even more to learn. 🐎 Let’s harness AI and move things forward.