Skip to content

Vision

Used in the playbook Project foundation, stage 2. Also used in Product vision

Download vision.md — the source, as in the repository.

How to use

The template's own instructions:

Template from the UASK Engineering Hub, playbook mgmt.project-foundation, stage 2. Save as project/VISION.md. One page or less. Sections marked "Optional" may be deleted; delete these comments when a section is written.

Fields

Front-matter fields and sections of the document the template creates. A section marked Optional in the template may be deleted from a copy; every other field and section stays (tools/check_artifacts.py checks this for the kinds it knows).

Field or sectionWhereRequired
titlefront matterrequired
statusfront matterrequired
versionfront matterrequired
datefront matterrequired
ownerfront matterrequired
Statementsectionrequired
Audiencessectionrequired
Outcomessectionrequired
Non-goalssectionrequired
Principlessectionoptional

Example

A filled-in copy for an invented product, templates/examples/vision.md, in the Hub repository.It shows the level of detail to aim for, not text to reuse.

example-vision.md
---
title: Product Vision
status: draft
version: 0.1.0
date: 2026-03-01
owner: Product Owner
---
# Product Vision — Fieldnotes
## Statement
For field researchers who work without a reliable connection, Fieldnotes is a note-taking app that keeps every note as a plain
file the researcher owns. Unlike cloud note services, it works fully offline and never locks the notes in.
## Audiences
| Audience | Gets |
|---|---|
| Field researchers | notes that are written offline and merged later without loss |
| Research team leads | one repository per project, with a history of every change |
## Outcomes
- **O-1** Within 12 months, 80 % of testers write a day of notes offline and merge them without help.
- **O-2** Any user can leave with all their notes in under five minutes.
## Non-goals
- No real-time collaborative editing.
- No built-in cloud storage; users bring their own Git host.
## Principles
- The user's files come first; the app is a way to work with them.

Completion checks

A copy is complete when:

  • every required field and section above is present, in the same order, and no bracketed placeholder is left;
  • the template's comments are deleted from the copy;
  • python3 .uask/hub/tools/check_artifacts.py . reports no failure for it: front matter, sections, ids, leftover placeholders and comments (tools/check_artifacts.py, in every release bundle);
  • the exit criteria of stage 2 of the playbook Project foundation are met;
  • the owner has approved it, where the playbook asks for approval. Only the owner sets approved.

Source

templates/vision.md, as in the repository. Placeholders are in square brackets; comments carry the instructions.

vision.md
---
title: Product Vision
status: draft # draft | review | approved — only the owner sets approved
version: 0.1.0
date: YYYY-MM-DD
owner: Product Owner
---
# Product Vision — Product name
<!-- Template from the UASK Engineering Hub, playbook mgmt.project-foundation, stage 2.
Save as project/VISION.md. One page or less. Sections marked "Optional" may be deleted;
delete these comments when a section is written. -->
## Statement
<!-- One paragraph in the classic positioning form:
For <target users> who <need or problem>, <product> is a <category> that <key benefit>.
Unlike <current alternatives>, it <main difference>.
Add a one-line motto only if the team will really use it. -->
## Audiences
<!-- Real groups, not "everyone"; what each gets from the product. -->
| Audience | Gets |
|---|---|
| … | … |
## Outcomes
<!-- Three to five results with a time horizon ("in 12 months"), each observable by someone other than
the author. Each has an id (O-1, O-2, …) that is never reused: the PRD's scenario table names the
outcome each scenario serves, so that an outcome nobody serves is visible. -->
- **O-1** …
## Non-goals
<!-- What the product deliberately will not do or be. The PRD's out-of-scope list follows from these. -->
- …
## Principles
<!-- Optional. Product principles that decide trade-offs. If they are rules for contributors, keep them in
AGENTS.md and link from here instead. -->