Show HN: Spec-Driven AI Development – Keep AI-Generated Code Maintainable I built a system to solve the biggest problem with AI-assisted coding: you can't maintain the code 6 months later because you've lost all context about WHY it was written. The core idea is simple: instead of jumping straight into code, you generate specifications first, then track every planning decision and todo in markdown files that move through folders (plans → in-progress → executed). This execution history stays with your project forever. The toolkit includes: - Spec generators (architect + development specs from requirements) - Session management (track progress across coding sessions) - Execution history tracking (the 3-folder system) - Git workflow helpers (branches, conventional commits) - Spring Boot test generation - Automated code review agents (OWASP security, SOLID, performance) It's built for Claude Code but the workflow concepts apply to any AI coding tool. I used this to build a complete Spring Boot backend — 45-day estimate compressed to 5 days. The execution history is still readable months later. $49 for the complete toolkit: https://hathwar.gumroad.com/l/spec-driven-ai Landing page with full details: https://samhath03.github.io/spec-driven-ai/ Happy to answer questions about the workflow. |