A chronological collection of insights on technical specification, product strategy, and AI-driven documentation.
Guide (13 articles)
Clear filtersSpec-Driven Development flips AI coding on its head: the specification becomes the source of truth and code becomes a generated artifact. Here's what SDD means, the tools that power it (GitHub Spec Kit, Kiro, Tessl, cc-sdd), how it works with Claude Code, Codex, and Cursor, plus the benefits, criticisms, and a practical workflow.
Stop writing prompts and start building specs. Myspec is the AI agent that turns your vision into structured product requirement documents (PRDs). By asking the right questions, myspec helps you define clear goals and catch edge cases before you start building, ensuring your AI-generated website is exactly what you imagined.
This is Vibe Specify’ing (Chat-to-Edit). This guide teaches you how to master the edit flow so you can refine your specifications at the speed of thought, keeping your spec bundle coherent without ever touching a raw markdown file.
How to scale Spec-Driven Development across multiple teams, repos, and products using interface specs, explicit dependencies, lightweight review, and clear metrics.
Turn your specs from static documentation into enforceable contracts by building verification into your workflow: from manual checklists to automated test mapping and browser-based verification, plus continuous alignment practices.
A practical workflow for turning an approved spec into a clean, testable implementation—from breaking down acceptance criteria into tasks to structuring your final PR, with AI as a guardrail-driven assistant.
Spec reviews catch design bugs before implementation starts. Learn why they matter, who should be involved, and how to run them efficiently.
A practical guide to structuring spec files in your repository, maintaining a spec index, naming conventions, and integrating specs into your Git workflow—including how to use specs effectively with AI coding tools.
Spec-first AI coding replaces vague prompts and chaotic code generation with a simple workflow: clarify requirements, write a spec, then let the AI implement exactly what you approved.
How to write observable, unambiguous, complete, and independent acceptance criteria that translate directly into automated tests and AI-executable contracts.
