跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

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):

DomainArtifactQuestion Answered
WHYCustomer Problems (CP)Why is the solution needed? (Business justification)
WHATCustomer Needs (CN)What outcomes must the software provide?
HOWFunctional 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.

ActionCommandPurpose
business-context/problem-based-srs business-contextStep 0: Establish structured business context and principles
problems/problem-based-srs problemsStep 1: Identify and classify customer problems
software-glance/problem-based-srs software-glanceStep 2: Create high-level solution view
needs/problem-based-srs needsStep 3: Specify customer needs (outcomes)
software-vision/problem-based-srs software-visionStep 4: Define software vision and architecture
functional-requirements/problem-based-srs functional-requirementsStep 5: Generate functional requirements
validate/problem-based-srs validateValidate traceability across domains (ZigZag)
complexity/problem-based-srs complexityOptional: Axiomatic Design quality analysis
full/problem-based-srsRun 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:

ActionReference file
business-contextreference/business-context.md
problemsreference/problems.md
software-glancereference/software-glance.md
needsreference/needs.md
software-visionreference/software-vision.md
functional-requirementsreference/functional-requirements.md
validatereference/validate.md
complexityreference/complexity.md
livereference/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:

ArtifactFormatExampleReads as
Customer ProblemCP.{n}CP.01the first customer problem
Sub-problemCP.{n}.{m}CP.01.1first facet of CP.01
Sub-sub-problem (rare)CP.{n}.{m}.{k}CP.01.2.1first facet of CP.01.2
Customer NeedCN.{cp}.{n}CN.01.1first need addressing CP.01
Functional RequirementFR.{cp}.{cn}.{n}FR.01.1.1first FR implementing CN.01.1
Non-Functional RequirementNFR.{n}NFR.01the first quality requirement

Rules:

  1. Always emit dotted IDs. CP.01, CN.01.1, FR.01.1.1 — never CP.1.1 for a need or other ad-hoc shapes.
  2. An ID must state its parent. FR.01.1.1 impleme
阅读完整来源 ↗