up-vision

Draft the System Vision Document using the vision template and save it as docs/up/01-vision.md.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: up-vision
Source: https://github.com/apolosan/unified_process_pi_extension/tree/main/skills/up-vision
Command: npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts the System Vision Document for UP Inception projects, providing a structured, stakeholder-aligned artifact that guides scope, constraints, and initial glossary.

Core Features & Use Cases

  • Uses the vision-template to capture problem statement, business context, stakeholders, scope, constraints, and glossary.
  • Automates artifact creation and saving to the UP state as 01-vision.md, enabling the next steps in the UP workflow.
  • Supports reuse across multiple inception efforts and ensures alignment with the UP process.

Quick Start

Draft the System Vision Document using the vision template and save it as docs/up/01-vision.md.

Frequently Asked Questions about up-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a System Vision Document for UP Inception?

To draft a System Vision Document for UP Inception, apply a structured template to capture the problem statement, stakeholders, scope, and constraints. This process ensures project alignment and saves the artifact as 01-vision.md.

What is a system vision document and what should it include?

A system vision document defines project alignment by capturing the problem statement, business context, stakeholders, scope, constraints, and glossary. It guides the initial UP Inception phase and establishes consistent project boundaries.

How do I capture stakeholder and scope details for project documentation?

You can capture stakeholder and scope details by applying a vision-template structure during the UP Inception phase. This structures your project documentation into a standardized artifact saved as 01-vision.md.

Does the UP Inception vision template support reuse across multiple projects?

Yes, the UP Inception vision template supports reuse across multiple inception efforts. It applies a consistent structure to capture scope and constraints, ensuring alignment with the UP process for each new project.

Can I automate saving the system vision artifact to update the UP state?

Yes, you can automate artifact creation and saving to update the UP state. The system saves the vision document as docs/up/01-vision.md, which automatically reflects the completion of the vision activity.