Menu
Generate a vision document from template
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
One-command project setup for OpenUP - interactive initialization wizard
Mark a task as complete, update roadmap, commit changes, and prepare traceability logs
Execute an already-claimed lane's Operations boxes with script/judgment classification — script steps run directly with zero self-brief, judgment steps self-brief and execute. Handles only pick/resume; every other resolve path routes to /openup-next.
Run OpenUP Assess Results at iteration end — check evaluation criteria, demo only completed acceptance-tested work, feed discovered work back, and trigger the milestone review at a phase boundary
Run the phase milestone go/no-go — prepare derived evidence, pause for the human decision via an input-request, and record the milestone (never advance the phase itself)
Begin a new OpenUP iteration with proper phase context and task selection
| 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}] |
This skill generates a vision document from the OpenUP template.
Use this skill when:
Do NOT use this skill when:
/openup-create-architecture-notebook)After using this skill, verify:
docs/vision.mdIf 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.
Read docs/project-status.md to understand:
Copy docs-eng-process/templates/vision.md to docs/vision.md
Update the vision document with:
$ARGUMENTS[project_name]$ARGUMENTS[problem_statement]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.
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.
Re-check every item in Success Criteria (top of this skill) against the document you produced; fix any gap before returning.
Returns:
| 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 |
docs-eng-process/templates/vision.mddocs-eng-process/openup-knowledge-base/core/common/workproducts/vision.mddocs-eng-process/openup-knowledge-base/core/role/roles/analyst-6.md