What a spec is for, and at what level to write it
Too vague, a spec leaves the team and coding agents to fill the gaps their own way; too detailed, it goes stale before anyone reads it. This lesson helps you clarify what a specification document should deliver and choose the right level of detail for the decision at hand and the reader, human or machine.
Lesson objective
By the end of this lesson, you will be able to say what a spec must enable (understand, decide, verify) and choose the right level (PRD, feature spec, ticket) according to the decision at hand and the reader, human or agent.
Topics covered
- writing specs
- PRD vs feature spec
- functional specification
- development ticket
- spec level of detail
Where it fits
The job of a spec
What is a spec for, at what level should you write it, and how do you say what you want without dictating how to do it?
Lessons in this module
- What a spec is for, and at what level to write it (this lesson)
- Intent before solution
What you will learn in this module
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.
Related courses
- Product ManagementJuniorSome basics are useful: introductory knowledge of the topic.
Design and validate a product experience with AI
2 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Instrument a product and use data to make decisions
3 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Prioritize and build an outcome-based roadmap
2 hr 30 min