Crema spec Get the free skill
Blog

Notes on building software with AI agents.

Software factories, product builders, and AI-native teams all run on one thing: a spec people can trust. These articles cover the research, the data, and the practice of governing it.

· spec-driven development

What Is Spec-Driven Development? A Guide for AI Coding Teams

Spec-driven development is a way of building software where a written spec, not a chat prompt, tells AI coding agents what to build and why. The spec becomes the source of truth that humans review and agents follow.

Read the article
· vibe coding

Vibe Coding vs. Spec-Driven Development: When Each One Breaks

Vibe coding vs spec-driven development is not a fight. Vibe coding is great for prototypes and throwaway tools, while specs are what you need once real users, real data, or a team depend on the code. Here is where each breaks and how to graduate from one to the other.

Read the article
· prd template

How to Write a PRD for AI Coding Agents (Free Template)

A PRD for AI coding agents is a short, testable requirements document that tells an agent who a change is for, why it matters, what is in and out of scope, and how to prove it works. Here is what to include, how long to make it, and a free template.

Read the article
· product builder

How to Hire (or Become) a Product Builder: Skills, Interview Questions, and Team Design

A product builder owns a feature from problem to shipped code, writing the spec, directing AI agents, and verifying the result. Here is the skills matrix, job description template, interview questions, take-home exercise, and team design to hire one.

Read the article
· spec drift

What Is Spec Drift? Why AI-Built Software Stops Matching the Plan

Spec drift is what happens when a team's spec splits into competing versions and the code follows whichever one an agent read last. Here is how it starts, how to spot it, what it costs, and how to stop it.

Read the article
· decision records

Decision Records for AI Teams: Why Every Spec Change Needs an Audit Trail

Decision records are short documents that capture what a team decided, why, and what it costs. AI agents now propose more spec changes than people can track, so every change needs a record of who proposed it, who approved it, and why.

Read the article
· software factory

What Is a Software Factory? Why AI Coding Pipelines Run on Specs

A software factory is an automated pipeline where AI coding agents take work through structured steps: intake, spec, build, verify, and ship. Humans set intent and approve gates while agents do the typing. The spec decides what the factory builds.

Read the article
· product builder

Product Builder vs. Product Manager: The Role AI Is Rewriting

A product builder is one person who decides what to build and then builds it, using AI coding agents to cover the engineering work. The role merges product management and software engineering, and AI-native companies are hiring for it now.

Read the article
· ai native companies

When 100% of the Company Codes: How AI-Native Companies Stay in Control

AI-native companies are startups built around AI agents from day one, and many have everyone coding. Designers, marketers, and founders ship changes with Claude Code and Cursor, so the question shifts from who can code to who checks the work.

Read the article