software-vision

Installation
SKILL.md

Software Vision

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC 2119 RFC 8174 when, and only when, they appear in all capitals, as shown here.

Overview

Step 4 of 5 in the Problem-Based SRS methodology.

Single Responsibility: Transform the Software Glance + Customer Needs into a detailed Software Vision document that provides high-level scope, positioning, and architectural boundaries.

Position in Process:

Step 1: Customer Problems → Step 2: Software Glance → Step 3: Customer Needs
                                           ↓                        ↓
                                  Step 4: SOFTWARE VISION (You are here)
                                  Step 5: Requirements Specification

Purpose

Installs
9
GitHub Stars
31
First Seen
Mar 21, 2026
software-vision — rafaelgorski/problem-based-srs