Your product in progress
Replace this starter entry with the product you are building. Capture the problem, current milestone, next steps, and the decisions still being explored.
Open product documentation
Replace each prompt with the facts, links, and decisions for this product. Mark unknowns as open questions instead of guessing.
What is it?
Product name, one-sentence description, value proposition, owner, and last-updated date.
Why are we building it?
User problem, business opportunity, evidence, goals, and how success will be measured.
Who is it for?
Primary users, use cases, permissions, user needs, and important operating contexts.
What does it do?
Core workflows, features, requirements, exclusions, and current capability status.
How does it feel to use?
Key journeys, design references, accessibility requirements, and usability findings.
Where is it going?
Current phase, recent progress, next milestones, blockers, and planned scope—with dates.
How is it put together?
System overview, components, data flows, diagrams, and the reasoning behind key decisions.
What does it depend on?
Languages, frameworks, infrastructure, third-party services, APIs, and integration owners.
How is information protected?
Data collected, retention, privacy assumptions, access controls, threat considerations, and security notes.
How do we know it works?
Test strategy, automated checks, manual scenarios, known defects, and release criteria.
How is it run?
Environments, deployment steps, monitoring, recovery, support process, and operational owner.
What needs attention?
Constraints, limitations, assumptions, risks, mitigations, and questions that still need an answer.
What are we learning?
Adoption and outcome measures, feedback sources, research notes, and how insights shape the roadmap.
What changed and when?
Dated release notes, meaningful product changes, decision records, contributors, and links to supporting docs.
For an in-progress product, keep the current state, next decision, and date of the last update easy to find.