DefineWrite down why you’re building it and which screens change
A feature spec holds the problem, non-goals, requirements, and acceptance criteria. Link screen specs to it, and the screens that change show up on the sitemap.
- Feature specs (PRD)
- Sitemap
- Screen specs and wireframes
- Decision log
- Space docs
- Direction docs
Feature specs (PRD)
Problem, why now, non-goals, requirements, acceptance criteria, success metrics
Problems and fixes
What changes
Every spec has a different format, so gaps go unnoticed
Feature specs have fields for requirements, acceptance criteria, and success metrics. When you go to approve one, zapp points out requirements without acceptance criteria.
Which screens a feature changes depends on someone’s memory
Link the sitemap and screen specs to the spec, and every screen that changes is visible at a glance.
You keep re-discussing “why did we do it that way?”
Decision records are never edited, only added. To reverse a decision, a new one supersedes the old one.
Features
What you can do in Define
Feature specs (PRD)
Problem, why now, non-goals, requirements, acceptance criteria, success metrics
Sitemap
Lay out pages as a tree and attach a spec to each screen
Screen specs and wireframes
Mark screens as existing, changed, or new. Wireframes are drawn in text, so AI can read and edit them too
Decision log
Decisions, troubleshooting, and incidents on one timeline
Space docs
Build a document tree of any depth inside a project
Direction docs
Start from strategy, north star, and positioning templates
Start light, with a one-line idea
Sign up and start right away in the web console. Basic is free.
Talk to us
Leave your question and we'll reply by email.