Module
Module 1 of 5Lesson 1 of 1~3 min

Course introduction

This course teaches product managers to write specs that a developer and a coding agent alike can follow without guessing. Step by step, you build the spec for a feature of your own product and the file that goes with it in the repository, ready to use with your team.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this introduction, you will know what you are going to produce (the spec of a feature from your product and its intent file) and in what order the four modules get you there.

Topics covered

  • writing specs
  • functional specifications
  • coding agents
  • specs for AI agents
  • product manager

Where it fits

Overview

What will I write in this course, and in what order?

Lessons in this module

  1. Course introduction (this lesson)

What you will learn in the course

This lesson is part of the course Write specs that developers and AI agents understand

  • Choose the level of spec suited to the decision at hand (PRD, feature spec, ticket) and know what each must contain.
  • State the intent of a feature (problem, target outcome, constraints, non-goals) separately from the solution, to leave the right room to the team and the agent.
  • Write verifiable, declarative and unambiguous Given/When/Then acceptance criteria, including as tables of examples.
  • Identify edge cases and non-functional requirements (performance, security, accessibility, personal data) and make them testable.
  • Write a spec and an intent file that a coding agent can use (context, constraints, files involved, out of scope, verifiable definition of done).
  • Review a coding agent's plan against the spec, spot gaps before it writes code, then check the evidence of what was delivered.
  • Keep a spec alive (versions, decisions, updates when the code reveals a case) and spot the anti-patterns that make it useless.

Related courses