problem-based-srs
Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability.
rafael-gorski · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add RafaelGorski/Problem-Based-SRS --skill problem-based-srs技能说明
name: problem-based-srs description: Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to functional requirements with full traceability. license: MIT metadata: author: rafael-gorski version: "1.3" methodology: problem-based-srs
Problem-Based SRS
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.
Orchestrate requirements engineering using the Problem-Based SRS methodology (Gorski & Stadzisz). This skill coordinates a structured process (Step 0 through Step 5) that ensures every requirement traces back to a real business problem.
Methodology Overview
Diagram standard: Use Mermaid UML diagrams as the preferred format for all visual artifacts. Mermaid is mandatory for Software Glance (Step 2) and Software Vision (Step 4), and preferred for other steps where diagrams add value.
Stakeholder Input
↓
┌──────────────────┐
│ Step 0: BC │ → /problem-based-srs business-context
│ Business Context │
└────────┬─────────┘
↓
┌──────────────────┐
│ Step 1: CP │ → /problem-based-srs problems
│ Customer Problems│
└────────┬─────────┘
↓
┌──────────────────┐
│ Step 2: SG │ → /problem-based-srs software-glance
│ Software Glance │
└────────┬─────────┘
↓
┌──────────────────┐
│ Step 3: CN │ → /problem-based-srs needs
│ Customer Needs │
└────────┬─────────┘
↓
┌──────────────────┐
│ Step 4: SV │ → /problem-based-srs software-vision
│ Software Vision │
└────────┬─────────┘
↓
┌──────────────────┐
│ Step 5: FR/NFR │ → /problem-based-srs functional-requirements
│ Requirements │
└──────────────────┘
Traceability Chain: FR → CN → CP (every requirement traces back to a problem)
Domain Mapping (WHY → WHAT → HOW):
| Domain | Artifact | Question Answered |
|---|---|---|
| WHY | Customer Problems (CP) | Why is the solution needed? (Business justification) |
| WHAT | Customer Needs (CN) | What outcomes must the software provide? |
| HOW | Functional Requirements (FR) | How will the system behave? |
Available Actions
The Problem-Based SRS methodology is driven by a single command — /problem-based-srs —
that dispatches to a step via an action argument. Run /problem-based-srs with no
action (or full) to orchestrate the complete methodology end-to-end.
| Action | Command | Purpose |
|---|---|---|
business-context | /problem-based-srs business-context | Step 0: Establish structured business context and principles |
problems | /problem-based-srs problems | Step 1: Identify and classify customer problems |
software-glance | /problem-based-srs software-glance | Step 2: Create high-level solution view |
needs | /problem-based-srs needs | Step 3: Specify customer needs (outcomes) |
software-vision | /problem-based-srs software-vision | Step 4: Define software vision and architecture |
functional-requirements | /problem-based-srs functional-requirements | Step 5: Generate functional requirements |
validate | /problem-based-srs validate | Validate traceability across domains (ZigZag) |
complexity | /problem-based-srs complexity | Optional: Axiomatic Design quality analysis |
full | /problem-based-srs | Run the complete methodology (Step 0 → Step 5) |
How actions are dispatched
Each action's detailed, step-specific instructions live in a reference file next to
this skill: reference/<action>.md (the file name IS the action). When the user
invokes an action, you MUST read the matching reference file before producing any
artifact, and follow it exactly:
| Action | Reference file |
|---|---|
business-context | reference/business-context.md |
problems | reference/problems.md |
software-glance | reference/software-glance.md |
needs | reference/needs.md |
software-vision | reference/software-vision.md |
functional-requirements | reference/functional-requirements.md |
validate | reference/validate.md |
complexity | reference/complexity.md |
live | reference/live.md — opens the SRS Navigator canvas (/live) |
For a full run (bare /problem-based-srs), work through the steps in order,
reading each reference/<action>.md as you reach that step.
🔖 Identifier Notation (CANONICAL)
Every artifact ID uses dotted notation, which encodes the traceability chain in the ID itself — reading an ID tells you what it descends from:
| Artifact | Format | Example | Reads as |
|---|---|---|---|
| Customer Problem | CP.{n} | CP.01 | the first customer problem |
| Sub-problem | CP.{n}.{m} | CP.01.1 | first facet of CP.01 |
| Sub-sub-problem (rare) | CP.{n}.{m}.{k} | CP.01.2.1 | first facet of CP.01.2 |
| Customer Need | CN.{cp}.{n} | CN.01.1 | first need addressing CP.01 |
| Functional Requirement | FR.{cp}.{cn}.{n} | FR.01.1.1 | first FR implementing CN.01.1 |
| Non-Functional Requirement | NFR.{n} | NFR.01 | the first quality requirement |
Rules:
- Always emit dotted IDs.
CP.01,CN.01.1,FR.01.1.1— neverCP.1.1for a need or other ad-hoc shapes. - An ID must state its parent.
FR.01.1.1impleme