openup-create-vision

name	openup-create-vision
description	Generate a vision document from template
model	sonnet
arguments	[{"name":"project_name","description":"Name of the project","required":true},{"name":"problem_statement","description":"Brief description of the problem to be solved","required":true}]

Create Vision Document

This skill generates a vision document from the OpenUP template.

When to Use

Use this skill when:

• Starting a new project and need to define the vision
• In Inception phase and need to document project scope
• Stakeholders need a clear understanding of project goals
• Need to define problem statement and proposed solution
• Creating initial project artifacts

When NOT to Use

Do NOT use this skill when:

• Vision document already exists (update it directly or use revision process)
• Need detailed requirements (use use case skills instead)
• Looking for technical architecture (use /openup-create-architecture-notebook)
• In later phases (Elaboration+) when vision should be stable

Success Criteria

After using this skill, verify:

• Vision document exists at docs/vision.md
• Project name and problem statement are filled in
• Proposed solution overview is present
• Stakeholders are identified
• Key features are listed
• Success criteria are defined

Process

Load Project Config (context + rules — do this first)

If docs/project-config.yaml exists, apply it before drafting (skip if absent): inject its context: as <project-context> and its rules.vision as <project-rules>, then confirm every injected rule holds before marking the artifact complete. Rules are additive — they may add but never waive a framework criterion. Full mechanism + precedence (the single source): docs-eng-process/project-config.md.

1. Read Project Context

Read docs/project-status.md to understand:

• Current phase
• Stakeholders
• Project context

2. Copy Template

Copy docs-eng-process/templates/vision.md to docs/vision.md

3. Fill in Vision Document

Update the vision document with:

• Project name: $ARGUMENTS[project_name]
• Problem statement: $ARGUMENTS[problem_statement]
• Positioning: What makes this solution unique
• Stakeholders: Key stakeholders and their needs
• Key features: High-level feature list
• Constraints: Technical, business, or other constraints

3a. Write Instance Frontmatter (T-038 — doc traceability)

Replace the template's provenance frontmatter (type: Template, source_url) with an instance frontmatter block declaring this file as a typed work-product instance under the project's docs/. The vision is the top of the OpenUP trace spine, so it has no traces-from. Grade afterward against the cross-cutting Doc Traceability Rubric — every authored instance is graded against it, additive to the vision-rubric.

Example block:

---
type: vision                # required — v1 spine
id: VIS-001                 # stable, project-unique
title: <Project Name>
status: approved            # draft | approved | implemented | verified | obsolete
owner-role: analyst         # optional
---

Field reference: docs-eng-process/doc-frontmatter.md. Validator: python3 scripts/check-docs.py.

4. Self-Critique

Apply the Self-Critique SOP (docs-eng-process/sops/self-critique.md) before validating: take a hostile-reviewer stance, surface every load-bearing assumption into the document, and confirm the problem statement and success criteria are falsifiable — not aspirational claims that could never fail. List every weakness you find — including ones you are uncertain about — then fix or explicitly flag each one. Rank them and record the top one or two with their resolutions.

5. Validate Completeness

Re-check every item in Success Criteria (top of this skill) against the document you produced; fix any gap before returning.

Output

Returns:

• Path to created vision document
• List of sections filled in
• Any sections that need manual completion

Common Errors

Error	Cause	Solution
Template not found	Template path incorrect	Verify docs-eng-process/templates/vision.md exists
File already exists	Vision document already created	Update existing file or confirm overwrite
Missing arguments	Required arguments not provided	Provide project_name and problem_statement

References

• Vision Template: docs-eng-process/templates/vision.md
• Vision Work Product: docs-eng-process/openup-knowledge-base/core/common/workproducts/vision.md
• Analyst Role: docs-eng-process/openup-knowledge-base/core/role/roles/analyst-6.md

See Also

• openup-inception - Inception phase guidance
• openup-create-use-case - Create detailed use cases
• openup-create-risk-list - Document project risks